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

KB8077: ’MsiStatisticsMgr::Init() failed: project=<Project Name>, HR=0x80004005, statistics will be disabled for this project!’ message appears in the DSSErrors.log of MicroStrategy Intelligence Server 9.x and 10.x


Community Admin

• Strategy


’MsiStatisticsMgr::Init() failed: project=<Project Name>, HR=0x80004005, statistics will be disabled for this project!’ message appears in the DSSErrors.log of MicroStrategy Intelligence Server 9.x and 10.x

 
SYMPTOM:
In Strategy Intelligence Server 9.x and 10.x , statistics are not logged even though they are enabled in the project configuration. Consequently, users see the following error message in the DSSErrors.log file:
 
'ConfigManager::InitProject(): MsiStatisticsMgr::Init() failed: project=<Project Name>, HR=0x80004005, statistics will be disabled for this project!.'
 
 
CAUSE:
When Strategy Intelligence Server is started, it looks for a valid connection to the Statistics database all projects that are loaded upon startup. If there is an error when checking the connection to the Statistics database (a connection cannot be made, the database is down, the database returns an out of space error, etc.), Strategy Intelligence Server will disable the Statistics logging for that specific project and output the error mentioned above to the DSSErrors.log file.
 
 
This is done so that Strategy Intelligence Server does not continue to attempt to connect to a database that is down or that experiences difficulties when it tries to log job statistics. Attempting to connect to a database that is down or has difficulties can cause performance issues on the Strategy Intelligence Server.
 
 
ACTION:
To resolve this issue, make sure the Statistics database is back up and running (connect to it through an ODBC tool to check for active connection) and restart the Strategy Intelligence Server.
 
 
Once Strategy Intelligence Server restarts, statistics are logged again normally.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

May 27, 2017

Last Updated:

May 27, 2017