Hi,
I am getting the S1001 issue. I have reinstalled the Plex media server, deleted database, and tried everything the help suggests except repairing the Plex database as I tried that and I don’t think that solved the issue.
I have attached the logs and if anyone can help, I would greatly appreciate it.
Server Version#: Version 1.24.0.4930
Player Version#: Version 4.59.2
Hello,
Bumping for visibility.
Bumping again for visibility. Can you please let me know why my pre-rolls aren’t working? The logs are not vebrose and please see the last few lines.
Bump for visibility.
I see the same problem. Only happens when the client is transcoding from what I’ve seen. Removing pre-rolls fixes the issue, but I sure miss having pre-rolls on my server.
Yeah, I want to add pre-rolls as it’s a great feature. But no dice.
I had a similar issue a while ago regarding s1001 error, this is based on how the system re-owned items upon upgrade, I would assume the same thing is occurring for your pre-rolls:
Basically:
Why?
I had a similar issue, but my data was on the same volume. This was due to the way file systems own data for a user.
Data is not actually owned by the Username , but rather a User ID .
e.g.
**user1 = 1001
user2 = 1002
**
When you upgrade the media server it literally recreates the username “ plex ”, every time, this actually creates a NEW USER ID in the jail,
e.g.
plex=1001 original user/owner
plex=1002 new user /non-owner
but doesn’t tell it to reacquire ownership of items belonging to that username.
What’s happening here?
The old one (plex=uid 1001) doesn’t exist, but the environment still recognizes the old user “plex (uid 1001)” as the owner as well as the new user “plex” (uid 1002), which creates the confusion.
Resolution
I corrected this by “re-owning” all files owned by the user “plex” to the new user “plex”
See this topic for a better explanation shaka1001 (Network)
Thanks. But I am not sure what do you mean by logging into my own jail? Can you ELI5 please?
@habibq, Jails are for NAS or “Applianced” typed servers.
They are contained environments with a Unix os such as FreeBSD or FreeNAS.
I’m assuming that you are using a Unix/Linux-based server?
Overall simply log into the server ( not always a jailed environment ).
Then try to understand the following:
Basically:
Why?
I had a similar issue, but my data was on the same volume. This was due to the way file systems own data for a user.
Data is not actually owned by the Username , but rather a User ID .
e.g.
**user1 = 1001
user2 = 1002
**
When you upgrade the media server it literally recreates the username “ plex ”, every time, this actually creates a NEW USER ID in the jail,
e.g.
plex=1001 original user/owner
plex=1002 new user /non-owner
but doesn’t tell it to reacquire ownership of items belonging to that username.
What’s happening here?
The old one (plex=uid 1001) doesn’t exist, but the environment still recognizes the old user “plex (uid 1001)” as the owner as well as the new user “plex” (uid 1002), which creates the confusion.
Resolution
I corrected this by “re-owning” all files owned by the user “plex” to the new user “plex”
Hi,
I am actually not in a Unix/Linux-based server but on Windows 11.
The narrative here is: You are playing with fire
Windows 11 is barely even a few months old, and you’re expecting Plex to run without issue.
You probably should have stated that, to begin with, although OS type/version still may not be your issue.
Try backing up your Plex metadata folders, then reinstalling Plex.
On Windows, the content is located inside of the user directory.
e.g.
%LOCALAPPDATA%\ Plex Media Server.
Note: Desktop machines are not typically set up to handle serviced software such as Plex, even with the proper hardware, it’s still hell on the on its’ Unrelated Processes, Memory, CPU, Hard Drives , etc.
I’d always suggest acquiring knowledge and a bit of experience on a NAS Server or “Appliance” typed setup, but can understand why you’d choose a Windows Desktop, as it may simply be a situation of " The Devil you know" 
And… while Windows 11 itself is still not quite in the “Production” phase as many companies have elected to wait until the bugs/kinks are removed (per usual), it is in such a decent state that as I’m typing this message I am running an Unsupported Windows 11 on Mac Bootcamp set up.
I’ll admit I love Unix/Linux, but I started off using Windows and can agree wholeheartedly that it is a systematized orchestra of user conveniences, which can make things a bit more complicated when looking for a resolution 
Hi,
TBH I only updated to Win 11 a month ago, as I had this issue on Windows 10, even after doing a fresh reinstall.
As for backing up, resintalli9ng and the content, I already did that when I reinstalled Windows 10. I guess it’s just an issue I will have to live with.
As for NAS, that would be an ideal situation but I am not in a situation where I can spend more money.
Thank you anyways for your support.
No worries @habibq , I completely understand.
In regards to your issues, try checking the permissions on the local installed areas
e.g
Startmenu> type %AppData%
Careful playing around in there, you don’t want to butcher other installations that write in this area .
As for starting a NAS project, you don’t need a fancy setup to get there, NAS is meant to be a lightweight OS, even an older used PC (like one that’s likely been sitting in the basement for years), would suffice as long as you don’t add a tone of people to your Plex account or only use it locally (in-home).
The thing about setting up a NAS for the first time is that once it’s done, you’ll have more knowledge and understanding about Unix/BSD type setups as well as the unpredictability of Windows, especially when using it as an appliance.
Good luck and stay safe man!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
