CORBA 2.6.1 Programmer's Reference

User Action: This error occurs during direct tcp_server initialization if the
profile@ORB{host_name} key can't be retrieved from the configuration database. Verify
that the server has the correct NSDOM_CFG_DBM environment; verify that the server should be
configured as a direct tcp_server (as opposed to USE_COMM_SERVER), verify that the
configuration database contains a valid profile@ORB{host_name} key and value.
1604 -Configuration error. No port number for profile name
User Action: This scenario is the same as for Error 1603, except it is for the port_number key
instead of the address key.
1605 - Configuration error. Failed to delete actual address for profile name
User Action: This error occurs during direct tcp_server initialization when the process fails in
its attempt to delete a previously created profile@actual_tcp_address entity. Verify that
the server process has write access to the configuration database.
1606 - Configuration error. Failed to update address for profile name
User Action: This error occus occurs during direct tcp_server initialization when the process
fails to write its profile@actual_tcp_address entity. Verify that the server process has
write access to the configuration database.
1607 - GIOP Client context not found
User Action: This error occurs during the processing of a GIOP reply message if the context
associated with the corresponding request can't be found. This error indicates a serious problem.
Obtain a trace of GIOP_FW and PROXY, and contact your service provider.
1608 - GIOP Client message error
User Action: This error occurs during client-side processing of a received message if it is not a
valid GIOP message. Verify that the server is sending a valid GIOP message.
1609 - GIOP Client invalid message type
User Action: This error occurs during client-side processing of a received message if its type is not
a GIOP Reply message. Verify that the server is sending a GIOP Reply message in response to a
GIOP Request.
1610 - GIOP Server message error
User Action: This error occurs during server-side processing of a received message if its type is
not a GIOP Reply message. Verify that the client is sending a valid GIOP message.
1611 - No load_table entries
User Action: This error occurs when an LSD is attempting to pick the least busy Comm Server to
associate with a client address, if no csmap@load_table entry(ies) can be found in the
configuration database. Verify that the Comm Server pool has started successfully and verify that
the Comm Server pool process name is correct.
1612 - User exception received but not expected. Not declared in IDL
User Action: This error occurs during demarshalling of an unrecognized user exception. Verify
that all exceptions are declared in the generated *_client.h and .cpp files.