Previous Topic: CA CSM Fails to Start with SAF Security EnabledNext Topic: Delete Task Button Disabled on the Tasks Tab

Troubleshooting › CA CSM Fails with Exception

CA CSM Fails with Exception

Symptom:

CA CSM fails with an exception, for example:

MSM0008E - System startup failed - please see error output for further information.
Fatal error that has stopped the startup was:
or g.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create
PoolableConnectionFactory (IO error sending or receiving native data:
ca.datacom.db.DBIOException: CCICONV FAILURE:  No receiver online in
Session(connect)).

MSM0010E - CA CSM startup failed.

FATAL (main) 2011-01-12 15:05:15,098 (SystemManager.java:333): java.lang.Error:
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create
PoolableConnectionFactory (IO error sending or receiving native data:
ca.datacom.db.DBIOException: CCICONV FAILURE:  No receiver online
in Session(connect))

Reason:

The ServerName for the CA Datacom/MSM server or ApplicationID in both the CUSMAC(SRVLIB) member and the context.xml file do not match.

Solution:

Change the ServerName or the ApplicationID in either context.xml or CUSMAC(SRVLIB) so that they match.

Note: For more information about editing values in the context.xml file, see the Administration Guide.