TV recommended pages won't load, some TV shows fail to play on latest version

Plex Media Server
,
1

I’ve had a problem for a while with my Home & TV recommended page loading quite slowly, but the latest version upgrade (1.25.9.5721-965587f64) of Plex completely broke my TV recommended page and also broke several shows so that I cannot watch them.

I have relatively succinct logs of the different problems happening with both Plex versions that hopefully help to pinpoint what is different between the two versions.

logs_to_share.zip (116.1 KB)

Older Server Version: 1.25.7.5604-980a13e02

Player (Web): 4.78.4 (though this also happens on iOS or ShieldTVs)

Behavior Observed:

  • TV recommended page loads very slowly (15+ seconds) or fails to load, but when I click “reload” on the recommended page, it will eventually reload the recommendations.
  • All TV shows play fine

Frequent Errors Observed in Logs (older version) When TV Recommend Pages are Trying to Load

QueryParser: Invalid field 'sectionID' found, ignoring.
QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.

###Newer Server Version: 1.25.9.5721-965587f64

Player (Web): 4.78.4 (though this also happens on iOS or ShieldTVs)

Behavior Observed:

  • I can not load my TV recommended page at all. (“Something went wrong”)
  • Also, various shows fail to play completely. (an attempt to play 1883 is in the logs along with the resulting errors)
  • If I downgrade back to the older version above, I can again play the shows like 1883 that fail, and my library recommended pages will load, albeit slowly.

Frequent Errors Observed in Logs on Latest Plex Version While Attempting to Load Recommended TV page:

ERROR - Unknown metadata type: folder

WARN - QueryParser: Invalid field 'sectionID' found, ignoring.

QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.

QueryParser: Invalid field 'contentDirectoryID' found, ignoring.

WARN - [DatabaseFixups] Held transaction for too long (E:\jenkins\server\3589017872\Library\MetadataCollection.cpp:479)

Subscription: Error refreshing sub: Could not find providers for subscription

And then this long error which directly precedes the library recommend page failing to load, as well as when I try to play :

Note that I’ve checked my database and the indexes mentioned do seem to exist.

Apr 11, 2022 16:42:37.475 [12836] ERROR - SQLITE3:0x724432f3, 1, no such index: index_metadata_item_views_on_guid in "select grandparents.id,metadata_item_views.originally_available_at,metadata_item_views.parent_index,metadata_item_views.`index`,max(viewed_at),grandparents.
Apr 11, 2022 16:42:37.478 [12836] ERROR - Soci Exception handled: sqlite3_statement_backend::prepare: no such index: index_metadata_item_views_on_guid for SQL: select grandparents.id,metadata_item_views.originally_available_at,metadata_item_views.parent_index,metadata_item_views.`index`,max(viewed_at),grandparents.library_section_id,grandparentsSettings.extra_data from metadata_item_views indexed by index_metadata_item_views_on_guid join metadata_items as grandparents indexed by index_metadata_items_on_guid on grandparents.guid=grandparent_guid join metadata_item_settings indexed by index_metadata_item_settings_on_account_id on metadata_item_settings.guid=metadata_item_views.guid and metadata_item_views.account_id=metadata_item_settings.account_id join metadata_item_settings as grandparentsSettings indexed by index_metadata_item_settings_on_guid on grandparentsSettings.guid=metadata_item_views.grandparent_guid and metadata_item_views.account_id=grandparentsSettings.account_id where metadata_item_views.library_section_id=? and viewed_at > '2022-02-21 15:42:37' and metadata_item_settings.view_count>0  and metadata_item_views.account_id=? group by grandparents.id order by viewed_at desc

What I’ve tried:

  • Checking database for corruption and repairing it. There was non reported but I ran the repair anyway.
  • Resetting all view customizations, no change
  • Testing with different managed users on my account, these problems seem to be isolated to my user. This feels important but I’m not sure what would be causing this to troubleshoot further.
  • Checked my hardware the library is on for performance. It is a high performance NVME drive showing no signs of failure (all other libraries load quite quickly, just not TV)

