title | description | ms.date | ms.reviewer | ms.custom |
---|---|---|---|---|
Known issues when you install Release Management |
This article describes the known issues that may occur after you install Release Management for Visual Studio 2013. |
04/24/2020 |
achand, daleche, muthuk, sriramb, ronai, ans, leov |
sap:Installation\Other |
This article lists the known issues that you may experience after you install Microsoft Release Management for Visual Studio 2013.
Original product version: Visual Studio 2013, Team Foundation Server 2013
Original KB number: 2905736
Microsoft Knowledge Base article | Description | Notes |
---|---|---|
2905740 | The other Release Management component does not work after you uninstall the client or server | |
2905742 | Deployment agents that rely on shadow accounts do not work with Release Management Server for Visual Studio 2013 | |
2905743 | Deployment fails when you use the HTTPS protocol in Release Management | This issue is fixed in Description of Visual Studio 2013 Update 1. |
2907777 | Error when you try to connect through Release Management Client: The server specified could not be reached | |
2907779 | Release Management Client crashes and logs a error (MissingSatelliteAssemblyException) | |
2989381 | TFS builds are not displayed in Release Management template when you upgrade from Release Management 2013 Update 1 | |
2989107 | Deploy to Azure environments fails after you upgrade from Release Management 2013 Update 3 RC to Update 3 RTW | |
2989108 | Error (500 Internal Server Error) occurs when you link an Azure VM in create new vNext: Azure environment flow | |
2989109 | Microsoft Deployment Agent 2013 auto-upgrade from Update 3 RC to Update 3 RTM does not succeed | |
2989110 | Releases to Azure environments fails after you upgrade from Release Management 2013 Update 3 RC to Update 3 RTW |