Thanks for your answer.
I just tried and indeed that works.
But the problem with Automatically (delayed) is that it kicks in after 120 seconds after boot.
That’s a tad to long for me. I’ve put the SSD in to get some more performance (faster boot etc) so if I have to wait 2 minutes before Plex works that’s not really an upgrade…
Though this tells us what the problem is.
Probably it’s to fast to load the service after boot.
Well I am still using HDDs so 120 seconds is good enough for me and my auto reboots are only weekly (just to make sure windows does not clog up)
Created a workaround for my problem:
Set the service PlexService from automatic to manual.
Created a batch file with the following content:
timeout /t 5
NET START PlexService
Scheduled a task in the tasks scheduler to run at start up and the action to take is run the batch file.
I just noticed another problem with PMS as a service.
If I stop and start the PlexService in services.msc multiple times I’m getting an error in the logs:
There is already a listener on IP endpoint 0.0.0.0:8787.
This could happen if there is another application already
listening on this endpoint or if you have multiple service
endpoints in your service host with the same IP endpoint
but with incompatible binding configurations.
Is there a way to fix this?
I think you have an environment issue. I don’t have any of the issues you’ve listed over the past few days and I’m running a Windows Server box that reboots every other day. You may have a compatibility issue within Win2016 and the service wrapper, or a configuration issue within Windows.
I know the service isn’t perfect, but again, I don’t have any errors restarting the services from services.msc multiple times.
Do you run Server 2016 as well?
No, but with only one data point, it’s not really fair to point the issue at PMS and ignore the OS configuration…
What do you mean with “only one data point”?
I’m not pointing at anyone or anything.
Just trying to get my problem resolved.
Maybe it’s just Server 2016. Are you running 2012r2?
You’re definitively pointing at PMS as the problem. Regardless of your OS, it could be a conflict in how you’ve configured your OS, not the specific OS or the PMS as a service program itself.
“One data point” means this isn’t a commonly reported issue, being that your data point (report of an issue) is the only “data point” (statistically speaking) that points to this being an issue.
I’m working on spinning up a clean W2016 machine in a VM to test that 2016 is or isn’t the issue.
Yes, I run 2012r2 for my PMS.
English is not my mother tongue.
So apologies if I come on over to strong.
When I have some time I’ll give 2012r2 a spin myself. Eager to hear your results as well.
It’s quite alright, I just wanted to make sure of where the problem actually existed. I thought somewhere someone here had reported W2016 was working without an issue.
Will be reinstalling everything and start from scratch.
Morning All
I’m getting ‘unable to connect’ in the service tray app, which I think is connecting to service. I have PMS up and running correctly on this machine on 32400. This server is 2016 server with GUI.
I have the Tray configured to 8787 as per the default install, but It’s not connecting. I can control the service via the service.msc app but I’d like to understand why this tray app doesn’t work.
Can someone tell me, whcih file/setting for the service which sets the port? so I can check it’s at 8787 too
This machine, is a single NIC which is not multi homed. Ports 8787 and 32400 are allowed on windows firewall for birectional traffic. (on a private network)
see the picture
So hardware transcoding is still not working when running Plex as a service right?
Don’t worry, I’ve found it.
%appdata%\plex service\setting.json and corrected the ServerPort setting.
However I think this exposes a bug where the tray looks at LocalSetting.json and the Service wrapper is looking at Settings.json.
Thank you ever so much for this cjmurph. Worked perfect on my Server 2012 essentials.
Been trying to solve this for a while. Much appreciated:slightly_smiling_face:
I wanted to let you all know I have this working on Windows Server 2019 with no issues. Thanks again for creating and supporting this @cjmurph!
+1, same here
Works perfectly since almost a year now on Windows Server 1709 (pure core version - semi annual channel)
Planning on migrating it to 1809 soon… 
