NoServerDefinedException will not start
 Technote (troubleshooting)
 
Problem(Abstract)
When attempting to start an IBM® WebSphere® Application Server known to a Cell, the Application Server does not start, and the NoServerDefinedException error is shown in Startserver.log.
 
Cause
One possible reason for seeing this error is a discovery problem. The Deployment Manager does not know about this Application Server.
Error
TRAS0017I: The startup trace state is *=all=disabled.
ADMU3100I: Reading configuration for server: myserver
ADMU3002E: Exception attempting to process server myserver
ADMU3007E: Exception com.ibm.websphere.management.exception.NoServerDefinedException:

No configuration defined for server: myserver
at com.ibm.ws.management.launcher.LaunchCommand.<init>

    (LaunchCommand.java:131)
at com.ibm.ws.management.tools.WsServerLauncher.

    initializeRepositoryAndLauncher(WsServerLauncher.java:254)
at com.ibm.ws.management.tools.WsServerLauncher.runTool

    (WsServerLauncher.java:149)
at com.ibm.ws.management.tools.AdminTool.executeUtility

    (AdminTool.java:167)
at com.ibm.ws.management.tools.WsServerLauncher.main

    (WsServerLauncher.java:91)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main

    (WSLauncher.java:94)
 
Resolving the problem
Compare the list of servers known to the node to the list of servers in the serverindex.xml.
  1. Check the Network Deployment (ND) configuration to confirm that the servers listed in the serverindex.xml file are the same as the servers listed in the configuration.
  2. Display the contents of
    • <WAS_ND_install_root>/config/cells/cellname/nodes/nodename/servers
  3. View the file
    • <WAS_ND_install_root>/config/cells/cellname/nodes/nodename/serverindex.xml
  4. Make sure the serverName= entries in the serverindex.xml file matches the list of servers in the nodename\servers folder.
  5. If they don't match, there could be corruption in the configuration files. Contact IBM Technical Support.
  6. If they do match, go to each node configuration and compare the server directory to the list of serverName= entries in the serverindex.xml files.
  7. If the node configuration does not match, synchronize the node with the Deployment Manager.
  8. From the node command line:
    • Stop the node agent:
      stopNode.sh

    • Complete the full synchronization:
       syncNode.sh      <dmgr-host-name>
        <dmgr-SOAP_CONNECTOR_ADDRESS-port>
        [-username <uid>]
        [-password <pwd>]

    • Start the node agent:
      startNode.sh


For additional information, see technote: MustGather: Node agent and Deployment Manager discovery problems.
 
Related information
Contact WebSphere Application Server Support
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1176517
IBM Group: Software Group
Modified date: Aug 16, 2004