Running 1.41.8.9834 on a Mac-Mini. In the LiveTV tab, Guide, What’s On and DVR Schedule all work as expected. Browse reports that “Something Went Wrong/An Unexpected Error Occurred.” This error shows up both in MacOS app and in a web browser. On an iPad, the iOS app no longer shows a browse option for the LiveTV option.
8 Likes
Same issue. Notably, I can browse the guide, but when I search for a program I KNOW is in the guide, it won’t show up in search, either—on top of this issue where I get “something went wrong” went clicking the browse tab.
1 Like
Here’s some additional information:
Plex Server Version 1.41.8.9834
Affects all clients (iOS, Roku, web)
Here’s my log entry:
Jun 08, 2025 11:34:04.797 [23344350374712] Debug — [Req#19445] Setting container serialization range to [0, 49] (total=-1)
Jun 08, 2025 11:34:04.995 [23344350374712] Error — [Req#19445] SQLITE3:0x80000001, 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"
Jun 08, 2025 11:34:04.996 [23344350374712] Error — 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
1 Like
Looks to be an issue in this SQL query:
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
Running it stand-alone produces the same error.
Seems like an updated database architecture is the cause of this breaking change. Would really appreciate an update from the Plex team on this.
This bug was released to the public channel. Plex??
1 Like
Same issue here, same server version, same error in the logs.
Plex staff, any update here? Is this being addressed .. ?
I upgraded PMS running on Synology to 1.41.8.9834-60009834 yesterday (stable channel) and started experiencing this same issue. Namely:
- “Live TV → Browse” fails with “Something went wrong. An unexpected error occurred.”
- Coincident with that, two similar error messages show up on the console:
[Req#93d04] SQLITE3:0x80000001, 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
I also experienced the same problem and am able to address it with a custom db query script. Details about that in different post, DVR Browse(source) returns sqlite3 error - #3 by gadz00ks.
Has anybody tried rolling back the version of plex media server and does that fix it?
I restored my C Drive image using a Macrium backup to the day before the Plex server update and it fixed this issue. I was also able to update the EPG no problem. I have since re -installed the server update and the problem is back. Just waiting for either a fix, or a new server update.
Just to add, same error.
Plex, can we have an indication that you’ve acknowledged this bug.
I can recreate using the web app, but
I cannot recreate using the mobile app.
Did you perhaps downgrade to the legacy mobile app?
Happy user, great service. Thanks. (working again 8/9/25 after server update: Plex for Windows ver. Version 1.109.0.329-ea562b95)
Same issue with “Browse”, web connection to server. PlexMediaServer-1.41.8.9834-071366d65-x86_64.exe
Good option is use What’s On (https://app.plex.tv/desktop/#!/live-tv/214da3ba744a607871ef8739b7f397031574c201/tv.plex.providers.epg.cloud:11?pivotID=dvr.whatson), view Movies on Later or TV on Later.
Broken web address (https://app.plex.tv/desktop/#!/live-tv/214da3ba744a607871ef8739b7f397031574c201/tv.plex.providers.epg.cloud:11?pivotID=dvr.browse)
1 Like
I’m also having the same issue with “Browse” feature for Live TV on my Synology NAS after upgrading to 1.41.8.9834. I hope the Plex team can get this issue resolved quickly. I use this feature every few days to schedule recordings.
Oh.. forgot to add, I’m seeing this both in the web app (both Windows and Mac) and also in the mobile iOS app too.
1 Like
That fact that a paid product with no tech support other than forums can have a breaking change get pushed and then go without a response for over two weeks is pretty wild, is it normally like this?
3 Likes
I run two servers and the HP with ryzen machine has this problem but the Dell with Intel is working properly. I returned to the previous release to fix the HP with ryzen.
I also reported error at that thread. Here’s my error:
Server version: 1.41.8.9834
Docker container: Linuxserver.io version:- 1.41.8.9834-071366d65-ls269 Build-date:- 2025-06-10T17:38:48+00:00
ERROR - 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
On my Mac-mini, I rolled back to version 1.41.7.9823, which was the last stable version before this problem appeared. With that, I can search upcoming shows and use the browse option. I’m not going to install any more releases, beta or public, until this problem is fixed.
