Closed AnthonyBe closed 1 year ago
Try setting it to automatic delayed. It doesn't do much on start, but If the system is busy or some other dependant service hasn't started yet, it might not be able to complete quick enough. The windows service manager has pretty tight return times for a start.
I'm pretty sure I've also tried that, but I'll give it another go just to be sure.
There is a lot going on on my server, and being a NAS (HP Microserver Gen 8) they aren't the fastest in starting everything up. I am also running Hyper-V on it with 2 VMs but that defaults to a delayed startup.
Finally had a reason to restart my server (Patch Tuesday) and setting the PlexService to Automatic (Delayed) seems to have worked this time.
I've been running into this slightly annoying issue ever since I updated from v1.1.7 to v1.2.0 and it persists with v1.2.1 I'm running Plex x64 on a Windows Server 2012 R2 server.
When I reboot the server, the PlexService never starts automatically. After I log in, I can manually start it without any problem. It will then work perfectly, handle PMS updates, etc. just fine. It just won't auto-start on server reboot. There are no errors which makes it even harder for me to troubleshoot.
The PlexService service is set to Automatic startup The PlexService service is configured to run under the local Administrator account (I know, bad practice.. but it works..)
After I reboot the server, this is what I see in the System Event Log:
As mentioned, when I manually start the service, it is happy and logs the following:
This is a sample of the PlexService.log on a day when I rebooted the server, note that 13:36 is when the service failed to start automatically, and 13:56 is when it was successfully manually started. At 13:36, nothing is logged.
Is there anything I'm missing that would be preventing the PlexService from starting automatically on server reboot? Or anything I could change and try to resolve this? Thanks!