DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2905736 - Last Review: August 4, 2014 - Revision: 3.0

On This Page

Summary

This article lists the known issues that you may experience after you install Microsoft Release Management for Visual Studio 2013. You can click the following numbers for the Microsoft Knowledge Base articles to learn more about these issues and the available workarounds.

Known issues for Release Management for Visual Studio 2013

Collapse this tableExpand this table
Microsoft Knowledge Base articleDescriptionNotes
2905740  (http://support.microsoft.com/kb/2905740/en-us/ ) The other Release Management component does not work after you uninstall the client or server
2905741  (http://support.microsoft.com/kb/2905741/en-us/ ) "Page not found" error message when you click "View Request" in a Release Management for Visual Studio 2013 approval notification This issue is fixed in Update 1  (http://support.microsoft.com/kb/2911573/en-us/ ) .
2905742  (http://support.microsoft.com/kb/2905742/en-us/ ) Deployment agents that rely on shadow accounts do not work with Release Management Server for Visual Studio 2013
2905743  (http://support.microsoft.com/kb/2905743/en-us/ ) Deployment fails when you use the HTTPS protocol in Release Management This issue is fixed in Update 1  (http://support.microsoft.com/kb/2911573/en-us/ ) .
2905744  (http://support.microsoft.com/kb/2905744/en-us/ ) "Could not find the file or assembly System.Management.Automation" error during a deployment in Release Management 2013
2907777  (http://support.microsoft.com/kb/2907777/en-us/ ) "The server specified could not be reached" error when you try to connect through Release Management Client
2907779  (http://support.microsoft.com/kb/2907779/en-us/ ) Release Management Client crashes and logs a "MissingSatelliteAssemblyException" error
2989381  (http://support.microsoft.com/kb/2989381/ ) TFS builds are not displayed in Release Management template when you upgrade from Release Management 2013 Update 1
2989107  (http://support.microsoft.com/kb/2989107/ ) Deploy to Azure environments fails after you upgrade from Release Management 2013 Update 3 RC to Update 3 RTW
2989108  (http://support.microsoft.com/kb/2989108/ ) "500 Internal Server Error" occurs when you link an Azure VM in create new vNext: Azure environment flow
2989109  (http://support.microsoft.com/kb/2989109/ ) Microsoft Deployment Agent 2013 auto-upgrade from Update 3 RC to Update 3 RTM does not succeed
2989110  (http://support.microsoft.com/kb/2989110/ ) Releases to Azure environments fails after you upgrade from Release Management 2013 Update 3 RC to Update 3 RTW


Applies to
  • Release Management Client for Visual Studio 2013
  • Release Management for Visual Studio 2013
  • Release Management Server for Team Foundation Server 2013
Keywords: 
kbhowto kbsurveynew KB2905736
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support