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

KB15177: After re-starting MicroStrategy Intelligence Server using MicroStrategy Command Manager scripts, the project schema is locked


Community Admin

• Strategy


When running a script via MicroStrategy Command Manager to stop MicroStrategy Intelligence Server, the users find that when re-starting MicroStrategy Intelligence Server, the schema is locked by MicroStrategy Command Manager.

SYMPTOM:
When running a script via Strategy Command Manager to stop Strategy Intelligence Server, the users find that when re-starting Strategy Intelligence Server, the schema is locked by Strategy Command Manager.
 
Consider the following command from the command line:
 
cmdmgr -n "Strategy BI Developer Kit" -u Administrator -f c:\stop.scp -o c:\command.log
Stop.scp contains the following:
 
STOP SERVER "localhost";
The stop command is followed by the start command below:
 
cmdmgr -n "Strategy BI Developer Kit" -u Administrator -f c:\start.scp -o c:\command.log
Start.scp contains the following:
 
START SERVER "localhost";
Running these commands causes the schema to be locked by Strategy Command Manager.
 
 
ACTION:
To avoid this situation, add the following command to the script that starts Strategy Intelligence Server:
 
UNLOCK CONFIGURATION FORCE;


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017