Java™ Naming and Directory Interface (JNDI) - Naming Services Error Messages
 Technote (FAQ)
 
Problem
This document highlights some of the error messages mentioned in the problem determination guide for JNDI - Naming Services.
 
Solution

NMSV0001W: NameServer already initialized, ignoring this request to initialize again
Explanation: The name server should be initialized only once, but there was an attempt to initialize it a second time.
User Response: This message is to aid in problem diagnosis and can be ignored if no external symptoms are experienced. If this message accompanies name server startup problems, please report this problem to IBM support.

NMSV0002W: WsnNameService bootstrap object created with no properties.
Explanation: No properties were supplied to the name server to create a bootstrap object.
User Response: This message is to aid in problem diagnosis and can be ignored if no external symptoms are experienced. If there is a problem starting the name server, please report this event to IBM support.

NMSV0003E: Name server initialization failed. Cannot obtain host name for this host.
Explanation: The name server could not be initialized. An error occurred while attempting to obtain the hostname for the name server's local host.
User Response: This error is an internal error. Please contact IBM support.

NMSV0004E: Name server initialization failed. Cannot initialize database tables.
Explanation: The name server could not be initialized. The database tables, used to store persistent name server data, could not be initialized.
User Response: Make sure that the database server is running and that the WebSphere® Application Server database exists. Confirm that a connection can be made to the database using the user id and password that WebSphere is configured to use.

NMSV0005E: Name server initialization failed. Cannot create the LDAP name tree.
Explanation: The name server could not be initialized. The LDAP directory space, used to store persistent name server data, could not be initialized.
User Response: This error is an internal error. Please contact IBM support.

NMSV0006E: Name server initialization failed. Name server implementation type of "{0}" is not supported in this release.
Explanation: The name server could not be initialized. WebSphere is configured to use a name server implementation that is not supported in this release.
User Response: This error is an internal error. Please contact IBM support.

NMSV0007E: Name server initialization failed. Name server implementation type of "{0}" is not recognized as a valid type.
Explanation: The name server could not be initialized. WebSphere is configured to use a name server implementation that is not recognized.
User Response: This error is an internal error. Please contact IBM support.

NMSV0008E: Name server initialization failed. Could not create a root context IOR. The name server implementation type is "{0}".
Explanation: The name server could not be initialized. The root context object could not be converted to an IOR.
User Response: This error is an internal error. Please contact IBM support.

NMSV0009E: Name server initialization failed. Unable to create name server bootstrap object.
Explanation: The name server could not be initialized. The name server bootstrap object could not be created.
User Response: This error is an internal error. Please contact IBM support.

NMSV0010E: Name server initialization failed. Initialization of the WLM Bootstrap Service failed.
Explanation: The name server could not be initialized. An error occurred while attempting to initialize the WLM Bootstrap Service.
User Response: This error is an internal error. Please contact IBM support.

NMSV0011E: Unable to start Bootstrap Server. The most likely cause
is that the bootstrap port is already in use. Please ensure that no servers or other processes are already using the bootstrap server
port.
Explanation: Make sure the bootstrap port is not already in use by any other server processes. This error can occur when the WebSphere name server has already been started. Otherwise, this error is an internal error. Please contact IBM support if the above actions do not correct the problem.
User Response: This error is an internal error. Please contact IBM support.

NMSV0012E: Name server initialization failed. Cannot create the CosNaming name tree.
Explanation: The name server could not be initialized. The CosNaming name tree structure could not be initialized.
User Response: This error is an internal error. Please contact IBM support.

NMSV0013E: Name server initialization failed. Method getInitialContextRdbBootstrap failed or called in error.
Explanation: The name server could not be initialized. The getInitialContextRdbBootstrap method was either called when not in RDB Name Server Bootstrap mode or it was unable to create the InitialContext.
User Response: This error is an internal error. Please contact IBM support.

NMSV0014E: Name server initialization failed. Attempt to bind an
object prior to initialization completing.
Explanation: The name server could not be initialized. The RDB Name Server has not yet been fully initialized, but was called to bind an object that was not one of the Name Service EJBs.
User Response: This error is an internal error. Please contact IBM support.

NMS0015E: Name server initialization failed. Could not build the System Name Space.
Explanation: The name server could not be initialized. There was an unrecoverable NamingException when building the System Name Space.
User Response: This error is an internal error. Please contact IBM support.

NMSV0016E: Internal implementation error. Unexpected InvalidNameException thrown by WsnName while converting an internally generated name string "{0}" to a CosName. Throwing a CosNaming InvalidName exception.
Explanation: The CosNaming name server initialization process cannot convert a name that was internallygenerated to the CosNaming name format.
User Response: This error is an internal error. Please contact IBM support.

NMSV0100E: new_context: Unbound context instances not allowed. Throwing NO_IMPLEMENT exception.
Explanation: The method, new_context, part of the CosNaming::NamingContext interface, is not supported.
User Response: A client program invoked the new_context method, which is not supported. Clients should use the bind_new_context method.

NMSV0101E: The name syntax property "{0}" is set to an unrecognized value of "{1}".
Explanation: An invalid name syntax was specified.
User Response: This error is an internal error. Please contact IBM support.

NMSV0102E: Internal implementation error. Unexpected InvalidNameException thrown by WsnName while converting the internally stored INS name string "{0}" to a CosName. Ignoring the exception and setting the name to an empty name.
Explanation: The CosNaming name server cannot convert a name stored in an internal format to the CosNaming name format.
User Response: This error is an internal error. Please contact IBM support.

NMSV0103E: A zero-length CosNaming::NameComponent array was specified. Throwing InvalidName exception.
Explanation: An empty name (zero name components) was passed to the CosNaming server. Empty names are not valid.
User Response: If the CosNaming client is a customer-provided application, this is a user error. If the CosNaming client is WebSphere's CosNaming JNDI plug-in (i.e., a WebSphere context factory was used to create an initial context), this is an internal error and should be reported to IBM support.

NMSV0104E: CosNaming::NameComponent[{0}] contains a null id or kind field. Throwing InvalidName exception.
Explanation: A component in a name passed to a method in the WebSphere name server implementation of CosNaming::NamingContext contained a null id or kind field. A null value for an id or kind field is invalid.
User Response: If the CosNaming client is a customer-provided application, this is a user error. If the CosNaming client is WebSphere's CosNaming JNDI plug-in (i.e., a WebSphere context factory was used to create an initial context), this is an internal error and should be reported to IBM support.

NMSV0105E: Cannot convert a CosName to a valid INS name.
Explanation: The CosNaming name server could not convert a CosNaming name to its internal form.
User Response: This error is an internal error. Please contact IBM support.

NMSV0106E: Target context type of "{0}" is not the expected type.
Explanation: The CosNaming name server encountered an unknown implementation of CosNaming::NamingContext.
User Response: This error is an internal error. Please contact IBM support.

NMSV0107E: An unexpected error occurred. Mapping to CORBA UNKNOWN.
Explanation: Some unexpected error occurring which processing a CosNaming name server request.
User Response: See the trace output for more details about the origin of the problem.

NMSV0108E: An error occurred attempting to create database tables.
Explanation: The database tables used by the name server to store name space data could not be created. The cause is probably specific to the relational database manager being used.
User Response: See the trace output for more details about the origin of the problem.

NMSV0109E: CosNaming server caught exception: AdapterAlreadyExistsException.
Explanation: The CosNaming name server encountered a fatal error during startup.
User Response: This error is an internal error. Please contact IBM support.

NMSV0110E: CosNaming server caught exception: InvalidServantException.
Explanation: The CosNaming name server encountered a fatal error during startup.
User Response: This error is an internal error. Please contact IBM support.

NMSV0301E: A lookup of "{0}" failed.
Explanation: An error occurred during deserialization of a JNDI context for a local name space, such as a java:URL name space. This error is most likely to occur during reactivation of an Enterprise JavaBean™ deployed on an application server.
User Response: This error is an internal error. Please contact IBM support.

NMSV0302E: NamingManager.getURLContext returned a null Context for the scheme "{0}".
Explanation: A URL was passed to a JNDI Context method, which then invoked the JNDI Naming Manager to return the Context identified by the URL. The Naming Manager method which was invoked returned a null value.
User Response: This problem is probably the result of an incorrect configuration. Make sure that the factory for the scheme of the specified URL can be located from the value of the property, java.naming.factory.url.pkgs, found in the Context's environment.

NMSV0303E: Exception occurred in NamingManager.getURLContext for the scheme "{0}".
Explanation: A URL was passed to a JNDI Context method, which then invoked the JNDI Naming Manager to return the Context identified by the URL. The Naming Manager invocation failed.
User Response: This problem is probably the result of an incorrect configuration. Make sure that the factory for the scheme of the specified URL can be located from the value of the property, java.naming.factory.url.pkgs, found in the Context's environment. The trace output may contain additional diagnostic information.

NMSV0304W: There was an attempt to set the java URL name space accessor more than once.
Explanation: This is an internal error. The Java URL name space accessor should be initialized only once, but there was an attempt to initialize it a second time.
User Response: This message is to aid in problem diagnosis and can be ignored if no external symptoms are experienced. If this message accompanies problems using java: URL names in java.naming.Context method calls, please report this problem to IBM support.

NMSV0305E: A NamingException occurred while getting the next object in the UrlBindingEnumeration
Explanation: Some error occurred while processing the method, next, in the NamingEnumeration returned from a URL context.
User Response: This error is an internal error. Please contact IBM support.

NMSV0306E: The scheme or package name was not set.
Explanation: An error occurred while processing a URL-based name space.
User Response: This error is an internal error. Please contact IBM support.

NMSV0401W: The name "{0}" is invalid.
Explanation: The LDAP plug-in for JNDI could not perform an internal name conversion. This is an internal error.
User Response: If incorrect results are accompanied by this message, please contact IBM support.

NMSV0402E: Cannot convert the JNDI name "{0}" to an LDAP name string.
Explanation: A JNDI name passed to the LDAP plug-in for JNDI could not be converted to an LDAP name. This is probably an internal error.
User Response: This error is an internal error. Please contact IBM support. As a work-around, use a different name if possible.

NMSV0403E: Error occurred while serializing context object.
Explanation: An error occurred during serialization of a JNDI context for an LDAP-based name space.
User Response: This error is an internal error. Please contact IBM support.

NMSV0404E: Error occurred while deserializing context object.
Explanation: An error occurred during deserialization of a JNDI context for an LDAP-based name space.
User Response: This error is an internal error. Please contact IBM support.

NMSV0501W: Ignored an InvalidPropertyName exception from the CosNaming name server.
Explanation: An internal error occurred during a JNDI lookup.
User Response: If this warning message is accompanied by incorrect JNDI lookup results, please context IBM support to report this problem.

NMSV0502W: The class "com.ibm.ejs.ns.jndi.CNInitialContextFactory" has been deprecated. It has been replaced with "com.ibm.websphere.naming.WsnInitialContextFactory".
Explanation: The initial context factory for WebSphere has changed. The old one will work, but some time in the future it will no longer be available.
User Response: Begin using the new initial context factory as soon as possible.

NMSV0601E: Naming Service unavailable. Null initial context returned from ORB.
Explanation: The initial context returned from the ORB was null.
User Response: This error is an internal error. Please contact IBM support.

NMSV0602E: Naming Service unavailable. A communications error occurred.
Explanation: A connection to the name server could not be made when attempting create an initial context.
User Response: The most like causes are that the provider URL is incorrect or that the name server identified by the provider URL is not running. Make sure that the name server is running and that the host and port in the provider URL are correct. Also, make sure that the host identified in the provider URL can be accessed from the machine on which the JNDI client is running. Refer to the trace output accompanying this message for more information about the root cause.

NMSV0603E: Naming Service unavailable. Could not get the root context.
Explanation: An unknown error occurred while attempting to obtain the initial context from the ORB.
User Response: For more information about the root cause, refer to any additional trace output accompanying this message.

NMSV0604E: Exception thrown in Referenceable.getReference().
Explanation: While processing a JNDI bind or rebind operation on a javax.naming.Referenceable object, a call to the method, getReference(), on the object resulted in an exception.
User Response: The Referenceable object could not be processed for some unknown reason. Check the trace output accompanying this message for more details on the root cause.

NMSV0605E: Exception thrown in NamingManager.getObjectInstance().
Explanation: While processing a JNDI lookup or listBindings operation on a javax.naming.Reference object, a call to the JNDI Naming Manager to process the object failed. It is possible that some class file required to process the Reference object cannot be found in the classpath. It is also possible that a factory for the Reference object could not be found, based on the value for the property java.naming.factory.object found in the JNDI context's environment.
User Response: Make sure that the classpath and java.naming.factory.object property setting are correct. Check the trace output accompanying this message for more details on the root cause.

NMSV0606E: Object is not of any type which can be bound.
Explanation: The JNDI bind or rebind method was passed an object which is of a type that cannot be bound. Allowed object types include CORBA objects (which includes EJBs deployed to WebSphere), JNDI contexts of the same type as the context object being invoked, javax.naming.Referenceable, javax.naming.Reference, and java.io.Serializable.
User Response: Attempt to bind or rebind only objects of the above types.

NMSV0607E: The Context at name path "{0}" was passed a null name to the method "{1}".
Explanation: A JNDI context method was passed a null name. Null names are not valid.
User Response: Use an appropriate name for the desired JNDI operation.

NMSV0608E: The Context at name path "{0}" was passed an empty name to the method "{1}".
Explanation: A JNDI context method was passed an empty name. JNDI context methods except for lookup, list, and listBindings, do not accept empty names.
User Response: Use an appropriate name for the desired JNDI operation.

NMSV0901E: An unexpected error occurred.
Explanation: Some unexpected error occurred.
User Response: Check any trace output accompanying this message for additional information. This is very possibly an internal error. If the problem cannot be resolved from the trace output, please contact IBM support.

NMSV0902E: An error occurred while serializing an object.
Explanation: An error occurred while attempting to serialize an object. This error probably occurred during a JNDI bind or rebind operation.
User Response: One possible cause is that some object encountered during the serialization process is not serializable. For more information about the root cause, see the trace output which accompanies this message.

NMSV0903E: An error occurred while deserializing an object.
Explanation: An error occurred while attempting to deserialize an object. This error probably occurred during a JNDI lookup or listBindings operation.
User Response: The most likely cause for this problem is not having the required class or classes in the JNDI client classpath. The trace output should contain more details, such as the class name that could not be found.

NMSV0904W: Ignored InvalidNameException while converting a CosName to a String.
Explanation: A name conversion performed for internal processing failed.
User Response: This is an internal error. This message is to aid in problem diagnosis and can be ignored if no external symptoms are experienced. If this message accompanies problems occurring with JNDI method calls, please report this problem to IBM support.

NMSV0905E: Failed to create Class object for the class "{0}".
Explanation: An error occurred during internal processing.
User Response: This error is an internal error. Please contact IBM support.

NMSV0906E: Could not create an instance of the class "{0}".
Explanation: An error occurred during internal processing.
User Response: This error is an internal error. Please contact IBM support.

NMSV0907E: Could not invoke method "{0}" on object of type "{0}".
Explanation: An error occurred during internal processing.
User Response: This error is an internal error. Please contact IBM support.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > JNDI/Naming
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1054715
IBM Group: Software Group
Modified date: Jan 5, 2004