Latest Update - Transcode Errors, DB Errors, Etc. - Steps to recover

Plex Media Server
1

Server Version#: 1.30.0.6406
Player Version#: 4.87.2

Been seeing some other users report various issues post updates. Here’s some steps, pitfalls and the approach I used to get my long running server back online and working.

Problem:
So basically my Plex server has been in existence for 5+ years. I have migrated this server 3 times (Windows 10 → Server 2016 → Server 2022). I have fully migrated all APPDATA each time as I did NOT want to lose plays, metadata and thumbnails. Plex APPDATA directory was near 1TB! I used to utilize plugins and various extra features.

I have encountered various problems, SQL errors, metadata growth, general issues and warnings in the logs. Slow Queries, invalid fields, transcode errors, etc. etc.

The typical fixes included updating the software and doing all tasks in “Fixing a corrupt database…”. But nothing seemed to fully fix the implementation.

This culminated in a unusable state after the latest update which took place yesterday. This presented as the transcoder wouldn’t work, database throwing all kinds of errors and my family contacting me trying to figure out why their TVs were stuttering.

Resolution:

I semi-wiped my APPDATA directory and recovered…

Steps and Pitfalls:

  1. Understand that following this method will create a bunch of work… You will have to reclaim your server, rebuild settings, re-share with friends, spend an hour of your time and potentially lose everything - But if it goes correctly you will retain your play history, your metadata and thumbnails.
  2. Open PMS and sign out - I also logged out every device authenticated to this server (User Account Settings)
  3. Stop PMS server/service
  4. Run all tasks in Plex’s guide for “Repairing a corrupt database…”
  5. Rename APPDATA folder “Plex Media Server”
  6. Export Plex Registry Keys - Just in case
  7. Delete all Plex registry keys
  8. Uninstall Plex Media Server application in control panel (I also uninstalled all .net Visual Studio distributions - likely not necessary)
  9. Delete any remaining Plex folders in Program Files (if exist)
  10. Download latest PMS
  11. Install…
  12. Start server and follow steps to create a new server → Friendly name should match previous server
  13. You’ll have to login and claim? Maybe? Also change some applicable settings: Empty Trash to off, various stuff that you want/need
  14. Shutdown/Exit PMS/plex services
  15. Go back to your renamed APPDATA folder. Copy the following items to the newly created APPDATA folder: Library DB, Library Blobs DB, Metadata and (Friendly Name) folder. - I did not copy my Cache folder as I wanted Plex to rebuild that. It also stores certs and was running into many server claiming issues.
  16. Restart PMS. You should see all items repopulated. Rebuild your PMS settings. Rebuild your pinned/dashboard settings. Reshare whatever you want to friends. Check the logs. Hopefully you have what I found:

PRISTINE! - NO ERRORS, NO PROBLEMS, HAPPY USERS :smiley:

2

Now uninstall 1.30.0.6406 and install Plex Media Server 1.29.2.6364 and wait till the next public release if you want a stable server through to the end of the year.

1.30 is well and truly a preview edition with updated FFMPEG and a few regressions.

3

The above list is missing the re-import of the registry settings. If you miss doing so, you’ll have to re-share the new server with each of your previously shared users.

4

Every time I imported registry the server would go unconnectable. I had a bunch of TLS errors… ?

Nothing I tried could get the server to recognize as the same machine.

I did have to re-share with my users but this was a small price to pay to actually have it working.

5

Since completing all the above steps I had no issues with the latest version. I DO have hardware acceleration enabled and an NVIDIA P2000. Don’t know if that has anything to do with the updated FFMPEG. But everything is working on this end.