Releases to Azure environments fails after you upgrade from Release Management 2013 Update 3 RC to Update 3 RTW

Symptoms

When you upgrade from Release Management 2013 Update 3RC to Release Management 2013 Update 3RTW, Releases to Azure environments fails, and the following error message will be logged in log file of the Predeploy step:

System.ArgumentNullException: Value cannot be null. Parameter name: azureStorage.ContainerName

Note 
The Predeploy step log can be accessed from the View Logs tab of the failed release.

Workaround

To work around this issue, validate the vNext Release path that is associated with the vNext Release template. To do this, follow these steps:
  1. Go to vNext Release Path tab under Configure Paths.
  2. Open the vNext Release path that is associated with the vNext Release template.
  3. Edit any of the fields to enable the Save button, undo the edits, and then Save the vNext Release Path.
  4. Trigger New-release.

To validate Azure subscription for the environment associated with the Release, follow these steps:
  1. Go to Manage Azure tab under Administration.
  2. Open the Azure subscription for the environment associated with the Release.
  3. Re-enter Management Certificate and Save the subscription.
Note Information about Azure Subscription ID and Management Certificate Key can be downloaded from publish settings file. Storage Account information is available in your Azure Account.
Properties

Article ID: 2989110 - Last Review: Aug 22, 2014 - Revision: 1

Release Management Client for Visual Studio 2013, Release Management for Visual Studio 2013, Release Management Server for Team Foundation Server 2013

Feedback