Share via

How to resolve file deployment issues to agents from Release Management

  • Article

Deepak Mittal, Support Escalation Engineer, brings to us another article on what to do if you face issues while deploying files to agents from Release Management

Problem Description:

If you face issues while deploying files to deployer agents from release management.

Please enable traces as mentioned below:

blogs.msdn.com/b/visualstudioalm/archive/2013/12/13/how-to-enable-detailed-logs-and-collect-traces-from-various-release-management-components.aspx

 In the logs, you may see issue like below:

 12/24/2013 12:57:40 PM - Error - (14064, 28536) - The request was aborted: The operation has timed out.: \r\n\r\n at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest
request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at Microsoft.TeamFoundation.Release.Data.ConfigurationServiceRef.ConfigurationService.GetSystemSettings()

   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)

 12/24/2013 11:47:11 AM - Error - (2588, 5428) - Error loading profile for current user: abc\xyz

12/24/2013 11:47:11 AM - Error - (2588, 5428) - Value cannot be null.

Parameter name: value:
\r\n\r\n   at Microsoft.TeamFoundation.Release.Common.ExtensionMethods.XmlExtensionMethods.ToXml(Object value)  at Microsoft.TeamFoundation.Release.Data.Model.CurrentUser.get_Profile()

In order to troubleshoot and resolve such issues, please check the following:

  1. First check the release management server service and deployment agent service, and try to restart them.
  2. Then use the release management server as deployment agent and see if things working fine.
  3. If you are using virtual machine as deployment agent, please change that.
  4. Also ensure you are able to browse <rmserver>:1000/releasemanagement from IE, if it throws authentication error of ask for the credential, then it may be an issue with either IE proxy or group policy or port 1000 block issue from agent.

 Written by: Deepak Mittal, Support Escalation Engineer

 Reviewed by: Romit Gulati, Support Escalation Engineer

Comments

  • Anonymous
    May 18, 2014
    "3. If you are using virtual machine as deployment agent, please change that." Release Management Deployment agent cannot be used in a Virtual Machine????  That seems like a rather large limitation.

  • Anonymous
    August 21, 2014
    Also check whether a shadow-account is properly set up. I had the same problem and this was the solution