[Enterprise Extensions only]

CORBA system exception minor codes

In the CORBA model for exception handling, all exceptions can be associated with minor codes. This topic provides details of these minor codes, in hexadecimal order.

Minor codes are used in several ways:

There is not a one-to-one mapping of system exceptions to minor codes. A single minor code can be associated with several different exceptions, and the diagnostic message can be different depending on which exception was thrown.

Each minor code is a three digit hexadecimal serial number. This number is prefixed with 0x49420, which is the OMG-assigned vendor identification code for the C++ ORB provided with IBM Websphere Application Server Enterprise Services.

Note: In some cases, minor code numbers may be reported without the vendor ID. Minor codes reported from Java are in decimal point and lack the vendor ID.

Minor code numbers are unique within the scope for each system exception, but there is no restriction that minor code numbers be unique across all system exceptions.

In this topic, the description of each minor code consists of:


Minor Code number (prefixed with vendor ID) : Error Text (the text string that identifies the minor code)
Explanation: A description of the problem that caused the error.
User Response: Actions needed to resolve the problem, if appropriate.

Minor code definitions


0x49420032 : SOMDERROR_CouldNotLoadLibrary
Explanation: Client initialization cannot load a required library.
User Response: Check the log for more information.

0x49420033 : SOMDERROR_NoMemory
Explanation: A memory allocation failed.
User Response: Verify that process does not have a memory leak. Increase system resources.

0x49420034 : SOMDERROR_NotImplemented
Explanation: The invoked operation is not supported in the product or is not valid on the target object
User Response: Check that the operation being invoked and the target object run-time type are compatible. Refer to the documentation for the operation for information about restrictions.

0x49420035 : SOMDERROR_InvalidProtocolInformation
Explanation: The configuration of the communications protocol is incorrect. Supported communication protocols are TCP/IP and IPC.
User Response: Ensure that at least one valid communications protocol image was configured using system management (for either TCP/IP or IPC). Ensure that a host image was configured using the correct host name. Ensure that for each communications protocol configured, the csProfileTag and portNumber are set and that the portNumber is not using another process on the system. (The portNumber is the port on which the location service daemon listens for requests.) The csProfileTag and portNumber settings must be unique for each communications protocol. Ensure that for each server registered in the Implementation Repository, the set of supported communication protocols intersects with the set of communications protocol images configured using system management.

0x49420036 : SOMDERROR_SOMDDAlreadyRunning
Explanation: The location service daemon cannot begin listening because another process is using the port number. Probably another instance of the process is already running.
User Response: Do not attempt to start the location service daemon or terminate the other instance. If no other location service daemon is running, try reconfiguring the location service daemon to listen on a different port number. Each communications protocol is configured with a separate port number using system management.

0x49420037 : SOMDERROR_InvalidConfigSetting
Explanation: A configuration setting or environment variable was not properly set.
User Response: An error log entry indicates which configuration setting or environment variable is not properly set. If the reported variable is HOSTNAME, ensure that a host image was configured using system management. If the reported variable is SOMCBASE, ensure that the product was properly installed (SOMCBASE should be set to the directory where the product was installed.) If the reported variable is SOMCBENV, ensure that SOMCBENV has one of the following forms: D:<image-name> S:<image-name> C:<image-name> A:<image-name> where "D:" starts the location-service daemon, "S:" starts a server process, "C:" starts a client process, and "A:" starts a systems management agent process. The <image-name> is the name of a systems management image. For servers, the image name is the same as the server alias. For non-managed clients, the SOMCBENV environment variable should be set to the name of a configuration file that contains configuration settings for the process. The default configuration file somcbenv.ini is in the "etc" subdirectory of the installed product directory.

0x49420038 : SOMDERROR_HostAddress
Explanation: Cannot map a host name on a different machine to a host address.
User Response: Ensure that the host with which this process is attempting to communicate is known and can be reached via TCP/IP. Try to ping the remote host by the host name.

0x49420039 : SOMDERROR_CouldNotStartProcess
Explanation: The location daemon cannot start a server process.
User Response: Check the log for more information.

0x4942003A : SOMDERROR_CouldNotStartThread
Explanation: Cannot start a thread.
User Response: Check the log for more information. Increase system resources.

0x4942003B : SOMDERROR_NoMessages
Explanation: No request messages were pending in a server process when the server invoked CORBA::BOA::execute_next_request or CORBA::BOA::execute_request_loop with the CORBA::BOA::SOMD_NO_WAIT flag.
User Response: Wait for a request to become available, or use the CORBA::BOA::SOMD_WAIT flag to call CORBA::BOA::execute_next_request or CORBA::BOA::execute_request_loop.

