Recently one of the customers reported that the Release Management client is failing with the above error and wanted to know how to come out of the error. Now let us understand this error a bit more and discuss the steps to come out of it.
Release management client caches the last server that you had accessed and by default tries to connect to it. When it is not able to connect to that server, it fails with the mentioned error. You can disable that cache by changing a setting in the client so that the next run of the client console ask you for the server details. Here is how you can do that: –
- Open an admin command prompt.
- Open the file Microsoft.TeamFoundation.Release.Data.dll.config file in the admin notepad (On my machine the file is at "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\Microsoft.TeamFoundation.Release.Data.dll.config").
- Change the value of RequestServerLocation setting to true. (On your machine, it will be false as it is not asking you for the server url)
<setting name="RequestServerLocation" serializeAs="String">
- Run the console client and it should ask you for the server url.