EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB42681: "The 'Project' object cannot be locked because one or more of its constituents have conflicting locks placed one them" error message appears when updating schema via Command Manager in MicroStrategy


Community Admin

• Strategy


This article addresses an error seen when updating schema via the UPDATE SCHEMA Command Manager script.

SYMPTOM:
The below error occurs when executing the script "UPDATE SCHEMA" in Strategy Command Manager.

ka0PW0000000t1JYAQ_0EM440000002HMM.png

 


"This ‘Project’ object cannot be locked because one or more of its constituents have conflicting locks placed on them.

Task(s) execution completed with errors."

NOTE:
Users can successfully update the schema manually within Developer.

ACTION:
One possible cause of this error message is outlined in KB36279 , in which Update Schema window for the mentioned project is open in Strategy Developer. The Update Schema window places a lock and prevents schema updating from Command Manager.
 
Close the Update Schema window in Strategy Developer and re-execute the command in Strategy Command Manager.
Or, unlock the schema using Strategy Developer: Schema > Unlock Schema
Workstation > Schema > Right Click on the schema > Click Unlock

ka0PW0000000t1JYAQ_0EM440000002HMN.png

 


Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

February 26, 2024