Symptom
- After a fresh installation logging in to Central Management Console (CMC) or BI Launch Pad (BILP) which 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) - CMS.exe or boe_cmsd processes (and other BI processes) do not start after starting the Server Intelligence Agent (SIA)
- CMS logs may show below errors:
(nsclient.cpp:261) NSCLIENT: Do connection to HOSTNAME:6400. Last successful connection to
(getior.cpp:281) GetIORViaTCPIP: Error in sending request to server: XXX
(oscafactorymgr.cpp:1283) invalid IP address: HOSTNAME
TheAPSServer::RegisterApsInNameServer: Fail to connect to the APS name service(Transport error: unable to retrieve the CMS factory.)
(nsdll.cpp:142) NS_TermNameService
(nsdll.cpp:154) NS_TermNameService completely released
assert failure: (apsserver.cpp:1419). (0 : Unable to register APS with local nameserver).
SIServerController:run: Fail to initialize or uninitialize. Reason is The root server reported an error Initialization Failure.
Read more...
Environment
- SAP BusinessObjects Business Intelligence Platform 4.x (BI 4.1 / 4.2 / 4.3)
- Central Management Server (CMS)
- Windows
- Linux / Unix
Product
Keywords
verify, network, 4.2, 4.3, installation, mismatch, hostname, oscafactorymgr.cpp, Initialization, NSCLIENT, GetIORViaTCPIP , KBA , BI-BIP-INS , Installation, Updates, Upgrade, Patching , 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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview