SAP Knowledge Base Article - Preview

2791114 - CMS on machine <MACHINE> was stopped due to a critical error. (FWM 20031)

Symptom

  • Logging in to Central Management Console (CMC) or BI Launch Pad (BILP) reveals the following error:
    Account information not recognized: Could not reach CMS 'HOSTNAME:PORT'. The CMS on machine 'HOSTNAME' was stopped due to a critical error. (FWM 20031)

  • In the Central Management Server (CMS) logs, the below errors can be seen:

    (..\ODBCStatement.cpp:199) ExecDirect: SQL: SELECT ObjectID, Version, LastModifyTime, CRC, SI_CRYPTOGRAPHIC_KEY, Properties FROM dbo.CMS_InfoObjects7 WHERE ObjectID IN (10) ORDER BY ObjectID
    (.\dbq.cpp:1364) DBQ: Time required to read 1 objects: 0.673270 ms
    (.\dbq.cpp:1351) Unable to find object 10 in the objects read from the database (num: 0)
    DBQueue::Read: 0
    assert failure: (.\SessionImpl_InMemory.cpp:2078). (m_pUser : no message).
    [UID=0;USID=0;ID=10 ] Found object id 10 in the fail-cache.


Read more...

Environment

  • SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.0 / 4.1 / 4.2)
  • Windows
  • Linux / Unix 

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2

Keywords

1. Stop the existing SIA
2. Start up the cms in serverconsole mode following KBA:
1828536 - How to start the CMS in console mode, BI 4.x (Windows)
3. Once it's started, type:
object 10
This should retrieve no results - indicating object 10 is missing.
4. Once it starts up, run the query:
select si_id,si_name,si_kind from ci_infoobjects,ci_systemobjects,ci_appobjects where si_name='BusinessObjects_SystemAccount_dfo.xml'
This should retrieve one result - note down the SI_ID
5. Run the command:
delete <SI_ID from step 4>
6. Run again the command below to make sure it was deleted (it should now retrieve no objects):
select si_id,si_name,si_kind from ci_infoobjects,ci_systemobjects,ci_appobjects where si_name='BusinessObjects_SystemAccount_dfo.xml'
7. Type quit to exit the CMS
8. Navigate to <BOBJINSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\dfo\dfo_<CUID>
9. Copy the file BusinessObjects_SystemAccount_dfo.xml
10. Place this file in <BOBJINSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\Packages
11. Run the serverconsole command again
12. The file should disappear from <BOBJINSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\Packages
13. Once it's started in serverconsole mode, run the command:
object 10
14. There should now be an object retrieved
15. If so, type quit and start the SIA , KBA , BI-BIP-SRV , CMS / Auditing issues (excl. 3rd Party Authentication) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.