Hopefully these details will help troubleshoot what is going on with my library. I’m reasonably proficient with the SQL DB so if I need to manually update something to fix whatever is broken, I can do so.

Help would very much be appreciated. Thank you!

2

Seems similar to my problem (SEE LINK & PICS in Link) but they don’t seem to care
Notice 0 responses to my question below.
Only been a customer since its inception
& turned on hundreds of people to PLEX over the years

3

I’m not sure if it’s the same or not. Can you check your logs to see if you have any of the same error messages I’ve posted above? You can watch the console in plex server settings while attempting to load your libraries that are broken and see what lines come across in yellow or red highlight which will quickly pinpoint the problematic queries.

4

I cant read logs. I deleted the PROGRAM. PMS. with Windows only then reinstalled a FW from over a yr ago. I’ll explain more whdn i’m in front of an actual PC

5

Ok so I read where you can Rollback-update PMS if you have an older FW and I have a few in my Downloads folder on the Server. You are supposed to find the “Updates” Folder in APPDATA etc etc, but I could not find it and don’t know if that is where or IF they even keep them anymore after you do you update. Also, I am on Windows 10, Yours may be different to do so for that, you have to research the Rollback or Downgrade of the FW on these Forums and it had other directions in it but I just copy and pasted my setup in a text file on my Desktop so I could do it that way. Ok so I could not find the Updates folder so I decided I would roll the dice, if you aren’t comfortable doing this, don’t. I am not responsible if you lose or mess anything up, this is my experience only. So I roll the dice figuring if it doesn’t work, I will do the Server from Scratch again.

So 1st STEP> I went to ADD or REMOVE PROGRAMS in the Windows Control Panel & hit uninstall on the PLEX MEDIA SERVER program. DO NOT USE ANY 3rd PARTY UNINSTALLER as that was mentioned NOT TO in the directions. So next I uploaded an update from 2 weeks ago before everything was fine BUT that just gave me the same situation of Blank Libraries with a GREEN LIGHT for Remote Access. So I decide to uninstall it one more the same as the 1st step but this time, go back further. I went back to Feb 2021 FW & clicked on the installer link & ran it & now everything came back like it was apparently so I don’t believe it was a corrupt database, I believe it was a corrupt FW in the current PMS update. I believe 124 is the first 3 numbers in that FW that worked for me. I want to go with a bit newer FW now that I got everything back to running seemingly normal. Don’ know if I am missing any changes of settings yet but is there a way to know if the FW is from the PUBLIC or BETA options by looking at the FW link itself? At some point in 2021 I decided to try the BETA builds and have since and THAT is why I decided to go so far back, because I want a PUBLIC build for sure now. So if there is a way to tell, I want the best Public Build of anything BEFORE we had this Streaming stuff of recent. I really plan on just never updating it again. I hit skip earlier to get rid of the FW notice on the Server. Now I’m gonna go watch a Barney Miller & go to bed. Good luck anyone who needs a fix and if I can be of any other help or you have any questions, just ask and I will respond asap. I think I was clear on what I did but fire away if I confused anyone. Goodluck all

6

Replying to my original post here in the hopes that someone from Plex can help troubleshoot. Thank you.

7

This error persists in the newest version installed today and now causes my Plex to crash regularly. Could someone from Plex please review & reply to this?

