# WME 4.6.0.01 Windows Service Not Starting

**URL:** https://community.wowza.com/t/wme-4-6-0-01-windows-service-not-starting/47808
**Category:** Wowza Streaming Engine
**Tags:** server-administration
**Created:** [December 20, 2016, 9:54am UTC](https://community.wowza.com/t/wme-4-6-0-01-windows-service-not-starting/47808 "2016-12-20T09:54:06Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Will\_Polley](https://avatars.discourse-cdn.com/v4/letter/w/a5b964/32.png) [@Will\_Polley](https://community.wowza.com/u/Will_Polley)
#### Post date: [December 20, 2016, 9:54am UTC](https://community.wowza.com/t/wme-4-6-0-01-windows-service-not-starting/47808/1 "2016-12-20T09:54:06Z")

</div>

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:

```auto
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?

---

<div class="post-metadata">

### Author: ![Will\_Polley](https://avatars.discourse-cdn.com/v4/letter/w/a5b964/32.png) [@Will\_Polley](https://community.wowza.com/u/Will_Polley)
#### Post date: [December 20, 2016, 10:02am UTC](https://community.wowza.com/t/wme-4-6-0-01-windows-service-not-starting/47808/2 "2016-12-20T10:02:41Z")

</div>

This [thread](http://community.wowza.com/t/-/39819) 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.

---

<div class="post-metadata">

### Author: ![Will\_Polley](https://avatars.discourse-cdn.com/v4/letter/w/a5b964/32.png) [@Will\_Polley](https://community.wowza.com/u/Will_Polley)
#### Post date: [December 20, 2016, 10:23am UTC](https://community.wowza.com/t/wme-4-6-0-01-windows-service-not-starting/47808/3 "2016-12-20T10:23:16Z")

</div>

Found the solution [here](https://www.wowza.com/docs/how-to-manually-install-and-troubleshoot-java-on-your-wowza-media-server) 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.
