Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

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

2,890 views
Skip to first unread message

aami...@gmail.com

unread,
Sep 14, 2006, 2:37:43 AM9/14/06
to
Hi All,

Each time i start my portal server, it gives the following exception in command prompt although it do start the server.

Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7704E: Failed while trying to start the Windows Service associated with server: WebSphere_Portal;probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWASServiceException: ADMU7711E: Unexpected exception associated with WASService.exe: exitCode = -1 during processing of server with name: WebSphere_Portal

Can anyone one point out how to fix it?

Thanking in anticipation

mrosenthalchicago

unread,
Sep 22, 2006, 12:28:11 PM9/22/06
to
Did you ever get any response from this? I am having the same problem.

aami...@gmail.com

unread,
Sep 26, 2006, 2:34:53 AM9/26/06
to
Can anybody solve this issue??

L D Jones

unread,
Sep 27, 2006, 11:29:36 AM9/27/06
to

amos...@yahoo.com

unread,
Mar 23, 2007, 11:09:35 AM3/23/07
to
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.

miwa...@de.ibm.com

unread,
May 16, 2007, 4:55:55 AM5/16/07
to

erw...@matrix.co.il

unread,
Jun 12, 2007, 2:36:33 AM6/12/07
to
Hi,

Look at this link:

http://support.microsoft.com/kb/839803

Erwin Karbasi
Development Architect
Optinity eSolutions

gunnar....@gmail.com

unread,
Jun 12, 2007, 3:43:07 AM6/12/07
to
Yup, this worked also for my WAS 6.1.

Regards,
guschra

ms.si...@gmail.com

unread,
Jun 27, 2007, 5:45:16 PM6/27/07
to

Yes this worked for me as well

Thanks

vivek.sr...@cgi.com

unread,
Feb 22, 2008, 8:24:30 PM2/22/08
to
Works for me too. WAS 6.1.0.13

agarwa...@gmail.com

unread,
Mar 14, 2008, 9:05:15 AM3/14/08
to

sanchez...@es.ibm.com

unread,
Jan 19, 2009, 11:31:45 AM1/19/09
to
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!

a.pu...@gmail.com

unread,
Apr 15, 2009, 5:19:25 AM4/15/09
to
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

arnab_...@infosys.com

unread,
Jun 18, 2009, 2:51:00 PM6/18/09
to
@ ANDRES_MOSCOSO--Thanks for the solution ..This works for me!!!

sudg...@in.ibm.com

unread,
Jul 16, 2009, 2:57:34 AM7/16/09
to
This worked for me too.
:)
thanks !

Nishi

unread,
Aug 6, 2009, 3:59:38 PM8/6/09
to
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

WdJong

unread,
Nov 23, 2009, 5:50:52 AM11/23/09
to
Deleting the .pid file worked for me.

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

Sandeep More

unread,
Dec 16, 2009, 5:27:59 PM12/16/09
to
On Nov 23, 4:50 am, WdJong <werner.de.j...@nl.ibm.com> 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.

Ktrino

unread,
Jan 7, 2010, 11:18:54 AM1/7/10
to

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.

0 new messages