By lmestre on Apr 07, 2014
Debugging WebLogic Server Windows Services can be a hard time. Sometimes it is difficult to collect debug information and in other cases, you can't even start it.
So here is my super hero "beasvc -debug"!
You can try :
beasvc -debug "Windows Service Name"
That will really show you the real error when you are not even able to start your windows service.
You can read more information about installing weblogic server as windows service in this My Oracle Support(MOS) documents(*):
How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
Other useful documents that are useful when you need to collect debug information when you are using a Windows Service
How Do I Get A Java Heap Dump When Running Weblogic As A Windows Service? (Hotspot JVM) (Doc ID 1264826.1)
Enabling stdout Logging and Generating Thread Dumps When Running WebLogic Server as a Windows service (Doc ID 858746.1)
How to connect to a remote JRockit Java Virtual Machine using JRockit Mission Control (Doc ID 1075329.1)
How to Monitor using JRockit Mission Control a WebLogic Server instance on top of JRockit JVM running as a Windows service (Doc ID 1329897.1)
(*) Links will work if you are logged to MOS.