Home > Failed To > Service Failed To Start. Startserver Return Code = -1

Service Failed To Start. Startserver Return Code = -1

Contents

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 Log in to reply. But for real applications built by IBM, the windows service is a waste. SystemAdmin 110000D4XK 30895 Posts Re: ADMU7704E: Failed while trying to start the Windows Service associated with server ‏2006-09-27T15:29:36Z This is the accepted answer. http://justjoomla.net/failed-to/error-deploying-artifact-failed-to-transfer-file-return-code-is-401.html

Hope this helps. [ November 10, 2004: Message edited by: Jayadev Pulaparty ] [ November 10, 2004: Message edited by: Jayadev Pulaparty ] [ November 10, 2004: Message edited by: Jayadev I hope this works for you too. This is the accepted answer. Thanks a ton...

Service Failed To Start. Startserver Return Code = -1

java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:571) Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7704E: Failed while trying to start the Windows Service associated with server: server1; probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWA And i cant even starting WebSphere from Command Prompt. KumaraRagavan 2700038YRK 2 Posts Re: ADMU7704E: Failed while trying to start the Windows Service associated with server ‏2010-06-15T16:43:33Z This is the accepted answer.

SystemAdmin 110000D4XK 30895 Posts Re: ADMU7704E: Failed while trying to start the Windows Service associated with server ‏2007-05-16T08:55:55Z This is the accepted answer. SystemAdmin 110000D4XK 30895 Posts Re: ADMU7704E: Failed while trying to start the Windows Service associated with server ‏2006-09-26T06:34:53Z This is the accepted answer. Deleting the .pid file worked for me. Share?Profiles ▼Communities ▼Apps ▼ Forums WebSphere Portal Log in to participate Expanded section▼Topic Tags ?

Browse other questions tagged websphere or ask your own question. Admu7713e 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 Thanks AnandRaj Log in to reply. David Ulicny Ranch Hand Posts: 724 posted 12 years ago Starting application: EEER What is this?

More... SystemAdmin 110000D4XK 30895 Posts Re: ADMU7704E: Failed while trying to start the server - Delete the .pid file in logs ‏2009-07-16T06:57:34Z This is the accepted answer. When I issue WAS start or stop I get this Exception. How to fix it is actually not too hard, i just delete server1.pid which located under my WebSphere logs folder and start my WebSphere again.

Admu7713e

SystemAdmin 110000D4XK ‏2007-03-23T15:09:35Z 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 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 Service Failed To Start. Startserver Return Code = -1 More... Admu3011e: Server Launched But Failed Initialization. WAS 6.1.0.13 Log in to reply.

[email protected] wrote: > Hi All, > > Each time i start my portal server, it gives the following exception in command prompt although it do start the server. > > Caused http://justjoomla.net/failed-to/failed-to-start-service-jboss-deployment-subunit-post-module.html Log in to reply. This is the location for my logs folder C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1 Have fun Google+ Java javaee utility web websphere edwin Related Posts [nginx] Replacing HTTP 302 Location URL from HTTP to HTTPS Thanks.

WASService -remove amsdevNode01 -serverName -profilePath -washome Note: washomepath will be like this "E:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config" Add service again using WASService " WASService -add amsdevNode01 -serverName -profilePath -washome SystemAdmin 110000D4XK ‏2007-06-12T07:43:07Z Yup, this worked also for my WAS 6.1. If websphere does not get start then restart machine once. Check This Out Its fixed my issue.

I am getting the following error "ADMU7704E: Failed while trying to start the Windows Service associated with server: server1; probable error executing WASService.exe" On some sites a workaround was to delete Hi, Look at this link: http://support.microsoft.com/kb/839803 Erwin Karbasi Development Architect Optinity eSolutions Log in to reply. SCJP
SCWCD
ICSD(286)
MCP 70-216 Jayadev Pulaparty Ranch Hand Posts: 662 posted 12 years ago I fought the same error sometime back.

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

Can anybody solve this issue?? 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 This is the accepted answer. I am having the same problem.

If your app server has a 500 meg footprint, which is the minimum practially with WebSphere, then just filling that memeory will take longer than the service is willing to wait. Difference between if else and && || How do you convince someone that parallel lines can touch? Windows service? this contact form Thanking in anticipation Log in to reply.

Log in to reply. Thanks in advance.:) More... more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed SystemAdmin 110000D4XK ‏2007-03-23T15:09:35Z 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