Live TV Searching Error with Latest PMS version

Server Version#: 1.41.8.9834 (server-windows)

After updating to Master version 1.41.8.9834 (server-windows) I get the following error in the logs when searching. The client displays “Some Search requests timed out.”
DB optimisation has been run. Reverting to previous Beta version 1.41.7.9823 resolves the issue.

Jun 11, 2025 12:23:50.871 [25236] 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 = 'Ghostbusters' or metadata_items.title_sort = 'Ghostbusters' or metadata_items.original_title = 'Ghostbusters') 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

Wondering if it’s a known issue in this version or a problem with my DB?

1 Like

Narrowed the problem down to something to do with Live TV DVR search results. Clicking on ‘Live TV & DVR’ > ‘Browse’ in the web client displays the error: “Something went wrong - An unexpected error occurred.” and a similar error in the logs with ‘no such column: media_items.begins_at’

Jun 19, 2025 12:15:45.780 [86464] ERROR - [Req#17f6f5] SQLITE3:(nil), 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 19, 2025 12:15:45.784 [86464] 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

Known issue. I rolled back to the previous version.

Have a look here.

Phil

Thanks - looks like it’s now fixed in current beta version 1.42.0.9975.

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