WAS - Start and Stop Server Problem on Windows

[r***@gmail.com]

Hello,

I need some help trying to start and stop Websphere Application Server. When I issue WAS start or stop I get this Exception. Could anyone direct me how to get this resolved on windows OS.

*ADMU7707E: Failed while trying to determine the Windows Service name for server: server1;*

+---Complete Exception Trace, when I issues stop server---+

java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
at org.eclipse.core.launcher.Main.run(Main.java:981)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:330)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:108)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7707E: Failed while trying to determine the Windows Service name for server: server1;
probable error executing WASService.exe: com.ibm.websphere.management.exception.AdminException: ADMU7709E: Unexpected exception while processing server: server1; exception = java.io.IOException: Cannot run program "C:\IBMWAS\WebSphere\AppServer\bin\WASService.exe": CreateProcess error=740, The requested operation requires elevation.
at com.ibm.ws.management.tools.WindowsService.getWindowsServiceNameForServer(WindowsService.java:221)
at com.ibm.ws.management.tools.WindowsService.(WindowsService.java:154)
at com.ibm.ws.management.tools.WindowsService.getWindowsServiceInstance(WindowsService.java:139)
at com.ibm.ws.management.tools.WsServerController.getWindowsServiceIfAvailable(WsServerController.java:161)
at com.ibm.ws.management.tools.WsServerStop.getWindowsServiceIfAvailable(WsServerStop.java:129)
at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindows(WsServerController.java:129)
at com.ibm.ws.management.tools.WsServerStop.main(WsServerStop.java:113)
... 21 more

[Tsaby]

Hi try to create (re-create) a Windows service for the WAS server,
with the WASService command.

http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1/topic/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html?resultof=%22%57%41%53%53%65%72%76%69%63%65%22%20%22%77%61%73%73%65%72%76%69%63%22%20

[k***@kaz-group.com]

The key is in

*CreateProcess error=740, The requested operation requires elevation.*

This is an error returned from Vista when the command needs to be executed as an Administrator.

Log in with an Administrator accoutn to ersolve hte problem.

[r***@gmail.com]

Log in with an Administrator accoutn to ersolve hte problem.

Well, I was logging in as administrator when I got this error. I do have a workaround for this issue, but not a permanent fix. In windows vista, in the User Accounts I turned off the "User Account Control" for the windows id I using to work on WAS. Since then I am not having problems issuing WAS start or stop commands.

But I would like to know if there is a permanent fix. One of my ex-colleagues told me that I could install WAS not as a service in windows. Hearing this, I uninstalled WAS and re-installed. While re-installing, I was watchful every step to uncheck "run WAS as a windows service", but I found it nowhere during the installation.

It would be great to know how to WAS installation on windows not as windows service.

Thank you Kenneth_Beaton for your response. I appreciate your time & effort.

[w***@cn.ibm.com]

To make WAS installation on windows not as windows service, you can't select default installation(typical installation) in the installation process, select the other option.

[k***@yahoo.co.in]

try using wasservice -remove service_name in ibm_install/bin directory

[k***@yahoo.co.in]

Hi,

If you click the option "run the server as Windows service" , make note of the service name from Windows service registry (or) execute the start script with correct service from the bin directory

type (on Windows)"startServer.bat -help" to find multiple option to start the server
thanks,
karuppiah