Topic
14 replies Latest Post - ‏2011-11-30T08:11:47Z by JohnnyKnoxville
SystemAdmin
SystemAdmin
11979 Posts
ACCEPTED ANSWER

Pinned topic Server server1 failed to start

‏2005-01-29T14:44:02Z |
Hi,
I have just installed WSAD 5.1 on Windows XP Professional box.when I try to start the server,it throws
me following error:

1/29/05 8:39:30:906 CST 3eb5ca6b WsServer E WSVR0003E: Server server1 failed to start
com.ibm.ws.exception.RuntimeError: Unable to initialize the Name Service
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:402)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Caused by: com.ibm.ws.naming.distcos.NameSpaceConstructionException: instantiateNC: Unexpected exception encountered
at com.ibm.ws.naming.distcos.NameSpaceBuilder.instantiateNC(NameSpaceBuilder.java:1212)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.createRootNC(NameSpaceBuilder.java:1108)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.buildNameSpace(NameSpaceBuilder.java:309)
at com.ibm.ws.naming.distcos.NSBSingleAppSvr.buildNameSpace(NSBSingleAppSvr.java:78)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:388)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:79)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:43)
at java.lang.reflect.Constructor.newInstance(Constructor.java:313)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.instantiateNC(NameSpaceBuilder.java:1205)
... 15 more
Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:667)
at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:583)
at com.ibm.rmi.iiop.TransportManager.initTransports(TransportManager.java:141)
at com.ibm.rmi.iiop.TransportManager.getServerIIOPProfile(TransportManager.java:148)
at com.ibm.CORBA.iiop.ORB.getTransportProfile(ORB.java:3272)
at com.ibm.ejs.oa.EJSRootOAImpl.registerServant(EJSRootOAImpl.java:380)
at com.ibm.ejs.oa.EJSOAImpl.registerServant(EJSOAImpl.java:254)
at com.ibm.ws.naming.distcos.ServantManagerImpl.registerContext(ServantManagerImpl.java:183)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.<init>(WsnOptimizedNamingImplBase.java:220)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.<init>(WsnOptimizedNamingImpl.java:182)
at com.ibm.ws.naming.distcos.WsnDistributedNC.<init>(WsnDistributedNC.java:116)
at com.ibm.ws.naming.distcos.ReadOnlyNC.<init>(ReadOnlyNC.java:59)
... 20 more
  • Begin backtrace for nested exception
com.ibm.ws.naming.distcos.NameSpaceConstructionException: instantiateNC: Unexpected exception encountered
at com.ibm.ws.naming.distcos.NameSpaceBuilder.instantiateNC(NameSpaceBuilder.java:1212)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.createRootNC(NameSpaceBuilder.java:1108)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.buildNameSpace(NameSpaceBuilder.java:309)
at com.ibm.ws.naming.distcos.NSBSingleAppSvr.buildNameSpace(NSBSingleAppSvr.java:78)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:388)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:79)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:43)
at java.lang.reflect.Constructor.newInstance(Constructor.java:313)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.instantiateNC(NameSpaceBuilder.java:1205)
... 15 more
Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:667)
at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:583)
at com.ibm.rmi.iiop.TransportManager.initTransports(TransportManager.java:141)
at com.ibm.rmi.iiop.TransportManager.getServerIIOPProfile(TransportManager.java:148)
at com.ibm.CORBA.iiop.ORB.getTransportProfile(ORB.java:3272)
at com.ibm.ejs.oa.EJSRootOAImpl.registerServant(EJSRootOAImpl.java:380)
at com.ibm.ejs.oa.EJSOAImpl.registerServant(EJSOAImpl.java:254)
at com.ibm.ws.naming.distcos.ServantManagerImpl.registerContext(ServantManagerImpl.java:183)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.<init>(WsnOptimizedNamingImplBase.java:220)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.<init>(WsnOptimizedNamingImpl.java:182)
at com.ibm.ws.naming.distcos.WsnDistributedNC.<init>(WsnDistributedNC.java:116)
at com.ibm.ws.naming.distcos.ReadOnlyNC.<init>(ReadOnlyNC.java:59)
... 20 more
  • Begin backtrace for nested exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:79)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:43)
