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.
Joined: Jan 30, 2009
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,
subject: WAS - Start and Stop Server Problem on Windows