Symptom
- The SIA remains in stopping state forever, require system restart to get it back to running state.
- The CMS.exe process is not running.
- When try to login on the CMC or through CCM - Manage server using the enterprise user got the error "Account information not recognized: Could not reach CMS hostname:6400'. Specify the correct host and port and check for network issues, please refer to SAP Knowledge Base Article 2151044 on the SAP Support Portal. (FWM 20030)"
- The other error might be seen in the event viewer log:
The root server reported an error Initialization Failure. (Reason: SAP BusinessObjects BI platform CMS: Unable to connect to the CMS system database "BO_CMS". Reason: [Microsoft][ODBC SQL Server Driver]Login timeout expiredSAP BusinessObjects BI platform CMS: Unable to connect to the CMS system database "BO_CMS". Reason: [Microsoft][ODBC SQL Server Driver]Login timeout expired CDatabase::Open failure
CMS is unstable and will shut down immediately. Reason: SAP BusinessObjects BI platform CMS: Unable to connect to the CMS system database "BO_CMS". Reason: [Microsoft][ODBC SQL Server Driver]Login timeout expired (FWB 00087
User hive is loaded by another process (Registry Lock) Process name: C:\Windows\System32\svchost.exe, PID: 3292, ProfSvc PID: 1636.
Read more...
Environment
- SAP BusinessObjects Business Intelligence (BI) Platform 4.x/2025
Keywords
CDatabase::Open failure, CMS is unstable, Authentication, SIA stopping state, Account information not recognized, svchost.exe, service account, windows ad. , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , BI-BIP-ADM , BI Servers, security, Crystal Reports in Launchpad , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview