InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.1: XMLConfig command line interface for XML configuration >
6.6.0.2.1.5: Troubleshooting XMLConfig

6.6.0.2.1.5: Troubleshooting XMLConfig

This article describes what to do if XMLConfig fails and displays the following message at its command line.

Unable to create Initial Context. Please check name service settings:
org.omg.CORBA.COMM_FAILURE:   minor code: 3  completed: No
java com.ibm.websphere.xmlconfig.XMLConfig
{ ( -import <xml data file> ) ||
[ ( -export <xml output file> [-partial <xml data file>] ) }
-adminNodeName <primary node name>
[ -nameServiceHost <host name> [ -nameServicePort <port number> ]]
[-traceString <trace spec> [-traceFile <file name>]]
[-substitute <"key1=value1[;key2=value2[...]]">]}
In input xml file, the key(s)  should appear as $key$ for substitution.

One or more of the following conditions is likely to have caused the problem:

  • The admin server didn't start properly.
  • XMLConfig is being run remotely from the machine on which the product administrative server is installed, and the -nameServiceHost parameter has not been set to the hostname of the machine containing the administrative server.
  • The naming service port was changed from the default 900 on the application server and the -nameServicePort parameter was not set to the changed port value
  • The -nameServicePort parameter was defined, but the -nameServiceHost parameter was not.
  • If the fully qualified host name (hostname + domain) is specified for the -adminNodeName parameter, instead of the node name (short host name), expect this error:
    001.553 22f45b XMLConfig     X Unabled to export Virtual Host Data: {0}
    javax.naming.NameNotFoundException:
    

To resolve the problem:

  1. Check whether the administrative server started successfully, as described in the documentation for starting the administrative server.
  2. If the XMLConfig tool is being run remotely with respect to the machine on which the IBM Websphere administrative server is running, ensure that the -nameServiceHost (as well as the -adminNodeName) parameter are set to the host name of the remote machine.
  3. If the naming service port has been changed from the default 900 on the machine on which the administrative server is running, look in the administrative server configuration file for the parameter:
    com.ibm.ejs.sm.adminServer.bootstrapPort
    

    Set the XMLConfig -nameServicePort parameter to this port value.

  4. If you use the -nameServicePort parameter, you must also use the -nameServiceHost parameter even if you are running XMLConfig on the same machine as the administrative server.
  5. Modify the -adminNodeName parameter to use the node name, which can be found as your hostname in your TCP/IP networking configuration and also in the Websphere administrative console under "Websphere Administrative Domain."
Go to previous article: wartoxmlconfig script Go to next article: WebSphere Control Program

 

 
Go to previous article: wartoxmlconfig script Go to next article: WebSphere Control Program