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

KB484960: Unable to stop or restart the Modeling service through Services after it crashes in Windows


George Nie

Quality Engineer, Senior • MicroStrategy


This article addresses the issue where the Modeling service crashes after being overloaded with too many "active" changeset sessions. This article also provides a workaround to avoid this behavior.

Description 


After the Modeling service crashes, the

RUNNING_PID
file in
./ModelService
is not deleted, so Windows Services doesn't recognize that the Modeling service has stopped. Thus, you can no longer stop or restart the Modeling service from the Windows Services program. 
If you try to continue to call the Strategy Library APIs (either directly or via Strategy Workstation), you may get an error message stating that the Modeling service is not configured.

Why is this happening? 


The Modeling service crash depends on the machine's memory allocated to the Modeling service. For example, in a Windows machine with 16GB RAM, it takes about 120 open changesets in a few minutes to crash it. 
 

Workaround 


You can run

stop.bat
manually in command line (administrator mode) and then you should be able to refresh the correct status in Services and restart the Modeling service from Services again. The
stop.bat
file can be found in
./ModelService/bin
. 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 1, 2021

Last Updated:

April 1, 2021