Pages

Friday, January 13, 2012

Salesforce Inbound Change Sets Deploy Error - organization's administration setup lock

During the validation and deployment of an inbound change set into a Salesforce production organisation I often run into the following issue.

I'll start either the validation or deployment action, wait awhile for the spin wheel to complete and then get a failed result.

The failure reason will be given as:

API Name: Deploy Error
Problem: The changes you requested require salesforce.com to temporarily lock your organization's administration setup. However, the administration setup has already been locked by another change. Please wait for the previous action to finish, then try again later.

If I wait for a period of time without any further action another deployment history will appear with the actual results of the action I started. It's like the deployment action splits off at some point and shows as both a failure due to the org admin setup lock and then later a success when it actually completes.

2 comments:

  1. I see this as well (the failure result, then, after waiting, the actual result). It would be so great if there was an easy way to monitor the deployment's actual status. The waiting between the "org lock" failure and eventual result is stressful.

    ReplyDelete
    Replies
    1. For some reason I found I was less likely to get the org lock message if I didn't leave the window open to actively monitor the deployment. I found it best to close the deployment window and then monitor it via the deployment history.

      Delete