KB38101: “Cannot unlock this object because the requested locked kind does not match that of the lock currently placed on the object” error message is received when attempting to unlock a project schema in MicroStrategy Developer 9.4.1 and 10.x.

Salesforce Solutions Architect • Strategy

After restoring a metadata from backup, a schema lock is in place and cannot be removed by going to Schema -> Unlock Schema from MicroStrategy Developer 9.4.1 and 10.x. Doing so results in the following error: "Cannot unlock this object because the requested lock kind does not match that of the lock currently placed on the object."

SYMPTOM:
After restoring a metadata from backup, a schema lock is in place and cannot be removed by going to Schema -> Unlock Schema from Strategy Developer 9.4.1 and 10.x. Doing so results in the following error:


Cannot unlock this object because the requested lock kind does not match that of the lock currently placed on the object.

CAUSE:
The schema was locked before the metadata backup was taken.

ACTION:
This error can be resolved by one of two actions:
1. Open the project with a locked schema in Strategy Object Manager, and then close object manager. Object Manager will force and release a new lock on the schema when connected.
2. Lock the entire project from Locking > Lock project and then unlock the project. The schema should be unlocked by going to Schema > Unlock Schema afterwards.

Comment

0 comments

Details

Knowledge Article

Published:

June 1, 2017

Last Updated:

June 1, 2017