0x4942003C : SOMDERROR_MarshalingError
Explanation: An error has occurred when trying to marshall or demarshall method parameters or return results as part of a remote invocation. This can occur if the process attempts to pass a IOM proxy as a method parameter or return result. Only objects that inherit from CORBA::Object_ORBProxy can be passed on cross-process invocations. It can also occur when demarshalling an inout sequence if the length of the incoming sequence is greater than the original sequence maximum. It can occur if methods are not invoked on the ServerRequest object in the correct order when using the Dynamic Skeleton Interface (DSI).
User Response: Ensure that IOM proxies are not passed as method parameters or return results. Ensure that inout sequences do not exceed the sequence maximum. If using the DSI, ensure that operations are invoked in the correct order on the ServerRequest object.

0x4942003D : SOMDERROR_CommTimeOut
Explanation: A process has timed out while waiting for a response from another process. Typically a client receives this error when the server has terminated or is hanging due to an application error.
User Response: Ensure that the other process is still active. To increase the timeout period, change the request timeout setting using system management.
Note: Setting the request timeout setting to zero results in an infinite timeout.

0x4942003E : SOMDERROR_CannotConnect
Explanation: A client process cannot connect to a server process when attempting to invoke a method on a proxy to an object residing in that server process.
User Response: Ensure that the location service daemon is running on the machine on which the server resides. Ensure that the object reference is still valid. Try to ping the remote machine to see that the two machines are connected.

0x4942003F : SOMDERROR_No_Server_Available
Explanation: A client has invoked a method on a proxy to an object residing in a server group, but no server in the server group is currently available or the server group cannot be reached. Either a method call was made on a server group aware object, but the server group has no servers configured in it. Or a method call was made on a server group aware object for which there is at least one server configured, but none of the servers that are available were selected by the configured bind policies. Can be the result of a permanent server failure or communications failure.
User Response: Configure at least one server into the server group if the server group has no configured servers. If the server group has at least one server configured, then ensure that the configured bind policies are deselecting all the available servers or the bind policy may have to be modified. Alternatively, there may be a problem communicating with one or more of the servers. Ensure that the servers in the server group are running and that there is communication between the client or server and the servers in the server group. Shut down and restart the client or server and reinitialize the application that caused the error. Alternatively, catch the error and retry the method call until a server becomes available.

0x49420040 : SOMDERROR_BadObjref
Explanation: An invalid object reference was used. For example, if the server receives a reference to an object that no longer exists or cannot be located in that server, this error is sent from a server to a client. This error can occur in a client process if an invalid string is passed to CORBA::ORB::string_to_object. This error occurs in a server if CORBA::BOA::create is called with input ReferenceData that doesn't map to any known exportable object residing in that server. The error occurs if CORBA::BOA::get_id is invoked on a nil object reference or on an object reference that has no associated ReferenceData in that server. Also, this error occurs if a server attempts to export an object reference that has no associated ReferenceData in that server, or if a non-server attempts to pass a local object as a parameter on a remote method invocation. (A " non-server" is any process that has not yet called CORBA::BOA::impl_is_ready.)
User Response: In a client process, ensure that the object which the object reference refers to still exists. Ensure that strings passed to CORBA::ORB::string_to_object have not been corrupted or truncated. There is no maximum length for an object reference string; some are larger than others. Ensure that servers do not attempt to export objects that are not handled by the application adaptor of the server. IOM proxies cannot be exported from a server.

0x49420041 : SOMDERROR_Unknown
Explanation: An unexpected error occurred during an operation.
User Response: Report the occurrence to technical support.

0x49420042 : SOMDERROR_CommunicationsError
Explanation: A communications failure occurred. Possible reasons are:
  • A process could have received an unknown or unexpected message type or message content
  • The process could have encountered a low-level communications failure in attempting to send a message or binding to a socket
  • An unexpected broken connection could have occurred.
User Response: Ensure that communications resources are functioning properly; for example, when using TCP/IP, try to ping the remote host. Ensure that the process has not failed due to an application error.

0x49420043 : SOMDERROR_ImplRepIO
Explanation: Cannot access the Implementation Repository database.
User Response: Ensure that the Implementation Repository was correctly created and configured using system management. Each host machine must have its own Implementation Repository.

0x49420044 : SOMDERROR_EntryNotFound
Explanation: Cannot find an entry in the Implementation Repository when attempting to delete, update, or locate it.
User Response: Ensure that the specified server alias or UUID matches a server that was previously registered in the Implementation Repository.

0x49420045 : SOMDERROR_ClassNotFound
Explanation: Cannot convert an IOR to an object. The class name was unknown or the proxy factory cannot be created.
User Response: Verify the class implementation and make sure that the bindings exist.

0x49420046 : SOMDERROR_ServerAlreadyExists
Explanation: A server cannot register with the location service daemon during CORBA::BOA::impl_is_ready. Another server may already be registered with the location service daemon under the server UUID. Only one instance of a particular server can be running on a given host.
User Response: Terminate the duplicate server process. If no duplicate server process is running, restart the location service daemon.

0x49420047 : SOMDERROR_CtxNoPropFound
Explanation: Cannot find a specified CORBA::Context property. This error occurs if an invalid property name was passed to CORBA::Context::delete_values.
User Response: Ensure that the specified property name exists in the context object

