NonStop DOM Error Messages
Subtopics
The following messages are errors that the NonStop DOM system components can generate. Listed in numerical order, the messages include a "User Action," which can give you an idea as to the cause of the error and how you might try to fix the problem. To view these message, you must have an EMS template file configured with NonStop DOM.
- 1100 - Event FrameWork error
- User Action: This error occurs when some notable event occurs in the Event FrameWork. The detailed error text explains the error in more detail.
- 1202 - Attempted delete of non-existent record
- User Action: No action required, this message is never issued.
The original intent was to inform the user of an attempt to delete a non-existing record.
- 1203 - Get of first record failed
- User Action: This message is issued if NonStop DOM fails to read the first record in a database. This might indicate a corrupt database.
- 1204 - Attempt to get next record failed: Key
<xyz> Failed
- User Action: An I/O error occurred in attempting to access the next record. This is due to an operating system error; please contact your Tandem representitive if you receive this message.
- 1206 - Attempt update failed: Key
<xyz> Failed
- User Action: An I/O error occurred in attempting to access the next record. This is due to an operating system error; please contact your Tandem representitive if you receive this message.
- 1209 - Failed to create database: FILE_CREATE
<name>
- User Action: An attempt to create a database failed. Some possible reasons might be the file system might be full, the user might not have proper permissions to update the file, or the database filename might not be correctly spelled.
- 1210 - Failed to open database: Cannot open database file
<name>. Aborting.
- User Action : Five attempts have been made to open a database named
<name> with unsuccessful results. Check the name, permissions and filecode (the filecode type should be 426).
- 1212 - Attempted delete of database failed: Delete for database failed:
<name>
- User Action: Unable to delete the requested database. Check the database permissions or the number of existing opens for the database.
- 1401 - Unable to open Trace file: Trace File =
<name>
- User Action: Make sure process opening the trace file has the access permission to the trace file.
- 1402 - Unable to open Trace file: Trace File =
<name>
- User Action: Make sure process has the write permission to the trace file.
- 1403 - Unable to read from Trace file: Trace File =
<name>
- User Action: Make sure process has the read permission to the trace file.
- 1404 - Unable to create Trace file: Trace File =
<name>
- User Action: Make sure process has permission to create the trace file.
- 1405 - Unable to lock Trace file record: Trace File =
<name>
- User Action: Make sure process has permission to write to the trace file.
- 1406 - Unable to unlock Trace file record: Trace File =
<name>
- User Action: The record is locked by another process.
- 1407 - Trace file is corrupted. Write on Trace file failed: Trace File =
<name>
- User Action: Delete the trace file. A new trace file will be created.
- 1601 - Configuration error. No tcp host name for LSD
<name>
- User Action: This error occurs during tcp_server initialization when the lsd1@actual_tcp_address{host_name} key can't be retrieved from the configuration database. Verify the server has the correct NSDOM_CFG_DBM environment; verify the configuration database contains a valid lsd1@actual_tcp_address entity. This entity is created during execution of the configure script.
- 1602 - Configuration error. No tcp port number for LSD
<name>.
- User Action: This is the same scenario as Error 1601, except it is for the for port_number key instead of the address key.
- 1603 - Configuration error. No host name for profile
<name>
- 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 the server has the correct NSDOM_CFG_DBM environment; verify the server should be configured as a direct (as opposed to USE_COMM_SERVER) tcp_server, verify 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 is the same scenario as 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 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 @actual_tcp_address entity. Verify 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 Tandem Computers, Inc, representitive.
- 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 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 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 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 the Comm Server pool has started successfully and verify the Comm Server pool process name is correct (see default.db).
- 1612 - User exception received but not expected. Not declared in IDL.
- User Action: This error occurs during demarshalling of an unrecognized user exception. Verify all exceptions are declared in the generated *_client.h and .cpp files.
- 1613 - Expected null for object key
<name>
- User Action: This error is generated when a POA is creating an object reference if the proxy's object key is not null.
- 1614 - GIOP Proxy marshalling 0 profiles
- User Action: This error occurs during the marshalling of an object reference, either as part of object_to_string or generating the response data for an out param or result, and there are no protocols enabled. Verify the profile used with the process is present in the configuration database. Verify the configured profile contains at least one server protocol (eg tcp_server, tsmp_server, fs_server).
- 1615 - GIOP Proxy demarshal - 0 profiles!
- User Action: This error occurs during the demarshalling of an object reference, either as part of string_to_object or demarshalling param or return value, if the reference contains 0 profiles. Verify the application that generated the reference is run with a valid profile. Verify the application that generated the reference has at least one server protocol (e.g. tcp_server, tsmp_server, fs_server) configured.
- 1618 - Object key error. Bad system name
<name>
- User Action: This error occurs during the demarshalling of an fs or tsmp profile if the system name is too long. Verify the reference has a valid system name using showior. If it is a file system profile, or a tsmp profile where the configured pathmon value does not contain a system name, the name has been generated for you–contact your Tandem representivite.
- 1619 - Object key error. Bad pathmon name
<name>
- User Action: This error occurs during demarshalling of a tsmp profile if the pathmon name is too long. Verify the referenced application's <profile>@ORB{pathmon} value is correct.
- 1620 - Object key error. Bad server class name
<name>
- User Action: This error occurs during the demarshalling of a tsmp profile if the server class name is too long. Verify the referenced application's <profile>@ORB{server_class} value is correct.
- 1621 - Configuration error. No pathmon for profile
<name>
- User Action: This error occurs during tsmp_server initialization if the <profile>@ORB{pathmon} key-value is not found. Verify <profile>@ORB is correct in the configuration database.
- 1622 - Configuration error. No server class for profile
<name>
- User Action: This error occurs during tsmp_server initialization if the <profile>@ORB{server_class} key/value is not found. Verify <profile>@ORB is correct in the configuration database.
- 1623 - Object key error. Bad process name
<name>
- User Action: This error occurs during the demarshalling of a file system profile if the process name is too large. This field is generated by NSDOM. This error can indicate a serious error. Capture the ior and contact your Tandem representitive.
- 1624 - Oject key error. Bad subdev name
<name> -
User Action: This error occurs during demarshalling of a file system profile if the subdevice field is too long. This field is generated by NSDOM. This error can indicate a serious error. Capture the ior and contact your Tandem representitive.
- 1630 - demarshalled invalid policy list length
demarshalled invalid string length
demarshalled invalid encap length
demarshalled invalid repository id length
demarshalled invalid operation length
demarshalled invalid principal length
demarshalled invalid sequence length
- User Action: This error occurs if a demarshalled length is larger than reasonable. Verify the data is not corrupt.
- 2001 - Configuration error. CommServer
<name> has no host name
- User Action: This error occurs when a comm server fails to find the <cs name>@comm_server{host_name} key in the configuration database. Verify the Comm Server server pool (see the nsdstart script) has the correct NSDOM_CFG_DBM env. Also verify the Comm Server server pool (see nsdstart) 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 the Comm Server server pool (see the nsdstart script) has the correct NSDOM_CFG_DBM env. Also verify the Comm Server server pool (see nsdstart) 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 <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 (aka 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 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 Tandem representitive.
- 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 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 Tandem representitive.
- 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 Tandem representitive.
- 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 Tandem representitive.
- 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 Tandem representitive.
- 2012 - Internal error. Address not found
- User Action: This is a file system error. Contact your Tandem representitive.
- 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.
- 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
- User Action: Make sure the IR database has read/write permission.
- 2205: Cannot insert key/value for IR object
- User Action: Make sure the IR database has read/write permission.
- 2206: Cannot read IR object from the IR database. IR object
<name>
- User Action: Make sure the IR database has read permission.
- 2207: IR object type is invalid for the operation
- User Action: Make sure the IR object is of right type to invoke the operation.
- 2208 Cannot initialize IR database
- User Action: For read mode, make sure the IR database exists and has read permission. For update mode, make sure you have the permission to create and write to the database.
- 2209: Invalid Container for the Contained object
- User Action: Make sure to put the Contained object into the right Container object.
- 2210: Cannot find IR object in the IR database. IR object
<name>
- User Action: None
- 2211: Later version of the IR object already exists. IR object
<name>
- User Action: None
- 2601 - push_to_consumer got system exception when tried to 'push' <exception#>
- User action: The Event Service was unable to sucessfully interact with a an application provided push consumer. The push consumer did not receive an event. The event service ceases to try to interact with the push consumer. Verify that no unexpected error occurred in an application provided push consumer. If the the push consumer correctly ceased to exist, no further action is necessary. For best results, the push consumer should be be reworked to correctly disconnect from the event channel before exiting. If the push consumer process failed, restart it and have it reregister with the event channel.
- 2602 - pull_to_supplier got system exception when tried to 'pull' or 'try_pull' <exception#>
- User action: The Event Service was unable to sucessfully interact with an application provided pull supplier. An event service consumer may not have obtained an event as expected. If a "comm failure" exception was raised, the event service ceases to try to interact with the offending pull supplier. Verify that no unexpected error occurred in an application provided pull supplier. If the the pull supplier correctly ceased to exist, no further action is necessary. Otherwise, if a comm failure occurred, the pull supplier should be restarted and reregistered with the event channel. If there was an exception other than a comm failure, the event channel will continue to try to interact with the pull supplier. If further errors occur, restart the pull supplier.
- 2603 - pull_from_supplier got user exception when tried to 'pull' or 'try_pull' <exception#>
- User action: This error is logged for information purposes; it has no effect on the Event Service. In response to a 'pull' or 'try_pull' request, an application provided pull supplier should not produce any user exception other than 'Disconnected'. Rewrite the application so that it does not generate the offending user exception.
- 2604 - GetEvent encountered inconsistency in saved events
- User action: An event requested by a consumer may not be available.
The event channel is unable to deliver a specific event but will recovers and deliver subsequent events.
- 2605 - release_proxy could not find object to be released
- User action: The event channel encountered an internal consistency problem but recovered automatically. If this problem occurs frequently contact Tandem support.
- 2606 - EventService could not obtain Root Name Context
- User action: The Event Service object reference was not placed in Naming Service. If this error is not corrected, application programs will be unable to query the Naming Service for an Event Service object reference. Verify correct configuration for Naming Service. Make sure Naming Service is operational. Verify that root name context for Naming Service appears in the configuration database. After correcting Naming Service errors, restart the Event Service.
- 2801 - Could not execute resolve_initial_references successfully
- User Action: Internal error, contact your Tandem representitive.
- 2802 - Cannot get Naming Database name from configuration database
- User Action: Set the 'DatabaseName' value in the NS@name_service_settings entity.
- 2803 - Could not create POA [NamingContextPOA' | 'BindingIteratorPOA']
- User Action: Internal error, contact your Tandem representitive.
- 2804 - Could not delete record from Naming database
- User Action: When trying to invoke the destroy method on a naming context object, it is unable to delete the naming context record from the naming database. This indicates a possible corruption of the naming database. Purge and reconfigure the naming database.
- 2805 - Could not initialize Naming database
<name>
- User Action: Possible database corruption, purge database and rerun initialization script.
- 2806 - Could not create Naming Service reference
- User Action: Internal error, contact your Tandem representitive.
- 2807 - Could not create Naming Service stringified reference
- User Action: Internal error, contact your Tandem representitive.
- 2808 - Cannot save Name Service IOR in config database
- User Action: Check that the configuration database file exists and the user has correct access.
- 2809 - Could not convert string IOR to object
- User Action: When trying to resolve a name, the stringified objref does not successfully resolve to an object with the orb's string_to_object method. This indicates that the object reference is no longer a valid object reference. Invoke the rebind method to bind the name to a new valid object reference.
- 2810 - Cannot set Servant Manager
- User Action: Internal error, contact your Tandem representitive.
- 2811 - Could not activate POA
- User Action: Internal error, contact your Tandem representitive.
- 2812 - Could not narrow to PortableServer::POA
- User Action: When invoking the list method on a naming context, it cannot successfully narrow an object returned from the orb's resolve_initial_references("RootPOA") method to a PortableServer::POA. This is an internal error.
- 2815 - Could not insert record into naming database
- User Action: This error message will also report the binding name component id of "NEW_CONTEXT" if the error was generated when you were attempting to create a new context. Check that naming database file exists and the user has has write access.
- 2817 - Could not narrow to CosNaming::NamingContext
- User Action: Internal error, contact your Tandem representitive.
- 2819 - Could not get timestamp from NamingContext
- User Action: Internal error, contact your Tandem representitive.
- 2821 - Could not create CosNaming::NamingContext
- User Action: Internal error, contact your Tandem representitive.
- 2822 - Could not find POA ['NamingContextPOA' | 'BindingIteratorPOA']
- User Action: Internal error, contact your Tandem representitive.
- 2823 - Could not create reference with ID
- User Action: Internal error, contact your Tandem representitive.
- 2824 - Could not get record from naming database
Could not find CosNaming::NamingContext start record in database.
- User Action: Check that the naming database file exists and the user has read permission. If there is no optional message, the target naming context object does not exist, which may indicate an internal error has occurred.
- 2825 - Could not initialize Naming database.
<name> already exists
- User Action: The ns_init program expects that the naming database does not exist. Purge the naming database and rerun ns_init.
- 2829 - Cannot set key cursor in CosNaming::BindingIterator
- User Action: Internal error, contact your Tandem representitive.
- 2830 - Cannot set alternate key in CosNaming::BindingIterator
- User Action: Internal error, contact your Tandem representitive.
- 2831 - Could not activate CosNaming::BindingIterator
- User Action: Internal error, contact your Tandem representitive.
- 2836 - Cannot unbind
<name>
- User Action: Check that the naming database file exists and the user has write access.
Event Framework Messages