Server Version#: 1.28.1.6018
I am currently seeing these kind of errors in the logs and there are really a lot of them
Aug 04, 2022 08:39:00.934 [10920] ERROR - Couldn't copy file "E:\Plex\Plex Media Server\Metadata\Albums\0\1964fa901406495d00daf166551db331f2bd8f9.bundle\Contents\_stored\posters\tv.plex.agents.music_512cc310adc5bc070be53db6a0edbf7b01cf4bb8" to "E:\Plex\Plex Media Server\Metadata\Albums\0\1964fa901406495d00daf166551db331f2bd8f9.bundle\Contents\_combined\posters\tv.plex.agents.music_512cc310adc5bc070be53db6a0edbf7b01cf4bb8": The file exists
Aug 04, 2022 08:39:00.934 [10920] ERROR - Couldn't rename file "E:\Plex\Plex Media Server\Metadata\Albums\0\1964fa901406495d00daf166551db331f2bd8f9.bundle\Contents\_stored" to "E:\Plex\Plex Media Server\Metadata\Albums\0\1964fa901406495d00daf166551db331f2bd8f9.bundle\Contents\_combined": Access is denied
Aug 04, 2022 08:39:00.935 [10920] ERROR - Couldn't copy file "E:\Plex\Plex Media Server\Metadata\Albums\0\1eabf93631a7d6724bcdc5f4105c3a09c921df9.bundle\Contents\_stored\posters\tv.plex.agents.music_ab3870cf03708357a5eef9ed32c9cf209321c85d" to "E:\Plex\Plex Media Server\Metadata\Albums\0\1eabf93631a7d6724bcdc5f4105c3a09c921df9.bundle\Contents\_combined\posters\tv.plex.agents.music_ab3870cf03708357a5eef9ed32c9cf209321c85d": The file exists
Aug 04, 2022 08:39:00.935 [10920] ERROR - Couldn't rename file "E:\Plex\Plex Media Server\Metadata\Albums\0\1eabf93631a7d6724bcdc5f4105c3a09c921df9.bundle\Contents\_stored" to "E:\Plex\Plex Media Server\Metadata\Albums\0\1eabf93631a7d6724bcdc5f4105c3a09c921df9.bundle\Contents\_combined": Access is denied
The folders under E:\Plex\Plex Media Server have the right permissions and nothing has been changed lately.
I think it started with the previous update but am not 100% sure
Have you ever started PMS “As Administrator”?
Tell your anti virus to leave E:\Plex alone and not interfere in there.
Don’t point other software tools to this folder either, like backup software, cloud sync, photo managers etc – at least while Plex server is running.
It is not only about writes. Read operations can also set a file lock.
You should shut down the server for backup. Otherwise, you will miss some files in the backup. Crucially the currently used database file will be either missing or corrupt in the backup.
I meant have you ever run PMS under the Administrator or the SYSTEM account? Even if it was just once?
If you did, those particular files could still be owned by these higher-privileged user accounts. To fix that, you will have to reset the ownership and access permissions of each folder, subfolder and each single file within.
Here is a comfortable tool to achieve that Resetting NTFS files permission in Windows – Graphical Utility – lallous' lab
Didn’t know that about the backup issue. Will look into this.
I don’t remember running Plex under the SYSTEM account. It used to start before as a service but with my account - which is an administrator account.
What should I reset ownership to in those files and folders with the tool, you linked to?
To the currently used Windows user account, which is linked to the scheduled task to start PMS.
I’ve reset ownership of E:\Plex\Plex Media Server - and subfolders, etc to the Windows user account that launches PMS from Task Scheduler and it looked fine but the errors are back.
What I’ve found out is that the owner of the Plex executable is SYSTEM
Don’t know if it is as it should
Leave everything as-is for the executables folder.
Did you perform the permissions reset while PMS was shut down? It should have been.
Perform CHKDSK for drive E:
If that doesn’t report any errors, repeat with surface scan.
As a last-ditch attempt, try Plex Dancing the media item that’s connected to the poster.
Thanks. Otto
It looks like the errors are triggered by a sort of migration:
Aug 04, 2022 11:34:46.526 [5820] INFO - Running migrations. (EPG 0)
Plex works fine otherwise. The only thing is that the Plex Media Server.log files are about 500 KB and there is a lot of writing
Absolutely not. This has nothing to do with the error.
Do you have Debug logging activated?
Then your logs are pretty much useless for debugging purposes. Like finding out what the errors are connected to.
(don’t enable Verbose)
I’ve enabled Debug logging.
Will restart PMS and see if there are any clues. Be right back 
Debug logging on.
Can’t see the same errors now but I really don’t know what to look for.
Should I upload the debug logs?
Let it run for a few hours.
Look at the timestamps in the older logs. Did the errors perhaps occur during the server maintenance period? Then you’ll have to wait until after the next maintenance.
Yes. It looks like the errors occur in the maintenance period - 8.00 to 17.00 (when usually none in my family is using Plex) -
I’ll look tomorrow after 8.00 and upload the logs then.
Many thanks!
It is important to fetch the logs before it is again being used for watching etc.
Otherwise the errors could be flushed out by all the newer activity.
Do consider shortening the maintenance period (max. 2 hrs) and set its begin a little closer to when you are coming home.
Perfect. Wasn’t aware of that.
I’ll upload logs a little later on and set the maintenance window to 2 hours
I have a fresh set of logs but curiously can’t find the same errors. May be I’m not looking at the right place.
How do I upload the logs? There seems to be plenty identifiable info in them: email address, IP address, media titles, etc.
