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

KB6384: ’The project is being modified by ’Username’. The Object cannot be opened until the project is no longer in use.’ warning message appears when opening objects or create new ones in MicroStrategy Developer 9.4.1 and 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


’The project is being modified by ’Username’. The Object cannot be opened until the project is no longer in use.’ warning message appears when opening objects or create new ones in MicroStrategy Developer 9.4.1 and 10.x

SYMPTOM
When users try to access objects in Strategy Developer 9.4.1 and 10.x, they see the following warning message:

ka02R000000kW3rQAE_0EM440000002GBC.gif


The project is being modified by 'Username'. The Object cannot be opened until the project is no longer in use.

 
However no user has currently an open session nor has the user locked the schema.
 
CAUSE
There may be different causes for this issue to occur. In fact, the project or parts of the project are locked by the locking Schema functionality to ensure that users do not modify the same schema objects at the same time. If a user who worked on Schema objects or with Strategy Administrator - Object Manager logs out successfully, the automatic Schema lock should be disabled. However, if the session ends unexpected (e.g., Application or Operation System crashes for any reason) the schema lock may still be active. As the Schema lock is stored in the metadata, a restart of the Strategy Intelligence Server would not help in this case.
 
ACTION
To resolve this issue, users may follow the steps below:

  • Make sure that the Strategy Administrator user is disconnected in all 3-tier and 2-tier modes sessions.
  • Open Strategy Administrator - Object Manager.
  • Login as Administrator to the 3-tier mode project that causes the locking issues; the following screen appears:
ka02R000000kW3rQAE_0EM440000002GBE.gif
  • Click on 'Yes'
  • The old lock will be deactivated and a new lock set up for the Administrator who just logged in.
  • In Strategy Administrator - Object Manager, disconnect from the project source. The lock will be release successfully
  • In Strategy Developer, connect with the user. Now, this user should be able to access the objects in Strategy Developer in write mode.

Comment

0 comments

Details

Knowledge Article

Published:

May 10, 2017

Last Updated:

May 10, 2017