CORBA 2.6.1 Programmer's Reference

cs_name@comm_server{host_name} key in the configuration database. Verify that the
Comm Server server pool has the correct NSDOM_CFG_DBM env. Also verify that the Comm
Server server pool and the configuration database names are correct.
2002 - Configuration error. CommServer name has no port number
User Action: This error occurs when a Comm Server fails to find the
cs_name@comm_server{port_number} key in the configuration database. Verify that the
Comm Server server pool has the correct NSDOM_CFG_DBM env. Also verify that the Comm
Server server pool and the configuration database names are correct.
2003 - Configuration error. Failed to set tcp_process
User Action: This error occurs when a Comm Server fails to its listening socket transport name.
Verify that cs_name@comm_server{tcp_process} is correctly configured.
2004 - NID interposed id Server Reply : ctx not found address
User Action: This error occurs as a Comm Server is relaying a reply message; the interposed
request id (also known as the New ID) does not map to the context held for a previously relayed
request.
2005 - Object key error. Bad system name
User Action: This error occurs when a Comm Server is relaying a request; the tsmp relay profile
contains a system name that is too large. Verify that the server@ORB{pathmon} value is
correct. If the value doesn't contain a system name, the generated one is in error. Capture the IOR
and contact your service provider.
2006 - Object key error. Bad pathmon name
User Action: This error is the same as Error 2005, except it applies to the pathmon process name.
Verify that the server@ORB{pathmon} value is correct.
2007 - Object key error. Bad server class name
User Action: This error is the same as Error 2005, except it applies to the server_class value.
2008 - Internal error. Address not found
User Action: This error occurs during tsmp server agent tear-down; the agent table is not
consistent. Contact your service provider.
2009 - Object key error. Bad system name
User Action: This error occurs when the file system is relaying a request; the tsmp relay profile
contains a system name that is too large. This field is generated. Capture the IOR and contact your
service provider.
2010 - Object key error. Bad process name
User Action: This error occurs when the process name is relaying a request; the tsmp relay profile
contains a system name that is too large. This field is generated. Capture the IOR and contact your
service provider.
2011 - Object key error. Bad subdev name