CORBA 2.3.3 Programmer's Reference (NonStop CORBA 2.3.7+)

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
User Action: This error occurs when the subdevice 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.
2012 - Internal error. Address not found
User Action: This is a file system error. Contact your service provider.
2013 - Initialization error. CommServer cs_name listen failed
User Action: This message is generated if a Comm Server cannot listen on its configured address.
Check the Comm Server configuration using the Configuration Tool. The Comm Server will stop
itself with a failure completion status. Pathway will attempt to restart it, allowing the Comm
Server to survive any tranisient TCP or configuration database problems.
Interface Repository Error Messages (Error
numbers 2200 - 2399)
2201 - Cannot find the Contained object within current Container name
User Action: Update the IR database with the Contained object.
2202 - Cannot delete IR object from the IR database. IR object name
User Action: Make sure IR database has read/write permission, make sure Repository object is
created with update mode.
2203: Cannot create IR object name
User Action: Make sure the IR database has read/write permission.
2204 Cannot write IR object