This tutorial is designed for WebLogic 10 – 11 installations on Windows Server Operating Systems.
Having issues starting the Weblogic Admin Server Service within the windows services console? Are the Admin logs not updating with pertinent server information required to resolve the problem? Follow the steps below to debug the Oracle Weblogic Admin Server. This tutorial has been tested on Windows Server R2 2003-2012. By executing the Debug tool via the windows command prompt, you will be provided detailed and comprehensive information needed to troubleshoot the exact reason your Administration Server has failed to start. Follow the simple steps below.
1, locate where the beasvc.exe is located within the directory of your WebLogic Installation folder, for example it could be — C:\WL_HOME\server\bin\beasvc.exe
2. Open the services console and copy the Service Name of the WebLogic Admin Server service.
note: The name of the admin service should be located in the services console, double-click the admin service and copy the information located under the Service Name field.
3. Open a command prompt and execute the following command
C:\WL_HOME\server\bin\beasvc.exe -debug “<Name of the Admin Service>”
4. Press [Enter]
You should receive detailed information needed to troubleshoot why the Admin server has failed to start