0x49420048 : SOMDERROR_BadParm
Explanation: An application supplied an invalid parameter to an operation.
User Response: Check the error log for a message indicating which operation was given the invalid parameter. Check the documentation for that operation and ensure that the passed parameters are valid.

0x49420049 : SOMDERROR_AuthnFail
Explanation: An application attempted to manipulate an entry in the Implementation Repository for a server that is either being managed or disabled by system management. Only entries registered using the ImplRepository interface can be updated or deleted using the ImplRepository interface. Such entries in the Implementation Repository cannot be deleted or updated using the ImplRepository programmatic interface. The error is also raised if CORBA::ImplRepository::find_impldef is used to find a server that was disabled by system management.
User Response: Manipulate the server using system management. Ensure that the server was not disabled by system management. Ensure that all entries in the Implementation Repository that are to be deleted or updated, were originally added programmatically and not by using system management.

0x4942004A : SOMDERROR_DuplicateEntry
Explanation: The application attempted to add a duplicate entry to the Implementation Repository, or attempted to update the server alias of an existing entry using a name that is not unique. The server alias need not be unique throughout the network but must be unique in each Implementation Repository.
User Response: Ensure that the server UUID and server alias of the ImplementationDef to be added or updated in the Implementation Repository are unique.

0x4942004B : SOMDERROR_Internal
Explanation: Unknown.
User Response: Report the occurrence to technical support.

0x4942004D : SOMDERROR_WrongRefType
Explanation: The wrong type of object reference was used. Probably, a client invoked an operation on an object in a server and the object did not support the invoked method. To support a given operation, a server must have been compiled and linked with the server-side C++ bindings for the interface that introduces that IDL operation. This error also occurs when a server application invokes CORBA::BOA::get_id and passes in a proxy object rather than a local object.
User Response: Ensure that a server is compiled and linked with all the server-side C++ bindings for the interfaces it exports. Ensure that a server does not pass a proxy object to CORBA::BOA::get_id.

0x4942004E : SOMDERROR_SOMDDNotRunning
Explanation: A server cannot register with the location service daemon (in CORBA::BOA::impl_is_ready), because it cannot contact the daemon. Maybe the daemon not running, or the daemon running on a port number that is different from what the server expected.
User Response: Ensure that the location service daemon is running on the same host as the server. Ensure that the port number configuration setting for each communications protocol is the same for the systems management server image and daemon image.

0x49420051 : SOMDERROR_DataConversion
Explanation: Cannot perform code set translation for character data. This results from a failure of the XPG4 functions iconv() or nl_langinfo(). It can occur if the process is using a non-standard XPG4 code set that does not map to an OSF code set. It can occur if the native code set for the process (as reported by the XPG4 function nl_langinfo) does not match the nativeCharSet configuration data of the process (which was configured using system management). It can occur if a server does not have XPG4 code set converters for the transmission code set chosen by the client process. It can occur if the char code sets configuration setting for the server contains one or more code sets for which the process cannot open (using iconv_open) XPG4 converters. It can occur if there is no common code set between the client and the server.
User Response: When using the translationEnabled configuration setting, ensure that the NLS-related configuration settings have been correctly set. Also ensure that the correct XPG4 code set converters have been installed and that all environment variables (such as LOCPATH) required by XPG4 have been properly set. Ensure that both the client and the server are using standard code sets and that there is some code set supported by both the client and the server.

0x49420052 : SOMDERROR_IRIncoherent
Explanation: An Interface Repository object references another named Interface Repository object which no longer resides in the IR database.
User Response: Contact IBM Support and report the problem.

0x49420053 : SOMDERROR_IRInternal
Explanation: An internal programming or database error has occurred.
User Response: Contact IBM Support and report the problem.

0x49420054 : SOMDERROR_IRDuplicateEntry
Explanation: Attempted to create an Interface Repository object where one already exists in the Interface Repository with either the same CORBA::RepositoryId or the same name within that container.
User Response: Change the ID (CORBA::RepositoryId) parameter that is passed to the 'create_xxxx' operation, or change the ID (CORBA::RepositoryId) value of the object already in the IR which is causing the duplicate entry error via the ID write operation. Change the name of one of the two conflicting objects within that container.

0x49420055 : SOMDERROR_IREntryNotFound
Explanation: One of the input parameters of a create_xxxx operation referenced an Interface Repository object which is not in the database.
User Response: Specify a named object that exists in the Interface Repository database.

0x49420056 : SOMDERROR_IRCannotConnect
Explanation: Cannot find or access the Interface Repository database. This occurs during a call to resolve_initial_references (with an input string of InterfaceRepository).
User Response: Ensure that the Interface Repository database exists and is properly configured. Ensure that the directory or file permissions associated with the Interface Repository database allow access by the user receiving the exception.

0x49420057 : SOMDERROR_IRInUse
Explanation: Another thread or process is updating that portion of the Interface Repository database.
User Response: Retry the Interface Repository operation that generated the exception at a later time.