Home > ALM, Release Management > Release Management: Communication with the deployer was lost during the deployment (The parameter is incorrect)

Release Management: Communication with the deployer was lost during the deployment (The parameter is incorrect)


At one of my clients, I got this error on Release Management 2015:

Communication with the deployer was lost during the deployment. Please make sure (1) the deployer machine has not rebooted during installation and (2) the component timeout is sufficient to copy the files from the drop location to the deployer machine and install the package.

History:

The Release Management database was migrated from environment to another following the steps at http://blogs.msdn.com/b/visualstudioalm/archive/2014/04/02/need-to-migrating-release-management-server.aspx

I didn’t migrate the machine key because we are only migrating the database and not the server.

Troubleshooting

Open the Deployment Agent log. The default location should be at

C:\Users\<user>\AppData\Local\Temp\Microsoft\ReleaseManagement\14.0\Logs

Where <user> is the user who initiates the build (e.g. your username, build_service user, etc)

In my case, I had the following error

{“ErrorMessage”:”The parameter is incorrect.\r\n”}
12/14/2015 9:20:32 AM – Error – (9528, 9260) – Error while converting string to XDocument: [Data at the root level is invalid. Line 1, position 1.] [   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Parse(String text, LoadOptions options)
at Microsoft.TeamFoundation.Release.Common.ExtensionMethods.XmlExtensionMethods.ToXDocument(String value, Boolean preserveWhitespace)].

The error doesn’t give a lot of information.

On the Release Management server, take a look at Release Management Services log which is located at

C:\Users\<RM user>\AppData\Local\Temp\Microsoft\ReleaseManagement\14.0\Logs\ReleaseManagementServices.log

Where <RM user> is the username of the RM account

ConfigureRM

In the ReleaseManagementServices.log, I saw the following error

Request http://rmserver:1000/account/releaseManagementService/_apis/releaseManagement/TfsService/DoesBuildExists?tfsServerId=1&teamProjectName=Services&buildDefinition=MyBuild&buildNumber=BuildName-1.1.28.21&api-version=6.0 threw exception: System.Security.Cryptography.CryptographicException: The parameter is incorrect.

The CryptographicException caught my attention. I visited the Release Management release definition and there was an encrypted password field.

Solution

Reenter the password in the password field and start new  a release

 

 

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: