Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs - Websphere

This is a discussion on Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs - Websphere ; I have had the same situation, (several times ), and what I found was : in the logs folder for the server, (e.g. ...\profiles\app\logs\server1 ) there is a file called server1.pid, in this case, this file, contains the process id ...

+ Reply to Thread
Results 1 to 13 of 13

Thread: Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

  1. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    I have had the same situation, (several times ), and what I found was :

    in the logs folder for the server, (e.g. ...\profiles\app\logs\server1 )
    there is a file called server1.pid, in this case, this file, contains the process id for the server process.

    This file it's supossed to be deleted when the server shuts down, but when the server crash down, or when some 'unusual' situation happens the file is not deleted, then when the server is trying to start and find this file, it doesn't start and give some weird exceptions, I don't know why, because I checked and the process id in the file most of the time it's not used by the OS, anyway the server simply doesn't start.

    What works in my case, was simply deleting the file, and start the server, and everything went fine.

    I hope this works for you too.

  2. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    Yup, this worked also for my WAS 6.1.

    Regards,
    guschra

  3. Re: ADMU7704E: Failed while trying to start the server - Delete the .pid file in logs

    On Jun 12, 2:43 am, wrote:
    > Yup, this worked also for my WAS 6.1.
    >
    > Regards,
    > guschra


    Yes this worked for me as well

    Thanks


  4. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    Works for me too. WAS 6.1.0.13

  5. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    On Feb 23, 6:24*am, vivek.sriniva...@cgi.com wrote:
    > Works for me too. WAS 6.1.0.13


    Works for me too. WAS 6.1

  6. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    It also worked for me to delete de server1.pid file that stores the process number

    I am using WAS 6.0.2.17 for Quickr 8.1.1

    Thanks!

  7. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    I had the same problem with WAS 6.1 windows version throwing "Service failed to start.startServer return code = -1" and DMGR was unable to start.

    Then after checking the SystemOut file came to know that I have added a line in winconfig.xml which would have caused the server to start and removed that line and started the server,,,, which worked fine for me.

    Thanks
    AnandRaj

  8. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    @ ANDRES_MOSCOSO--Thanks for the solution ..This works for me!!!

  9. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    This worked for me too.

    thanks !

  10. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    Hi all

    i am facing the same issue . I tried to follow the solution to delete
    server1.pid, but i dont have that file in the location specified.

    ANy other suggestion to fix the problem will really help.

    thanks

  11. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    Deleting the .pid file worked for me.

    Thanks for the resolution. to bad to see that these issues still occur.

  12. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    On Nov 23, 4:50*am, WdJong wrote:
    > Deleting the .pid file worked for me.
    >
    > Thanks for the resolution. to bad to see that these issues still occur.


    Well, I had the same issue. I didn't had the server1.pid file. To make
    WAS 6.1 behave I had to create a new server instance (I used the same
    profile) and things started working.

  13. Re: ADMU7704E: Failed while trying to start the server - Delete the.pid file in logs

    On 16 dic 2009, 16:27, Sandeep More wrote:
    > On Nov 23, 4:50*am, WdJong wrote:
    >
    > > Deleting the .pid file worked for me.

    >
    > > Thanks for the resolution. to bad to see that these issues still occur.

    >
    > Well, I had the same issue. I didn't had the server1.pid file. To make
    > WAS 6.1 behave I had to create a new server instance (I used the same
    > profile) and things started working.


    I can't delete the .pid file because it was not created. How can I
    create another server instance within the same profile if i'm not able
    to log on to the Console.

+ Reply to Thread