at java.lang.reflect.Constructor.newInstance(Constructor.java:313)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.instantiateNC(NameSpaceBuilder.java:1205)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.createRootNC(NameSpaceBuilder.java:1108)
at com.ibm.ws.naming.distcos.NameSpaceBuilder.buildNameSpace(NameSpaceBuilder.java:309)
at com.ibm.ws.naming.distcos.NSBSingleAppSvr.buildNameSpace(NSBSingleAppSvr.java:78)
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:388)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTransport.java:667)
at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:583)
at com.ibm.rmi.iiop.TransportManager.initTransports(TransportManager.java:141)
at com.ibm.rmi.iiop.TransportManager.getServerIIOPProfile(TransportManager.java:148)
at com.ibm.CORBA.iiop.ORB.getTransportProfile(ORB.java:3272)
at com.ibm.ejs.oa.EJSRootOAImpl.registerServant(EJSRootOAImpl.java:380)
at com.ibm.ejs.oa.EJSOAImpl.registerServant(EJSOAImpl.java:254)
at com.ibm.ws.naming.distcos.ServantManagerImpl.registerContext(ServantManagerImpl.java:183)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.<init>(WsnOptimizedNamingImplBase.java:220)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.<init>(WsnOptimizedNamingImpl.java:182)
at com.ibm.ws.naming.distcos.WsnDistributedNC.<init>(WsnDistributedNC.java:116)
at com.ibm.ws.naming.distcos.ReadOnlyNC.<init>(ReadOnlyNC.java:59)
... 20 more

1/29/05 8:39:30:984 CST 3eb5ca6b WsServer E WSVR0009E: Error occurred during startup
1) Any idea how to fix this.I went through the documentation to figure out the problem.No Use.
Finally,I need to post to this user group.

2)Any help in this regard is appreciated.

