WME 4.6.0.01 Windows Service Not Starting

Wowza Streaming Engine
1

Hello,

I updated to 4.6.0.01 yesterday and at the same time updated to Java 8u111.

Now the service will not start. However, running startup.bat and startmgr.bat manually works fine.

Here are entries from the event log for the manager service:

Service WowzaStreamingEngineManager403 received START control, which will be handled.
Started C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.3\manager\bin\startmgr.bat service for service WowzaStreamingEngineManager403 in C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.3\manager\bin.
Program C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.3\manager\bin\startmgr.bat for service WowzaStreamingEngineManager403 exited with return code 0.
Killing process tree of process 2568 for service WowzaStreamingEngineManager403 with exit code 0
Killing PID 2568 in process tree of PID 2568 because service WowzaStreamingEngineManager403 is stopping.
Service WowzaStreamingEngineManager403 action for exit code 0 is Exit. Exiting.
Requested stop of service WowzaStreamingEngineManager403.  No action is required as program C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.3\manager\bin\startmgr.bat is not running.

The same happens for the streaming engine.

The host OS is Windows Server 2012 R2.

Any ideas?

2

This thread seems to be related.

JAVA_HOME is correct in the system environment variables, but wowza is holding onto the old location.

echoing JAVA_HOME in command prompt prints the correct location as well.

3

Found the solution here tucked away in a tiny note. Manually set WMSJAVA_HOME. Which is odd since I upgraded from a working 4.3.0 install.

And doesn’t explain why setenv.bat is reporting JAVA_HOME incorrectly.