I have an odd issue. For a long time now i have been using the pms service for plex. Now while trying to use the standard launch plex media server icon i get an error saying corrupt database. I can still launch it as a service with no issues but not without the service.
if i try rolling back to a previous version of the DB i am able to start plex with the standard plex executable but then i cant access the web interface at all. if i launch the pms service i then can access plex web but then get the error message again if i try using the standard plex executable.
Which Windows user account did you select for the service to run under?
If it was the ‘SYSTEM’ account (or any other Windows user account not identical to your regular Windows user), then the regular Windows user you are using has no write permissions to the files created by the service.
Which could explain the error message you get when trying to start the server in the regular way.
You will have to untangle the file and foder access permissions in the Plex data folder if you want to run Plex server in the ordinary way.
Post scriptum: It is a horrible idea in general to run plex under the SYSTEM account.
If you are using Plex as a service, I recommend you to run it either under your own Windows user account or to create a dedicated Windows user account just for Plex.
all processes are stopped totally in the pms service, and windows service. i confirmed it all in task manager.
the ownership permissions are all set correctly and im able to see files get created correctly in the folder so i know the read and write are working as its supposed to.
Dont forget im also using the exact same account for the service and regular.
In the logs i also see plex starting correctly which is why im so confused. no errors or warnings to note
You cannot possibly verify that for each and every subfolder and every file in there. There are millions of files and folders in a bigger Plex installation.
powershell command get-childitem -recurse > c:\PlexPerm.txt will send it to a file for you to peruse. difficult but not impossible to verify.
If the database did get damged like that, wont the service have an issue running it to begin with? it should fail to start as both a service and regular since the service launches the program in the background.