DVR Browse(source) returns sqlite3 error

Plex Media Server
,
1

Server Version#: 1.41.8.9834-071366d65 (ubuntu 24.04)
Player Version#: N/A

When clicking on Live TV/Browse (source), I get the error “Something went wrong”. The XX database appears to be corrupt. Any search for items in the upcoming schedule are not returned, but the schedule for previously defined upcoming recordings is correct. I backed up the database, deleted it and restarted plexmediaserver and it recreated the file. The SQLite error is

Jun 11, 2025 09:21:59.000 [128177006136120] 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 where (metadata_items.title = ‘Petrified Forest’ or metadata_items.title_sort = ‘Petrified Forest’ or metadata_items.original_title = ‘Petrified Forest’) and metadata_items.library_section_id in (1) and metadata_items.metadata_type=1 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 limit 101 offset 0

The data in the upcoming schedule is still via a direct link, e.g. http://HOST:32400/web/index.html#!/server/SERVERID/provider/tv.plex.providers.epg.cloud:12/details?key=%2Ftv.plex.providers.epg.cloud%3A12%2Fmetadata%2Fplex%253A%252F%252Fmovie%252F6684101d7819b5b8f06f0ba3

I recently upgraded to this version of plex, so it might be a bug in the latest version.

2 Likes
2

The XX database refers to the tv.plex.providers.epg.cloud database file in ‘Plex Media Server/Plugin Support/Database’.

3

I’m getting this exact same error as well after patching to the new server version.

[Req#1f71] SQLITE3:0x7ff7cbba7300, 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”

4

Here is a script that will allow you query the upcoming DVR schedule and show only newly listed shows/movies with a link to record them. It will work, despite the existing SQL issue (which is a query where the field name does NOT exist in a table.) If you find it useful (or not), please comment with your experience.
plex_distribute.gz (2.0 KB)

5

Same here, error below.
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

6

having the same issue as well.

7

Same here on Server version Version 1.41.8.9834 on Synology NAS running DSM 7.2.2…

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”

and 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

8

Same issue here, Hopefully there’s a new build coming soon

9

Downgrading works for me.

1 Like
10

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