After the most recent update my Plex Media Server crashes only a few seconds after launching. The Server is running on Windows 10. I’ve attempted a system reboot. Only error that I can find in the logs is “Failed to grant application loopback exemption” When I run the loopback exemption from an elevated CMD prompt the exception is granted successfully. “PS C:\WINDOWS\system32> CheckNetIsolation LoopbackExempt -a “-n=caf9e577.plex_aam28m9va5cke”
OK.”
No recent applications have been installed or updated on this server. Windows has not been updated since this issue began.
Also, I ran AV and Malware scans and both returned clean.
I’m not sure who to reach out to regarding this issue. Can you please point me in the right direction?
Thanks for the logs - I found a number of uploaded crash reports for your server. running Plex Media Server 1.23.2.4656-85f0adf5b
Could you get me copies of the following database files - zipped. If too big to attach to a message please upload somewhere eg dropbox/google drive etc and send me link by Private Message. Please send to me and @BigWheel as I am only working one day a week (on Tuesdays)
The database files to copy out and zip are:
C:\Users\Rob\AppData\Local\Plex Media Server\Plug-in Support\Databases\com.plexapp.plugins.library.db
C:\Users\Rob\AppData\Local\Plex Media Server\Plug-in Support\Databases\com.plexapp.plugins.library.db-wal
C:\Users\Rob\AppData\Local\Plex Media Server\Plug-in Support\Databases\com.plexapp.plugins.library.db-shm
Also the 3 files in that directory with db filenames starting with tv.plex.providers.epg.
Thanks for the reply. @BigWheel noticed an entry in the logs related to a DVR schedule for upcoming events. The logs didn’t list an error related to this but it was the last entry before crash on multiple occasions. I was able to bring up the server long enough to delete this schedule and since then the server has been stable again. I noticed that the DVR needed to update the guide. I’m not sure if the update coinciding with the schedule entry was causing a conflict. That schedule had been in place for weeks so I believe the guide update was the trigger.
