Prev
Next
Forums S3 Systems Administration

WebSphere web server start

Sort:
You are not authorized to post a reply.
Author
Messages
Roger French
Veteran Member
Posts: 545
Veteran Member
6/18/2008 5:48 PM

    Have an issue on WebSphere 6.1.017 (patches applied), where the web server (called webserver1) is not running (yes I've refreshed the status0> Also the Start button is greyed out. So, how do I start webserver1? Tried using startserver on command line. Stopped and restarted app server, node agents, etc. Even rebooted the box a few times, still no go.

    Windows 2003, LSF9.0.0.4, Websphere 6.1.017. Environment and webserver are local on same box.

     

    thanks in advance,

    Roger

    John Henley
    Posts: 3352
    6/18/2008 5:58 PM
      I have found that sometimes you need to delete the *temp* directories under the WAS profile, e.g. %WAS_HOME%\AppServer\Profiles\AppSrv01\*temp*
      Thanks for using the LawsonGuru.com forums!
      John
      Roger French
      Veteran Member
      Posts: 545
      Veteran Member
      6/18/2008 6:24 PM

        Tried that... deleted the temp folder... stopped and restarted node agents, app server and dmgr. THen restarted everything, deleted temp folder. Still the Start button on webserver1 is greyed out.

         

         

         

        Posted By John Henley on 6/18/2008 1:58 PM
        I have found that sometimes you need to delete the *temp* directories under the WAS profile, e.g. %WAS_HOME%\AppServer\Profiles\AppSrv01\*temp*

         

        Ben Coonfield
        Veteran Member
        Posts: 146
        Veteran Member
        6/19/2008 6:14 PM
          Do you mean that you go to the Websphere console Servers->Webserver, and you see a web server defined but the start button doesn't work? Not sure exactly how this works on Windows but on Unix there is a adminctl process that needs to be started. In windows I suspect that this would be a similar Windows service. Try going to control panel->Admin Tools->Services and look for a service that should be started and was not. Are you using IIS or IHS as your webserver? If it is IIS I'd guess it might be the IIS Admin Service.
          Roger French
          Veteran Member
          Posts: 545
          Veteran Member
          6/20/2008 11:55 AM

            Using IIS, Already tried all of that... no go.

             

            Posted By Ben Coonfield on 6/19/2008 2:14 PM
            Do you mean that you go to the Websphere console Servers->Webserver, and you see a web server defined but the start button doesn't work? Not sure exactly how this works on Windows but on Unix there is a adminctl process that needs to be started. In windows I suspect that this would be a similar Windows service. Try going to control panel->Admin Tools->Services and look for a service that should be started and was not. Are you using IIS or IHS as your webserver? If it is IIS I'd guess it might be the IIS Admin Service.

             

            John Henley
            Posts: 3352
            6/20/2008 1:42 PM
              Was this configuration working at some previous time, or is this a brand new install?

              Make sure you are starting the other components (i.e. LSF9, etc.) in the correct order.

              Have you tried the /snoop servlet to see if this is an IIS plugin issue vs. Websphere?

              Is the websphere console available (e.g. port 9060)?



              Thanks for using the LawsonGuru.com forums!
              John
              Shasidhar Vemireddy
              Basic Member
              Posts: 14
              Basic Member
              7/6/2008 1:57 AM

                check your IIS plugin setup..it is not communicating with webserver setup in websphere.

                You are not authorized to post a reply.