Topic
  • 25 replies
  • Latest Post - ‏2013-11-11T13:20:54Z by JS22
SystemAdmin
SystemAdmin
37421 Posts

Pinned topic WAS is not starting properly.

‏2010-11-29T07:31:57Z |
Hi all,

I installed Websphere application server v7 on windows 2003 server. It was installed successfully. Its worked fine for 2 days. After that server was not starting and got this error:

WASX7023E: Error creating "SOAP" connection to host "localhost"; exception information: com.ibm.websphere.management.exception.ConnectorNotAvailableException: com.ibm.websphere.management.exception.ConnectorNotAvailableException: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8880.

The admin console was never started earlier it was. After that I created a management profile and tried to register the server. But when I am registering that Websphere application service, I am getting the error like
The system cannot create a SOAP connector to connect to host localhost at port 8877.
I am also attaching a file showing the error.

Was my WAS not installed properly.

While installed AdminAgent i did not get Server adminagent open for e-business; process id is 1932.

Your help is very much required one.
Updated on 2010-12-02T12:21:25Z at 2010-12-02T12:21:25Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T09:14:51Z  
    Hi,

    Did you change your SOAP port as it is shown as 8880 once and 8877 second time?

    Kindly make sure that port is correct in serverindex.xml file and is listening.

    //Ahmed
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T10:36:56Z  
    Hi,

    Did you change your SOAP port as it is shown as 8880 once and 8877 second time?

    Kindly make sure that port is correct in serverindex.xml file and is listening.

    //Ahmed
    Ahmed,

    That two ports are actually first (8880) was for Application server profile and second(8877) was for Administrative agent that is management profile. Both run as service. I am getting same error in both profiles i.e. soap error.

    My both services are not starting.

    Look if you get some more idea.

    Thanks for reply.

    regards.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T10:45:39Z  
    Ahmed,

    That two ports are actually first (8880) was for Application server profile and second(8877) was for Administrative agent that is management profile. Both run as service. I am getting same error in both profiles i.e. soap error.

    My both services are not starting.

    Look if you get some more idea.

    Thanks for reply.

    regards.
    OK, Kindly make sure that this port is not used in other services on your computer plus checking startServer.log file while starting this app server.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T11:06:17Z  
    OK, Kindly make sure that this port is not used in other services on your computer plus checking startServer.log file while starting this app server.
    Ahmed,

    These are the output of startServer.log :

    11/29/10 12:20:58:107 GMT+05:30 00000000 WindowsServic > getWindowsServiceNameForServer adminagent Entry
    <null>
    11/29/10 12:20:58:107 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:20:58:107 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -getServiceName adminagent -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01
    11/29/10 12:20:58:139 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@a160a16
    11/29/10 12:20:58:154 GMT+05:30 00000002 WindowsServic 3 inputRec == IBMWAS70Service - i3mc083AANode01
    11/29/10 12:20:58:154 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 0
    11/29/10 12:20:58:170 GMT+05:30 00000000 WindowsServic 3 exitCode = 0
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic < getWindowsServiceNameForServer Exit
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic 1 Trying to new up WindowsService using serverName=adminagent, winServiceName=i3mc083AANode01
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic > getServiceLogName for adminagent Entry
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -getServiceLogName adminagent -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@28892889
    11/29/10 12:20:59:185 GMT+05:30 00000004 WindowsServic 3 inputRec == C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01\logs\i3mc083AANode01 Service.log
    11/29/10 12:20:59:185 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 0
    11/29/10 12:20:59:185 GMT+05:30 00000000 WindowsServic 3 exitCode = 0
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic < getServiceLogName Exit
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic < WindowsService Exit
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic > getServiceStatus Entry
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -status i3mc083AANode01
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@7b1d7b1d
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 1
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 3 exitCode = 1
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic < getServiceStatus Exit
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic > getServiceStatus Entry
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -status i3mc083AANode01
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@2070207
    11/29/10 12:21:00:217 GMT+05:30 00000006 WindowsServic 3 inputRec == The service is stopped.
    11/29/10 12:21:00:248 GMT+05:30 00000008 WindowsServic 3 inputRec == The service is stopped.
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 1
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic 3 exitCode = 1
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic < getServiceStatus Exit
    11/29/10 12:21:00:248 GMT+05:30 00000000 WsServerContr 1 Window service status (1=stopped, 2=started, 3=not-registred) is 1
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic > doWASServiceAction action start Entry
    <null>
    11/29/10 12:21:00:248 GMT+05:30 00000000 AdminTool A ADMU7701I: Because adminagent is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -start i3mc083AANode01
    11/29/10 12:21:00:264 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@58a458a4
    11/29/10 12:21:00:279 GMT+05:30 0000000a WindowsServic 3 waitForFileExist(C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01\logs\i3mc083AANode01 Service.log)
    11/29/10 12:21:00:779 GMT+05:30 0000000a EncodingUtils > getProperEncoding Entry
    11/29/10 12:21:00:779 GMT+05:30 0000000a EncodingUtils 3 System.getProperty("file.encoding") is: Cp1252
    11/29/10 12:21:00:779 GMT+05:30 0000000a EncodingUtils > isPlatformWindows() Entry
    11/29/10 12:21:00:779 GMT+05:30 0000000a WindowsServic 3 *** returned readerencoding = Cp850
    11/29/10 12:21:26:294 GMT+05:30 0000000d WindowsServic 3 inputRec == Starting Service: i3mc083AANode01
    11/29/10 12:21:26:294 GMT+05:30 0000000d WindowsServic 3 inputRec ==
    11/29/10 12:21:26:294 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is -1
    11/29/10 12:21:26:294 GMT+05:30 00000000 WindowsServic 3 -- interrupt the thread that is collecting stdout
    11/29/10 12:21:26:294 GMT+05:30 0000000e WindowsServic 3 inputRec == Service failed to start. startServer return code = -1
    11/29/10 12:21:27:294 GMT+05:30 00000000 WindowsServic 3 exitCode = -1
    11/29/10 12:21:27:294 GMT+05:30 00000000 WindowsServic 3 Service failed to start. startServer return code = -1
    11/29/10 12:21:27:294 GMT+05:30 0000000a WindowsServic 3 readAndDisplayServiceLogFile(), caught InterruptedException
    11/29/10 12:21:27:294 GMT+05:30 00000000 AdminTool A ADMU7704E: Failed while trying to start the Windows Service associated with server: adminagent;
    probable error executing WASService.exe: Starting Service: i3mc083AANode01
    Service failed to start. startServer return code = -1

    And both the ports 8880 and 8877 are not listening.

    The services are not being started up.

    So where may the wrong and how to start the servers.

    regards,
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T12:12:59Z  
    Ahmed,

    These are the output of startServer.log :

    11/29/10 12:20:58:107 GMT+05:30 00000000 WindowsServic > getWindowsServiceNameForServer adminagent Entry
    <null>
    11/29/10 12:20:58:107 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:20:58:107 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -getServiceName adminagent -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01
    11/29/10 12:20:58:139 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@a160a16
    11/29/10 12:20:58:154 GMT+05:30 00000002 WindowsServic 3 inputRec == IBMWAS70Service - i3mc083AANode01
    11/29/10 12:20:58:154 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 0
    11/29/10 12:20:58:170 GMT+05:30 00000000 WindowsServic 3 exitCode = 0
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic < getWindowsServiceNameForServer Exit
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic 1 Trying to new up WindowsService using serverName=adminagent, winServiceName=i3mc083AANode01
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic > getServiceLogName for adminagent Entry
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -getServiceLogName adminagent -profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01
    11/29/10 12:20:59:170 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@28892889
    11/29/10 12:20:59:185 GMT+05:30 00000004 WindowsServic 3 inputRec == C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01\logs\i3mc083AANode01 Service.log
    11/29/10 12:20:59:185 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 0
    11/29/10 12:20:59:185 GMT+05:30 00000000 WindowsServic 3 exitCode = 0
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic < getServiceLogName Exit
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic < WindowsService Exit
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic > getServiceStatus Entry
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -status i3mc083AANode01
    11/29/10 12:21:00:185 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@7b1d7b1d
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 1
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 3 exitCode = 1
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic < getServiceStatus Exit
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic > getServiceStatus Entry
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -status i3mc083AANode01
    11/29/10 12:21:00:217 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@2070207
    11/29/10 12:21:00:217 GMT+05:30 00000006 WindowsServic 3 inputRec == The service is stopped.
    11/29/10 12:21:00:248 GMT+05:30 00000008 WindowsServic 3 inputRec == The service is stopped.
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is 1
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic 3 exitCode = 1
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic < getServiceStatus Exit
    11/29/10 12:21:00:248 GMT+05:30 00000000 WsServerContr 1 Window service status (1=stopped, 2=started, 3=not-registred) is 1
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic > doWASServiceAction action start Entry
    <null>
    11/29/10 12:21:00:248 GMT+05:30 00000000 AdminTool A ADMU7701I: Because adminagent is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic > getWASServiceCmdPath Entry
    <null>
    11/29/10 12:21:00:248 GMT+05:30 00000000 WindowsServic 1 In executeCommand, args are: C:\Program Files\IBM\WebSphere\AppServer\bin\WASService.exe -start i3mc083AANode01
    11/29/10 12:21:00:264 GMT+05:30 00000000 WindowsServic 1 Runtime.exec() returned process java.lang.ProcessImpl@58a458a4
    11/29/10 12:21:00:279 GMT+05:30 0000000a WindowsServic 3 waitForFileExist(C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01\logs\i3mc083AANode01 Service.log)
    11/29/10 12:21:00:779 GMT+05:30 0000000a EncodingUtils > getProperEncoding Entry
    11/29/10 12:21:00:779 GMT+05:30 0000000a EncodingUtils 3 System.getProperty("file.encoding") is: Cp1252
    11/29/10 12:21:00:779 GMT+05:30 0000000a EncodingUtils > isPlatformWindows() Entry
    11/29/10 12:21:00:779 GMT+05:30 0000000a WindowsServic 3 *** returned readerencoding = Cp850
    11/29/10 12:21:26:294 GMT+05:30 0000000d WindowsServic 3 inputRec == Starting Service: i3mc083AANode01
    11/29/10 12:21:26:294 GMT+05:30 0000000d WindowsServic 3 inputRec ==
    11/29/10 12:21:26:294 GMT+05:30 00000000 WindowsServic 1 retCode from childProcess.waitFor() is -1
    11/29/10 12:21:26:294 GMT+05:30 00000000 WindowsServic 3 -- interrupt the thread that is collecting stdout
    11/29/10 12:21:26:294 GMT+05:30 0000000e WindowsServic 3 inputRec == Service failed to start. startServer return code = -1
    11/29/10 12:21:27:294 GMT+05:30 00000000 WindowsServic 3 exitCode = -1
    11/29/10 12:21:27:294 GMT+05:30 00000000 WindowsServic 3 Service failed to start. startServer return code = -1
    11/29/10 12:21:27:294 GMT+05:30 0000000a WindowsServic 3 readAndDisplayServiceLogFile(), caught InterruptedException
    11/29/10 12:21:27:294 GMT+05:30 00000000 AdminTool A ADMU7704E: Failed while trying to start the Windows Service associated with server: adminagent;
    probable error executing WASService.exe: Starting Service: i3mc083AANode01
    Service failed to start. startServer return code = -1

    And both the ports 8880 and 8877 are not listening.

    The services are not being started up.

    So where may the wrong and how to start the servers.

    regards,
    Check in the logs folder for the server, (e.g. ...\profiles\app\log\server1)
    there is a file called server1.pid, in this case, this file, contains the process id for the server process, it will not be deleted in case of abnormal shutdown for the server so if it does exist delete it and try to start adminagent again.

    //Ahmed
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T13:55:43Z  
    Check in the logs folder for the server, (e.g. ...\profiles\app\log\server1)
    there is a file called server1.pid, in this case, this file, contains the process id for the server process, it will not be deleted in case of abnormal shutdown for the server so if it does exist delete it and try to start adminagent again.

    //Ahmed
    Hi,

    As you mentioned server1.pid in not there in

    C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1

    C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01\logs\adminagent.

    When I am starting ServiceAANode01 from the service it is being started after that I execute the registernode command to register application server in it to manage.

    I have attached a word file for reference.

    (I did it as i was getting soap error when i was starting Application server as suggested in doc.) But Admin console was not starting say that server is not able to start. And it was stopped in service)

    Now both admin console is not running. My requirement is anyhow to run application server.

    regards,
    Afroz
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T14:02:29Z  
    Hi,

    As you mentioned server1.pid in not there in

    C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1

    C:\Program Files\IBM\WebSphere\AppServer\profiles\AdminAgent01\logs\adminagent.

    When I am starting ServiceAANode01 from the service it is being started after that I execute the registernode command to register application server in it to manage.

    I have attached a word file for reference.

    (I did it as i was getting soap error when i was starting Application server as suggested in doc.) But Admin console was not starting say that server is not able to start. And it was stopped in service)

    Now both admin console is not running. My requirement is anyhow to run application server.

    regards,
    Afroz
    In order to register this node to admin agent, admin agent and node themselves should be started and you already unable to start them, so I suggest to start app server itself using startserver command from its bin folder after making sure that its ports not in use by this computer using netstat -a, if it started successfully i believe that you do not need to add this node to admin agent as you was doing this in order to start that app server.

    If app server didn't start using startserver from its bin folder just attach startserver.log and systemout.log as well.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T14:40:49Z  
    In order to register this node to admin agent, admin agent and node themselves should be started and you already unable to start them, so I suggest to start app server itself using startserver command from its bin folder after making sure that its ports not in use by this computer using netstat -a, if it started successfully i believe that you do not need to add this node to admin agent as you was doing this in order to start that app server.

    If app server didn't start using startserver from its bin folder just attach startserver.log and systemout.log as well.
    Ahmed,

    I tried to start the appserver everyway and with command startServer server1 from bin folder also.

    Also port 9060 and 8880 is not listening and not being used any programme. For your reference I have attached the startServer.log and systemOut.log files in this reply.

    Please find it.
    second file in subsequent reply.

    Regards,
    afroz
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T14:41:28Z  
    Hi,

    Did you change your SOAP port as it is shown as 8880 once and 8877 second time?

    Kindly make sure that port is correct in serverindex.xml file and is listening.

    //Ahmed
    2nd file systemOut.log
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-29T17:08:30Z  
    2nd file systemOut.log
    I didn't find any errors except the one in systemout.log of SSL expired certificate but server started normally after that, did you change windows account used to run this app server windows service?
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T07:48:37Z  
    I didn't find any errors except the one in systemout.log of SSL expired certificate but server started normally after that, did you change windows account used to run this app server windows service?
    Ahmed,

    I am sending the startServer.log file padding.
    • Start Display Current Environment ************
    Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 2
    Java version = J2RE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260-20080816_22093 (JIT enabled, AOT enabled)
    J9VM - 20080816_022093_lHdSMr
    JIT - r9_20080721_1330ifx2
    GC - 20080724_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = C:\Program Files\IBM\WebSphere\AppServer
    user.install.root = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
    Java Home = C:\Program Files\IBM\WebSphere\AppServer\java\jre
    ws.ext.dirs = C:\\Program Files\\IBM\\WebSphere\\AppServer\\java\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\classes;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\installedChannels;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib\\ext;C:\\Program Files\\IBM\\WebSphere\\AppServer\\web\\help;C:\\Program Files\\IBM\\WebSphere\\AppServer\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime
    Classpath = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties;C:\Program Files\IBM\WebSphere\AppServer\properties;C:\Program Files\IBM\WebSphere\AppServer\lib\startup.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/lmproxy.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/urlprotocols.jar;C:\Program Files\IBM\WebSphere\AppServer\java\lib\tools.jar
    Java Library path = C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;.;C:\Program Files\IBM\WebSphere\AppServer\bin;C:\Program Files\IBM\WebSphere\AppServer\java\bin;C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\IBM\SQLLIB\BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL
    Current trace specification = *=info:com.ibm.*=all
    • End Display Current Environment *************
    11/30/10 12:30:52:437 GMT+05:30 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
    11/30/10 12:30:52:718 GMT+05:30 00000000 WsServerContr 1 Executing executeUtilityOnWindows with args: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config i3mc083Node01Cell i3mc083Node01 server1 -fromWinService \\.\pipe\w6SvcPipe_29F1A_1216A
    11/30/10 12:30:52:718 GMT+05:30 00000000 WsServerContr 1 invokedByWindowsService has been set to true earlier
    11/30/10 12:30:52:718 GMT+05:30 00000000 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
    11/30/10 12:30:53:437 GMT+05:30 00000000 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile
    11/30/10 12:30:53:437 GMT+05:30 00000000 AdminTool A ADMU3100I: Reading configuration for server: server1
    11/30/10 12:30:57:730 GMT+05:30 00000000 AdminTool A ADMU3200I: Server launched. Waiting for initialization status.

    I think the log file shud end with some process id which is normally used to be there. But not now onwards.

    When I restarted the system, WASNode service is showing started. But When i am trying to get admin console started it is not saying port 9060 is not listening.

    one another question you asked regarding changing windows account is like that: I installed the websphere with Windows Local admin but I am running them with my domain id.

    I am also getting same problem when I an login thru Windows Local Admin.

    regards,
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T08:26:38Z  
    Ahmed,

    I am sending the startServer.log file padding.
    • Start Display Current Environment ************
    Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 2
    Java version = J2RE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260-20080816_22093 (JIT enabled, AOT enabled)
    J9VM - 20080816_022093_lHdSMr
    JIT - r9_20080721_1330ifx2
    GC - 20080724_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = C:\Program Files\IBM\WebSphere\AppServer
    user.install.root = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
    Java Home = C:\Program Files\IBM\WebSphere\AppServer\java\jre
    ws.ext.dirs = C:\\Program Files\\IBM\\WebSphere\\AppServer\\java\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\classes;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\installedChannels;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib\\ext;C:\\Program Files\\IBM\\WebSphere\\AppServer\\web\\help;C:\\Program Files\\IBM\\WebSphere\\AppServer\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime
    Classpath = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties;C:\Program Files\IBM\WebSphere\AppServer\properties;C:\Program Files\IBM\WebSphere\AppServer\lib\startup.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/lmproxy.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/urlprotocols.jar;C:\Program Files\IBM\WebSphere\AppServer\java\lib\tools.jar
    Java Library path = C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;.;C:\Program Files\IBM\WebSphere\AppServer\bin;C:\Program Files\IBM\WebSphere\AppServer\java\bin;C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\IBM\SQLLIB\BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL
    Current trace specification = *=info:com.ibm.*=all
    • End Display Current Environment *************
    11/30/10 12:30:52:437 GMT+05:30 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
    11/30/10 12:30:52:718 GMT+05:30 00000000 WsServerContr 1 Executing executeUtilityOnWindows with args: C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config i3mc083Node01Cell i3mc083Node01 server1 -fromWinService \\.\pipe\w6SvcPipe_29F1A_1216A
    11/30/10 12:30:52:718 GMT+05:30 00000000 WsServerContr 1 invokedByWindowsService has been set to true earlier
    11/30/10 12:30:52:718 GMT+05:30 00000000 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=info.
    11/30/10 12:30:53:437 GMT+05:30 00000000 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile
    11/30/10 12:30:53:437 GMT+05:30 00000000 AdminTool A ADMU3100I: Reading configuration for server: server1
    11/30/10 12:30:57:730 GMT+05:30 00000000 AdminTool A ADMU3200I: Server launched. Waiting for initialization status.

    I think the log file shud end with some process id which is normally used to be there. But not now onwards.

    When I restarted the system, WASNode service is showing started. But When i am trying to get admin console started it is not saying port 9060 is not listening.

    one another question you asked regarding changing windows account is like that: I installed the websphere with Windows Local admin but I am running them with my domain id.

    I am also getting same problem when I an login thru Windows Local Admin.

    regards,
    Hi,

    Thank you, yes you are correct it hangs on AdminTool A ADMU3200I: Server launched. Waiting for initialization status. so can you try starting it using trace command:

    startServer server1 -trace
    
    from this app server bin directory and send me startServer.txt log after that, it will contain more detailed info while starting.

    another issue, are you sure that there are no firewalls locking these ports?

    //Ahmed
    Updated on 2014-03-25T23:59:12Z at 2014-03-25T23:59:12Z by iron-man
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T09:05:51Z  
    Hi,

    Thank you, yes you are correct it hangs on AdminTool A ADMU3200I: Server launched. Waiting for initialization status. so can you try starting it using trace command:

    <pre class="java dw" data-editor-lang="java" data-pbcklang="java" dir="ltr">startServer server1 -trace </pre> from this app server bin directory and send me startServer.txt log after that, it will contain more detailed info while starting.

    another issue, are you sure that there are no firewalls locking these ports?

    //Ahmed
    Hi,

    I ran startServer server1 -trace commnad. Server is not starting. have attached the file. Please get it.

    For ports I am not sure. As I am doing in local system, so the ports are generally open I think. If you can suggest me some process as how to check it. I am sure that the port 9060 or 8880 is not listening so not being used by another program.

    regards,
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T09:43:03Z  
    Hi,

    I ran startServer server1 -trace commnad. Server is not starting. have attached the file. Please get it.

    For ports I am not sure. As I am doing in local system, so the ports are generally open I think. If you can suggest me some process as how to check it. I am sure that the port 9060 or 8880 is not listening so not being used by another program.

    regards,
    Hi,

    Checking your job log in details found that environemnt variables changed on Nov 25 as there are a path to your app server bin directory is missing, check differences in attached text files named worked and failed, adjust this and try again.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T12:21:07Z  
    Hi,

    Checking your job log in details found that environemnt variables changed on Nov 25 as there are a path to your app server bin directory is missing, check differences in attached text files named worked and failed, adjust this and try again.
    Hi,

    I find that these paths are extra

    C:\Program Files\IBM\WebSphere\AppServer\bin;C:\Program Files\IBM\WebSphere\AppServer\java\bin;C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin

    i mean once more it is there. I checked my path env variable which is correctly set. And also java is also set.

    Otherwise I don't know how to adjust. Please put more light.

    regards,
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T14:02:55Z  
    Hi,

    I find that these paths are extra

    C:\Program Files\IBM\WebSphere\AppServer\bin;C:\Program Files\IBM\WebSphere\AppServer\java\bin;C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin

    i mean once more it is there. I checked my path env variable which is correctly set. And also java is also set.

    Otherwise I don't know how to adjust. Please put more light.

    regards,
    yes you are correct, it is a redundant!, do you have other app servers installed on this server trying to start them?

    regarding firewall, just switch it off from windows settings and keep me updated.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T14:29:53Z  
    yes you are correct, it is a redundant!, do you have other app servers installed on this server trying to start them?

    regarding firewall, just switch it off from windows settings and keep me updated.
    No, I have only one application server. There are not any other application servers on my system.

    Also the Windows Firewall is already switched off!!!

    regards,
    ak
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-11-30T17:44:33Z  
    No, I have only one application server. There are not any other application servers on my system.

    Also the Windows Firewall is already switched off!!!

    regards,
    ak
    Hi, run serverStatus and let me know its reply as last log before this misbehavior was server already started!
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-12-01T08:33:11Z  
    Hi, run serverStatus and let me know its reply as last log before this misbehavior was server already started!
    Hi,

    When I restarted the system, I find the Websphere application service running. After that I run the serverStatus command for which result comes as the server seems to be stopped.

    I am sending you previous serverStatus file as attached word file.

    And status of new is pasted here.
    Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 2
    Java version = J2RE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260-20080816_22093 (JIT enabled, AOT enabled)
    J9VM - 20080816_022093_lHdSMr
    JIT - r9_20080721_1330ifx2
    GC - 20080724_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = C:\Program Files\IBM\WebSphere\AppServer
    user.install.root = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
    Java Home = C:\Program Files\IBM\WebSphere\AppServer\java\jre
    ws.ext.dirs = C:\\Program Files\\IBM\\WebSphere\\AppServer\\java\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\classes;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\installedChannels;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib\\ext;C:\\Program Files\\IBM\\WebSphere\\AppServer\\web\\help;C:\\Program Files\\IBM\\WebSphere\\AppServer\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime
    Classpath = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties;C:\Program Files\IBM\WebSphere\AppServer\properties;C:\Program Files\IBM\WebSphere\AppServer\lib\startup.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/lmproxy.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/urlprotocols.jar;C:\Program Files\IBM\WebSphere\AppServer\java\lib\tools.jar
    Java Library path = C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;.;C:\Program Files\IBM\WebSphere\AppServer\bin;C:\Program Files\IBM\WebSphere\AppServer\java\bin;C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\IBM\SQLLIB\BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL
    Current trace specification = *=info

    12/1/10 13:49:31:794 GMT+05:30 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info.
    12/1/10 13:49:32:177 GMT+05:30 00000000 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile
    12/1/10 13:49:32:177 GMT+05:30 00000000 AdminTool A ADMU0500I: Retrieving server status for server1
    12/1/10 13:49:32:305 GMT+05:30 00000000 ModelMgr I WSVR0801I: Initializing all server configuration models
    12/1/10 13:49:38:258 GMT+05:30 00000000 SSLConfig W CWPKI0041W: One or more key stores are using the default password.
    12/1/10 13:49:38:290 GMT+05:30 00000000 SSLConfigMana I CWPKI0027I: Disabling default hostname verification for HTTPS URL connections.
    12/1/10 13:49:38:418 GMT+05:30 00000000 SecurityObjec I Client code attempting to load security configuration
    12/1/10 13:49:45:153 GMT+05:30 00000000 SecurityConne A JSAS0006I: Security connection interceptor initialized.
    12/1/10 13:49:45:185 GMT+05:30 00000000 ServiceInit A JSAS0001I: Security configuration initialized.
    12/1/10 13:49:45:185 GMT+05:30 00000000 ServiceInit A JSAS0003I: Authentication mechanism: BASICAUTH
    12/1/10 13:49:45:313 GMT+05:30 00000000 CSIClientRI A JSAS0007I: Client request interceptor registered.
    12/1/10 13:49:47:228 GMT+05:30 00000000 ProviderTrack I com.ibm.ffdc.osgi.ProviderTracker AddingService FFDC1007I: FFDC Provider Installed: com.ibm.ffdc.EmptyProvider(silent)
    12/1/10 13:49:52:927 GMT+05:30 00000000 AdminTool A ADMU0509I: The Application Server "server1" cannot be reached. It appears to be stopped.
    regards,
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-12-01T11:16:41Z  
    Hi,

    When I restarted the system, I find the Websphere application service running. After that I run the serverStatus command for which result comes as the server seems to be stopped.

    I am sending you previous serverStatus file as attached word file.

    And status of new is pasted here.
    Host Operating System is Windows Server 2003, version 5.2 build 3790 Service Pack 2
    Java version = J2RE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260-20080816_22093 (JIT enabled, AOT enabled)
    J9VM - 20080816_022093_lHdSMr
    JIT - r9_20080721_1330ifx2
    GC - 20080724_AA, Java Compiler = j9jit24, Java VM name = IBM J9 VM
    was.install.root = C:\Program Files\IBM\WebSphere\AppServer
    user.install.root = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01
    Java Home = C:\Program Files\IBM\WebSphere\AppServer\java\jre
    ws.ext.dirs = C:\\Program Files\\IBM\\WebSphere\\AppServer\\java\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\classes;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib;C:\\Program Files\\IBM\\WebSphere\\AppServer\\installedChannels;C:\\Program Files\\IBM\\WebSphere\\AppServer\\lib\\ext;C:\\Program Files\\IBM\\WebSphere\\AppServer\\web\\help;C:\\Program Files\\IBM\\WebSphere\\AppServer\\deploytool\\itp\\plugins\\com.ibm.etools.ejbdeploy\\runtime
    Classpath = C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\properties;C:\Program Files\IBM\WebSphere\AppServer\properties;C:\Program Files\IBM\WebSphere\AppServer\lib\startup.jar;C:\Program Files\IBM\WebSphere\AppServer\lib\bootstrap.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/lmproxy.jar;C:\Program Files\IBM\WebSphere\AppServer/lib/urlprotocols.jar;C:\Program Files\IBM\WebSphere\AppServer\java\lib\tools.jar
    Java Library path = C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;.;C:\Program Files\IBM\WebSphere\AppServer\bin;C:\Program Files\IBM\WebSphere\AppServer\java\bin;C:\Program Files\IBM\WebSphere\AppServer\java\jre\bin;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\IBM\SQLLIB\BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL
    Current trace specification = *=info

    12/1/10 13:49:31:794 GMT+05:30 00000000 ManagerAdmin I TRAS0017I: The startup trace state is *=info.
    12/1/10 13:49:32:177 GMT+05:30 00000000 AdminTool A ADMU0128I: Starting tool with the AppSrv01 profile
    12/1/10 13:49:32:177 GMT+05:30 00000000 AdminTool A ADMU0500I: Retrieving server status for server1
    12/1/10 13:49:32:305 GMT+05:30 00000000 ModelMgr I WSVR0801I: Initializing all server configuration models
    12/1/10 13:49:38:258 GMT+05:30 00000000 SSLConfig W CWPKI0041W: One or more key stores are using the default password.
    12/1/10 13:49:38:290 GMT+05:30 00000000 SSLConfigMana I CWPKI0027I: Disabling default hostname verification for HTTPS URL connections.
    12/1/10 13:49:38:418 GMT+05:30 00000000 SecurityObjec I Client code attempting to load security configuration
    12/1/10 13:49:45:153 GMT+05:30 00000000 SecurityConne A JSAS0006I: Security connection interceptor initialized.
    12/1/10 13:49:45:185 GMT+05:30 00000000 ServiceInit A JSAS0001I: Security configuration initialized.
    12/1/10 13:49:45:185 GMT+05:30 00000000 ServiceInit A JSAS0003I: Authentication mechanism: BASICAUTH
    12/1/10 13:49:45:313 GMT+05:30 00000000 CSIClientRI A JSAS0007I: Client request interceptor registered.
    12/1/10 13:49:47:228 GMT+05:30 00000000 ProviderTrack I com.ibm.ffdc.osgi.ProviderTracker AddingService FFDC1007I: FFDC Provider Installed: com.ibm.ffdc.EmptyProvider(silent)
    12/1/10 13:49:52:927 GMT+05:30 00000000 AdminTool A ADMU0509I: The Application Server "server1" cannot be reached. It appears to be stopped.
    regards,
    Hi,

    It is a strange issue, i found some solution on forums try it:

    http://www.ibm.com/developerworks/forums/thread.jspa?threadID=93178

    Step to resolve the "ADMU3011E" error.

    Solution for windows-XP
    Let WPS_HOME = C:\IBM\WebSphere

    Step (1): Go to command prompt
    Step (2): cd <WPS_HOME>\wp_profile\bin
    Step (3): execute file "osgiCfgInit.bat" at command prompt

    Now, start server using startServer.bat

    Step (4): startServer.bat WebSphere_Portal -user wpsadmin -password wpsadmin

    serverName : WebSphere_Portal
    userName : wpsadmin
    password : wpsadmin
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-12-02T12:16:35Z  
    Hi,

    It is a strange issue, i found some solution on forums try it:

    http://www.ibm.com/developerworks/forums/thread.jspa?threadID=93178

    Step to resolve the "ADMU3011E" error.

    Solution for windows-XP
    Let WPS_HOME = C:\IBM\WebSphere

    Step (1): Go to command prompt
    Step (2): cd <WPS_HOME>\wp_profile\bin
    Step (3): execute file "osgiCfgInit.bat" at command prompt

    Now, start server using startServer.bat

    Step (4): startServer.bat WebSphere_Portal -user wpsadmin -password wpsadmin

    serverName : WebSphere_Portal
    userName : wpsadmin
    password : wpsadmin
    Hi,

    ADMU7704E: Failed while trying to start the Windows Service associated with server

    I am able to solve the problem. The problem was actually of Windows service. The websphere application service was registered as Windows service. So when I was starting the server it was first starting the wasservice registered as windows. And that was not letting to start the server.

    So I removed the service from Windows service by running following
    command
    +WASINSTALLROOT+/WASService.exe -remove service_name

    after that it went all well.

    Regards,
    Afroz
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-12-02T12:18:11Z  
    Hi,

    ADMU7704E: Failed while trying to start the Windows Service associated with server

    I am able to solve the problem. The problem was actually of Windows service. The websphere application service was registered as Windows service. So when I was starting the server it was first starting the wasservice registered as windows. And that was not letting to start the server.

    So I removed the service from Windows service by running following
    command
    +WASINSTALLROOT+/WASService.exe -remove service_name

    after that it went all well.

    Regards,
    Afroz
    Thanks for all your efforts and help.
  • SystemAdmin
    SystemAdmin
    37421 Posts

    Re: WAS is not starting properly.

    ‏2010-12-02T12:21:25Z  
    Thanks for all your efforts and help.
    Hi,

    Good news but while windows service is stopped you can startserver using command line normally!

    may be you had a conflict somewhere in this service!

    //Ahmed
  • JS22
    JS22
    2 Posts

    Re: WAS is not starting properly.

    ‏2013-11-11T13:03:29Z  
    Hi,

    Good news but while windows service is stopped you can startserver using command line normally!

    may be you had a conflict somewhere in this service!

    //Ahmed

    I have the same problem. I discovered that the problem was with the Windows service, so I disabled it. After that I was able to start WAS via startserver command. The problem now is that after starting it this way, it seems the server does not remain started. I am having to manually restart it after a couple of minutes to enable business processing. I deleted the existing windows service and recreated it. As long as the windows service is enabled, WAS will not start.

     

    This is not a new installation. Everything worked fine from day of installation in 2011 until this Friday when WAS service failed to start.

    Please assist.

    Updated on 2013-11-11T13:10:49Z at 2013-11-11T13:10:49Z by JS22