More Event Logs in Production Servers

Question

The description for Event ID 0 from source Microsoft Deployment Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
Timestamp: 3/23/2015 1:00:01 AM
Message: Object reference not set to an instance of an object.: \r\n\r\n   at Microsoft.TeamFoundation.Release.Data.Model.SystemSettings.LoadXml(Int32 id)
   at Microsoft.TeamFoundation.Release.Data.Model.ModelFactory.Load[T](Int32 id)
   at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.HeartBeat.SetNewInterval()
   at Microsoft.TeamFoundation.Release.DeploymentAgent.Services.Deployer.HeartBeat.TimerElapsed(Object sender, ElapsedEventArgs e)
Category: General
Priority: -1
EventId: 0
Severity: Error
Title:
Machine: SANDMAN
Application Domain: DeploymentAgent.exe
Process Id: 2148
Process Name: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\bin\DeploymentAgent.exe
Win32 Thread Id: 56408
Thread Name: 
Extended Properties: 
I get the above error logged in production servers and its affecting the performance of my production servers. There is a problem in establishing a connection between the deployment agent and release management server and that's identified as the reason
for these errors. 
Please advice on how to change the frequency of number of errors logged in production servers.

Answer 1

Hi Amar_Baktha,
For your situation, you can follow the following methods to check if the problem can be fixed:
1. Please let us know the version of Release Management you're using. If you use Update 2 or 3, you can rollback to RTM or install Update 4 to have a try. Check last reply in this
thred for more info.
2. Also let us know if the production server and client machine in different domains. If yes, then you can use shadow account. You can refer to this
blog.
3. Remove IIS and readd it.
4. Check if Windows server update service is installed on your production machine. Install/Uninstall it to have a check if the connection can be established.
Please try the methods I mentioned above. If the problem still exist, it would be better to elaborate more details about your scenario.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.