Why do I receive an 'Org Administration Locked' message?
|Knowledge Article Number||000004045|
Administrators attempting to make changes to sharing setup or custom field/object setup may receive an error like the following.
This occurs when a similar setup change that affects a large number of records is still being processed. In order to maintain data integrity, the relevant setup area is locked until the change is complete. Sharing changes will only lock sharing setup and custom field/object changes will only lock custom field/object setup.
Examples of scenarios that trigger this message if simultaneous setup changes are attempted:
2. ANT deployments can create an Org Lock
3. A Terminated ANT deployment, does not imply the process is terminated immediately on the server, hence an org lock continues
4. A Timeout ANT deployment just means that the ANT(client) side timeout waiting for the process to complete, does not imply the process is terminated immediately on the server, hence an org lock continues until complete or recovered. To avoid this you may need to adjust the timings in your build.xml file.
5. A heap error could occur with ANT during deployment, this also does not imply the process is terminated immediately on the server, hence an org lock continues until complete or recovered. To avoid this you may need to adjust Java/ANT heap setting in your environment
6. Simultaneous ANT deployments by different individuals can be blocked out due to org locks
Change management, change control and scheduling procedures are essential when making administrative changes as a team.
An Org lock is created to protect the Org from data and metadata integrity issues. There are NO options to remove/delete the org lock.
The duration of the Org lock varies based on the Administrative activity in progress, and is not measurable. The duration depends on multiple factors, object/feature, security controls, table sizes, essentially scope and impact of the changes in progress.
Logging a case with Salesforce support for an Org lock is not necessary, unless the lock exceeds 3hrs or is significantly impacting a critical project. When logging a case, please include the Org with the problem, username with the problem, Logs including Salesforce debug logs & ANT logs, and most importantly the ANT package that caused the problem, and lastly the Setup audit Trail.
To find out what action triggered the organization lock, users can check the "Setup Audit Trail" to view recent actions that meet the criteria outlined above.