The Connection Server

I remember the first time I had to work out why WebLogic wouldn't run as a service. It was a frustrating experience. There were no error messages. No Windows error dialog. No console output. How do you troubleshoot something like this??!! This short article will show you. For simplicity I'll talk about the node manager, but the same principles apply for running an admin or managed server as a service. First Steps First, you still have your server logs. Sure the console output is better, but it's a starting point. Check this log for errors and especially take note of the start up variables such as PATH and CLASSPATH. If the server log isn't being created, that tells you WebLogic probably isn't even being started. (Check that you have a license file if you haven't already.) Ok, so the logs were no help. The next step is to look at how the service is trying to start WebLogic. When you install WebLogic as a service, you're really setting up beasvc.exe as the ser...