“unexpected error has occurred” error message when using customer filter to select audio language for TV Shows

Server Version#: 1.15.4.919
Player Version#: 3.95.1

Hello,
I got an error message on Plex Web when I am in a TV shows library named “Séries TV” and try to do a customer filter for searching specific audio language

In the log we find that :

Apr 22, 2019 20:56:42.944 [16188] DEBUG - Setting container serialization range to [0, 49] (total=-1)
Apr 22, 2019 20:56:42.944 [16188] ERROR - SQLITE3:0xb8f01689, 1, no such column: grandchildren.id in "select count(*) from (select distinct(metadata_items.id) from metadata_items  where metadata_items.library_section_id in (4) and (metadata_items.metadata_type=2 and (select
Apr 22, 2019 20:56:42.960 [16188] ERROR - Soci Exception handled: sqlite3_statement_backend::prepare: no such column: grandchildren.id for SQL: select count(*) from (select distinct(metadata_items.id) from metadata_items  where metadata_items.library_section_id in (4) and (metadata_items.metadata_type=2 and (select count (*) as cnt from media_streams join media_items on media_items.id=media_streams.media_item_id where media_streams.language='eng' and media_streams.stream_type_id=3 and media_items.metadata_item_id=grandchildren.id) > 0) )
Apr 22, 2019 20:56:42.960 [6004] DEBUG - Completed: [127.0.0.1:64300] 500 GET /library/sections/4/all?type=2&episode.subtitleLanguage=eng&includeCollections=1 (10 live) TLS GZIP Page 0-49 7ms 484 bytes (pipelined: 6)

All other custom search is ok except audio language and subtile language.

I don’t have the issue in my Movies Library.

Could someone try on your side ?

Here the error.

I tried to repair the DB following the support page but no luck.
I also tried to install a new server and only adding 1 file but no luck.

Best Regards.

I have the same problem and error screen. It worked in the past.
Server Version 1.15.4.993

Confirmed the error. I have filed a bug report.

Workaround:
if you set the library view mode to ‘Seasons’ or ‘Episodes’, the filter is working.

I have the same error, it looks like this bug is still outstanding? I can confirm workaround does work.

Looks like it will be fixed in server version 1.16.3

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