Browse in LiveTV Tab reports error

I downgraded my Synology to 1.41.7.9823.
Works for me atm.

Error in 1.41.8.9834: (Windows 11)

[Req#844b1] SQLITE3:0x7ff6a8297300, 1, no such column: media_items.begins_at in “select metadata_items.id from metadata_items join metadata_items as parents on parents.id=metadata_items.parent_id join metadata_items as grandparents on grandparents.id=parents.parent_id where metadata_items.library_section_id in (2) and metadata_items.metadata_type=4 order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc”

Got exception from request handler: sqlite3_statement_backend::prepare: no such column: media_items.begins_at for SQL: select metadata_items.id from metadata_items join metadata_items as parents on parents.id=metadata_items.parent_id join metadata_items as grandparents on grandparents.id=parents.parent_id where metadata_items.library_section_id in (2) and metadata_items.metadata_type=4 order by media_items.begins_at asc, metadata_items.id asc, media_items.width desc, metadata_items.originally_available_at asc, media_parts.id asc

Experiencing the same issue, running Plex Server 1.41.8.9834 on Windows 11.

Same issue mentioned with unable to search for items i can see in the guide while using web app or android app. Also attempting to add new recording shows error but does show up in the priority list but with no future episodes

same poblem here…

Same problem here running my server on Windows 11 and I can produce the error on the Windows app and in both Edge and Chrome browsers.

Also Synology v1.41.7.9823
with Android App 2025.18.0

has Bugs..
[Req#18a238] Invalid library metadata ID plex: passed.

But I’ve just seen 2025.19.0 ist already on the way..
https://l.plex.tv/mbrn

Edith: 2025.19.0 did Not fix Android app

Same issue here on Windows 11. Is there a way to roll-back to previous version? I coincidentally just swapped my server to another machine and deleted it from my previous machine. I do not have old .exe’s. I’ve heard reinstalling an old version could be a temporary fix.

Same problem here on Debian Linux. Anyone have the download path for the previous version?

1 Like

Same issue. Debian Linux.

Browse page doesn’t load, Live TV search doesn’t work, recordings stopped working.

If you think about it, the browse tab is actually gone from the interface in the new Plex Experience on Android. I just noticed this. And I haven’t upgraded to the latest public PMS yet (still on the previous public) so it’s not something with that either. So maybe it is intentional.

It seems a bit strange that they would remove it though. @McWanke could you maybe clarify?

1 Like

I pulled open the Plex DB in HeidiSQL, took a look at the media_items table, and there is indeed a begins_at column.

Executing select media_items.begins_at from media_items yields rows, but they’re all NULL

The problem appears to be with the query itself. If I copy the query from the logs:

select metadata_items.id from metadata_items   
join metadata_items as parents on parents.id=metadata_items.parent_id  
join metadata_items as grandparents on grandparents.id=parents.parent_id  
where metadata_items.library_section_id in (2) and metadata_items.metadata_type=4  
order by  media_items.begins_at asc, 
  metadata_items.id asc, 
  media_items.width desc, 
  metadata_items.originally_available_at asc, 
  media_parts.id asc

And execute it, I get the same “column not found”, and I think it’s because we’re not touching the media_items table in the SELECT part of the query. So either the query is missing a JOIN to the media_items table, or the ORDER BY includes items it shouldn’t.

Sadly, this means we can’t simply “fix” or workaround the issue as users; they need to modify the query that their code calls.

2 Likes

On the plus side, that suggests that our DBs are intact. I.e. it’s not a corrupt DB, failed migration, or similar, but rather just a programming error in the construction of the SQL query.

It should be a simple fix. I sure wish they’d fix it!

2 Likes

There seem to be two separate problems. One is that server versions after 1.41.7.9823 have broken the browse function. Reverting to 1.41.7.9823 on a mac-mini resolved the problem for me when I use a web browser and, at least for the time being, the Plex for Mac app which is currently at 1.109.0.329-ea562b95. I also found that reverting to the standard Roku app rather than the Preview app still has the previous functionality. The new “plex experience” in both the Roku app and the iOS and iPad apps no longer provides a browse function, so I can no longer use those to schedule recordings.

At least for me, the whole reason for Plex DVR is to be able schedule and record TV programs. These changes are making it almost impossible to do that.

1 Like

I’ve had this error on all versions of Plex DVR server, Windows, Mac, and TrueNAS versions(have not tried Linux)
All versions of client software i have access to, Windows, Android, ShieldTV, Xbox, Web.
Going on for a little more than a month. Just havent raised a stink because what is good on TV any more that i dont already have scheduled.

I have tried imaging up a new device and installing a fresh Plex DVR server install, same issue
I can view the guide and whats on, but the guide tab that lets me browse by name just errors out with ‘something went wrong, an unexpected error occurred’

A work around for movies is to go to the ‘whats on’ tab and scroll down to ‘movies on later’. There are too many shows for this to be a functional option unless you look up when the show is going to be on, and then waiting for its first airing to schedule its recording.

Also of note, the search function no longer shows EPG listings, at least on the devices and server’s i’ve tried.

1 Like

I wish Plex would take this seriously

1 Like

same problem, agree wish they would at least acknowledge this and indicate they are working to resolve the issue. same problem on web and iOS

1 Like

I absolutely cannot believe that there has been no response to this. It appears to be a universal problem with the current release, and should be an easy fix: namely, just the addition of a SQL join to a poorly-written query. But the fact that the query got pushed to the public release in this state – and that no one from Plex has responded so far – strongly suggests something rotten in Denmark.

Since @sa2000 is retired, hardly anyone feels responsible for DVR anymore.
:frowning:

1 Like

This is my experience to.

Can’t use iPad app as DVR functionality missing.
Can’t use web browser as broken.
Can’t search for live tv content as broken on both.

Plex staff, you must really hate us.

3 Likes

@taborj You might get more traction with plex support if you started a new post with this information. Maybe put something in the title about the errors your seeing. They’ll want to see your logs. Full logs.