1658653 - XI 3.1 - CMS does not come up after the SIA is started

Symptom

After the Server Intelligence Agent (SIA) is started, the Central Management Server does not startup
No errors are logged under the Event Viewer
Starting the SIA with -trace in the command-line, the SIA scans for the list of CMS and stalls while "Connecting" to a CMS following a successful ping on it:

2011-11-28 10:46:16.893 INFO Thread-0                 server query string = SELECT SI_CUID,SI_UPDATE_TS,SI_EXPECTED_RUN_STATE_TS,SI_FRIENDLY_NAME,SI_SERVER_IOR,SI_SERVER_IS_ALIVE,SI_EXPECTED_RUN_STATE,SI_AUTOBOOT,SI_ENTERPRISENODE,SI_CONFIGURED_CONTAINERS,SI_HOSTED_SERVICES,SI_SERVER_KIND,SI_SERVER_NAME,SI_PID FROM CI_SYSTEMOBJECTS WHERE (si_obtype=16) AND (CHILDREN ("si_name='EnterpriseNode-Server'", "(si_cuid = 'AXLFTdaDyVNOi8zP7iwI59I')") OR (si_server_kind='aps')).
2011-11-28 10:46:16.893 INFO Thread-0                 Adding HOSTNAME1:6400.
2011-11-28 10:46:16.893 INFO Thread-0                 Adding HOSTNAME2:6400.
2011-11-28 10:46:16.893 DEBUG Thread-0                 getCMSNames: cmsNames.size() = 2
...
2011-11-28 10:46:20.075 INFO InfoStore Agent          Ping to HOSTNAME2:6400 succeeded.
2011-11-28 10:46:20.075 INFO InfoStore Agent          Connecting to HOSTNAME2:6400.

Environment

Business Objects Enterprise XI 3.1 SP4 (all versions)
Windows (All versions)

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , 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.