May 17, 2022 08:22:48.603 [17712] ERROR - Thread: Uncaught exception running async task which was spawned by thread 17276: sqlite3_statement_backend::prepare: no such index: index_metadata_item_views_on_guid for SQL: select grandparents.id,metadata_item_views.originally_available_at,metadata_item_views.parent_index,metadata_item_views.index,max(viewed_at),grandparents.library_section_id,grandparentsSettings.extra_data from metadata_item_views indexed by index_metadata_item_views_on_guid join metadata_items as grandparents indexed by index_metadata_items_on_guid on grandparents.guid=grandparent_guid join metadata_item_settings indexed by index_metadata_item_settings_on_account_id on metadata_item_settings.guid=metadata_item_views.guid and metadata_item_views.account_id=metadata_item_settings.account_id join metadata_item_settings as grandparentsSettings indexed by index_metadata_item_settings_on_guid on grandparentsSettings.guid=metadata_item_views.grandparent_guid and metadata_item_views.account_id=grandparentsSettings.account_id where metadata_item_views.library_section_id=? and viewed_at > '2022-03-29 08:22:48' and metadata_item_settings.view_count>0 and metadata_item_views.account_id=? group by grandparents.id order by viewed_at desc

8

I don’t know if it’s related to this problem, but I can no longer click on the Recently Added in TV Shows tab.

Error message:
“We’re having trouble finding this page. It might have been deleted”

Only error I can find in the console is:
“QueryParser: Invalid field ‘sectionID’ found, ignoring.”

Also, all newly added episodes now will have “1900-01-01” in the Originally Available date field…

Version 1.26.2.5797

9

@myrison @Turfking8 You guys are dealing with broken databases see Repair a Corrupted Database | Plex Support

@skyesete betting you have prefer local metadata enabled, with invalid date format for your 1900 date error. For the others try optimizing your database and check the link above to see if you have database corruption. Worst case, start a new thread for your issue and post your server logs.

10

Thanks for the reply @dbirch . I already checked for corruption and didn’t find any, but did the repair anyway, to no effect. Any other ideas ?

What I’ve tried:

  • Checking database for corruption and repairing it. There was none reported but I ran the repair anyway.
11

Did you optimize the database? and can you provide full server logs?

12

Hi @dbirch, sorry for the very slow reply. I’d decided just to stay on the old version to see if at some point I was able to migrate. I tried the latest version a couple of days ago and I’m back to my recommended page in TV shows not loading.

Full logs are included here from a fresh startup and navigating to the recommended TV page where things break down. The error messages are the same as in my original post.

I’ve tried a DB repair, a DB optimize, both without luck. Thank you for any help you can provide.

Logs attached here.

Plex Media Server Logs_2022-07-31_14-00-19.zip (3.7 MB)

This is the error message:

Got exception from request handler: sqlite3_statement_backend::prepare: no such index: index_metadata_item_views_on_guid for SQL: select grandparents.id,metadata_item_views.originally_available_at,metadata_item_views.parent_index,metadata_item_views.index,max(viewed_at),grandparents.library_section_id,grandparentsSettings.extra_data from metadata_item_views indexed by index_metadata_item_views_on_guid join metadata_items as grandparents indexed by index_metadata_items_on_guid on grandparents.guid=grandparent_guid join metadata_item_settings indexed by index_metadata_item_settings_on_account_id on metadata_item_settings.guid=metadata_item_views.guid and metadata_item_views.account_id=metadata_item_settings.account_id join metadata_item_settings as grandparentsSettings indexed by index_metadata_item_settings_on_guid on grandparentsSettings.guid=metadata_item_views.grandparent_guid and metadata_item_views.account_id=grandparentsSettings.account_id where metadata_item_views.library_section_id=? and viewed_at > 1655064173 and metadata_item_settings.view_count>0 and metadata_item_views.account_id=? group by grandparents.id order by viewed_at desc

13

Well, after digging in again on this problem, I may have progress to report. I manually opened the database using “DB Browser for SQLite” in Windows and deleted and created the missing index. Once I did this, the error message changed to another “no such index” error. When I closed Plex again and checked for the index, it was already there, so I deleted it and recreated it as well. After doing this for 3 different indices, my TV recommendations page loaded successfully for the first time in May when on the current version of Plex. I’m going to leave this thread open for a bit longer to make sure the problem is really fixed. After that I’ll mark this as the solution if it continues to work.

14

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.