Thanks
DrWSAD
Updated on 2011-11-30T08:11:47Z at 2011-11-30T08:11:47Z by JohnnyKnoxville
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2005-04-19T15:12:26Z  in response to SystemAdmin
    I am facing the exact same problem with an identical error message. I have not yet been able to find a solution.
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2005-06-05T23:31:15Z  in response to SystemAdmin
    I found the same issue on win2K.
    I changed the Server connection type and admin port and it works if you select SOAP (more firewall compatible) SOAP connector port: 8880
    • SystemAdmin
      SystemAdmin
      11979 Posts
      ACCEPTED ANSWER

      Re: Server server1 failed to start

      ‏2005-06-27T10:59:12Z  in response to SystemAdmin
      ED_C please could you elaborate more on exactly what you changed to get this to work. Thanks
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2005-07-07T15:51:34Z  in response to SystemAdmin
    I had the same issue on XP , got it to work by replacing "WINNT" with "Windows" in the server configuration like so
    variable name="SystemRoot" value="C:\Windows"

    thx
    Sam
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2006-03-28T15:50:43Z  in response to SystemAdmin
    I have the same problem. Can you please post the solution.
    Thanks,
    K
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2006-06-12T18:53:04Z  in response to SystemAdmin
    Most of the time it is related to port conflict...

    the below link asks you to check
    SAS_SSL_SERVERAUTH_LISTENER_ADDRESS
    CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS
    CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS

    in my case...there was conflict with ORB_LISTENER_ADDRESS. After changing the port number...it worked perfectly fine!!!

    Check this link...
    http://www-1.ibm.com/support/docview.wss?uid=swg21162691
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    SOLUTION

    ‏2007-09-14T15:10:03Z  in response to SystemAdmin
    Issue the netstat -A COMMAND and find the ports which are conflicting wt the server ports listed in serverIndex.xml document

    C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\AppSrv0000\config\cells\akaketwaNode01Cell\nodes\akaketwaNode01\serverindex.xml

    Reassign unused port numbers which are conflicting ion the serverIndex documemnt and restart the sserver. guuuuuuuuuudluck!!
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2008-03-18T20:55:49Z  in response to SystemAdmin
    I encountered this error message in WAS 5.1.1.3, but could not find a port conflict.

    However, what I did find was much stranger: I found that other JVM applications, installed in the same instance of WebSphere, had somehow become bound to the startup of Server1.

    To resolve this: I had to remove the other applications, but, since I could not get into the WebSphere console, I had to go into <WAS Home>/config/cells/<cellname>/applications, then delete the .ear files of the offending apps.

    I still don't know how this happened, but the issue started happening following the installation of a JVM.

    Once I removed the .ear files (in this case, the Sample applications that can be installed with WAS 5), server 1 again started with no errors.
  • alexbp
    alexbp
    1 Post
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2008-05-27T23:55:09Z  in response to SystemAdmin
    Hello everyone

    I have the same problem.

    In my indexserver.xml I have this

    <endPoint xmi:id="EndPoint_1" host="130.60.70.245" port="2833"/>
    </specialEndpoints>
    <specialEndpoints xmi:id="NamedEndPoint_2" endPointName="SOAP_CONNECTOR_ADDRESS">
    <endPoint xmi:id="EndPoint_2" host="130.60.70.245" port="8880"/>
    </specialEndpoints>
    <specialEndpoints xmi:id="NamedEndPoint_3" endPointName="DRS_CLIENT_ADDRESS">
    <endPoint xmi:id="EndPoint_3" host="130.60.70.245" port="7873"/>
    </specialEndpoints>
    <specialEndpoints xmi:id="NamedEndPoint_4" endPointName="JMSSERVER_QUEUED_ADDRESS">
    <endPoint xmi:id="EndPoint_4" host="130.60.70.245" port="5558"/>
    </specialEndpoints>
    <specialEndpoints xmi:id="NamedEndPoint_5" endPointName="JMSSERVER_DIRECT_ADDRESS">
    <endPoint xmi:id="EndPoint_5" host="130.60.70.245" port="5559"/>
    </specialEndpoints>

    <specialEndpoints xmi:id="NamedEndPoint_6" endPointName="SAS_SSL_SERVERAUTH_LISTENER_ADDRESS">
    <endPoint xmi:id="EndPoint_6" host="130.60.70.245" port="0"/>
    </specialEndpoints>
    <specialEndpoints xmi:id="NamedEndPoint_7" endPointName="CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS">
    <endPoint xmi:id="EndPoint_7" host="130.60.70.245" port="0"/>
    </specialEndpoints>
    <specialEndpoints xmi:id="NamedEndPoint_8" endPointName="CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS">
    <endPoint xmi:id="EndPoint_8" host="130.60.70.245" port="0"/>

    I need to change the port 0 value?

    Because when I type netstat -a I got this

    root@PGA-LNX02 PGA-LNX02# netstat -na | grep 2833
    tcp 0 0 0.0.0.0:2833 0.0.0.0:* LISTEN
    root@PGA-LNX02 PGA-LNX02# netstat -na | grep 8880
    root@PGA-LNX02 PGA-LNX02# netstat -na | grep 7873
    root@PGA-LNX02 PGA-LNX02# netstat -na | grep 5558
    root@PGA-LNX02 PGA-LNX02# netstat -na | grep 5559
    root@PGA-LNX02 PGA-LNX02# netstat -na | grep 0
    tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN
    and a list of 0 port used.

    Here I have another 2 questions

    The first one the port 8880 is not listen thats ok or have to be listen ?
    I have to change th port 0 because many things have this one ?
    Thanks for your tips.

    I need to resolve this thanks again
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2009-03-13T14:04:22Z  in response to SystemAdmin
    com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
    solution:
    turn ports below into 0. Restart the server - it works.
    CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS :0
    CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS :0
    ORB_LISTENER_ADDRESS :0
    SAS_SSL_SERVERAUTH_LISTENER_ADDRESS :0
    • iNimish
      iNimish
      1 Post
      ACCEPTED ANSWER

      Re: Server server1 failed to start

      ‏2010-09-08T07:19:45Z  in response to SystemAdmin
      Hi I tried your solution, it yet gives me the same error.
      Do you know anything more about this error?

      Thanks.
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Server server1 failed to start

    ‏2010-07-13T22:20:09Z  in response to SystemAdmin
    1. generate/propergate webservers
    2. stop and restart webservers
    3. stop all application servers
    4. stop all IBM services from Windows Services
    5. kill all java.exe from Windows Task Manager>Processes
    6. Start all IBM services from Windows Services
    7. start all application servers(if they haven't started up already)
    This should solve issue.