WAS - Start and Stop Server Problem on Windows

[Rajiv Bandaru]

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.<init>(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

   

[f malin]

Rajiv,
From what I can find on the web, it would appear that you are running vista:
http://forums.sun.com/thread.jspa?threadID=5209511&tstart=33390

If changing the user account control does not work, I would try to remove the server as a windows server, you may want to do this anyway since starting and stopping the server should be faster;
<WAS_HOME>/bin/WASService.exe -remove <nodeName>

The nodename is listed in the service panel in windows, or can be found in the <PROFILE_DIR>/config/cells/<cellName>/nodes/<nodeName>

This should remove the call which is failing.

Frank

[Rajiv Bandaru]

Frank,

Thank you very much for your time & effort to reply to my post. You guess it right, I'm running WAS on Vista. Changing the user account control did work very well.

Thank you again,

Rajiv