[BUG] Photos > SQLITE3:0x80000001, 28, double-quoted string literal: "2021-05-17 19:36:06"

Server Version#: 1.23.1.4528
Player Version#: 4.56.4 (app.plex.tv)

It seams like opening photos or videos (library type: Photo) in the latest PMS is broken in some way. Everything returns the following in the Settings > Console, when opening/clicking a photo or video.

Playback Error
An error occurred loading items to play.
SQLITE3:0x80000001, 28, double-quoted string literal: "2021-05-17 17:00:00"

May I have the ZIP log files where you found this please?

The errors are visible in my PlexWeb console (under settings). Also logged in the PMS logs. This worked without problems before the current PMS release.

Stopped PMS. Deleted all logs. Enabled DEBUG logging (not verbose). Waited 1 minute. Logs attached:

May 17, 2021 22:17:59.321 [0x7fa301abbb38] ERROR - SQLITE3:0x80000001, 28, double-quoted string literal: “2021-05-17 20:17:59”

Plex Media Server Logs_2021-05-17_22-18-22.zip (26.8 KB)

Thank you for the logs.

This shows perfectly what I need to write up and submit to Engineering to investigate further.

Thanks @ChuckPa

Followup question?

Other than the log errors, Are you seeing other impact : Displayed information changed / missing ?

I also present the same error in the log, and the impact that I am getting is that sometimes it takes time to load the libraries, I also present errors on occasions, and some things are not shown. that only happened to me after updating to version 1.23.1.4528-c0513eb4c

@prime20

I will need to see your DEBUG logs ZIP file so I can follow along what PMS is doing at the time the errors are reported.

I’ve just noticed, that these errors only occur in the Timeline view. Which I always use. It doesn’t look like anything else has changed. Media information, tagging and ordering is correct.

EDIT: It looks like the .plexignore bug has returned. I previously reported a bug on this. The exact same happens again.

I can repro this. getting the exact same issues. I haven’t upgraded my Plex Server version in a while, so I am still on 1.21.4.4079, using the x64 RPM version on a bare metal installation. Now I decided to move from one hw to another, stopped the Plex server on the old machine and tried to move the complete /var/lib/plexmediaserver folder to the new server. Then I mounted the old config folder within the container’s /config folder and it all went super well, my Plex server was up and running.

But this container trickery made my version to be upgraded to 1.22.3.4523-d0ce30438. The first thing I noticed is that if I did a rescan on any media folder (videos or tv shows type), it reran the media scanning on every single item. I thought this might be to collect more metadata for the smart playlists feature added to plex lately. However after the rescan my whole db structure is broken apparently, many keys are conflicting or not even existing.

Then I rolled back to the old backup and instead of hitting rescan I tried running optimize database. Since then I see issues like this in the log:

log

Whenever I try to play something for instance. The playback is also super slow and often doesn’t start at all. If you tell me what kind of command outputs you are interested in, I can provide any.

I’m getting the same error as of a short while ago - Everything worked fine last night before i went to bed around 10pm. Upgraded to PMS 1.23.1.4571 around 7am or so this morning and I’ve had issues playing pretty much any video file. Seemingly, nothing will play. I’ve tested using about half a dozen video files and tried from different views as well (home page, drilling to the TV show, Season. Nothing works).

I restored the database off a backup from a couple of days ago and everything seems to be working now. The only side effect now seemingly is that my “watch” data is a couple of days old - otherwise it seems to be all good

Platform is a WD My Cloud PR4100

I also have observed this issue but rolled back to the :latest image. This roll back took place before 1.23.1.4571 became available to everyone.

I am seeing this as well but I don’t know of a direct impact it is having on using. But concerning never the less.

It seems to happen when I click on any of the top level home menu items on the left nav bar.

Server Version: 1.23.1.4571
OS: Big Sur 11.3.1
Plex Web App Version: 4.57.4

Upgraded to docker [1.23.1.4602-280ab6053]; it ran fine for about 5 days, then when i was replacing some files inside a tv show and hit rescan, i saw the same error again.

Aside from the error, the only real symptom was on the Roku TV, where I simply tried to view the season from which I had replaced the files, and it actually timed out with an error. Something to the effect of “Failed to load.”

I have downgraded to [1.22.3.4523-d0ce30438] and the same season is now working properly.

Same issue with me, only after updating to Plex Pass version: 1.23.2.4600. Host uses Docker.

This SQLITE double-quoted string literal error message is not actually causing any issues (it should actually just be a warning message).

If you have problems, it’s not related to this log line.

This has been fixed in the next release though so this error message will go away.

1 Like

Could seeing this error in the logs potentially cause the same media to reprocess over and over again?

Ehhhmmm, so what about the problem itself, that we can’t view any new photos (at all) ?

Sounds like it is only the logging type (error to warn), that is changed in the next release?

Just updated server to 1.23.2.4625-6000 and am still having this error not being able to view photos.

The following are the related log lines that show up with the error. Definitely hitting a 500 error with Exception handled: std::bad_cast.

Jun 01, 2021 22:28:11.836 [0x7f2dec763b38] Debug — Request: [192.168.86.25:55592 (Subnet)] POST /playQueues?type=photo&uri=server%3A%2F%2F<redact>%2Fcom.plexapp.plugins.library%2Flibrary%2Fmetadata%2F20202%2Fchildren&key=%2Flibrary%2Fmetadata%2F20203&repeat=0&own=1&includeChapters=1&includeMarkers=1&includeGeolocation=1&includeExternalMedia=1 (9 live) TLS GZIP Signed-in Token (johnbart)
Jun 01, 2021 22:28:11.837 [0x7f2dec763b38] Debug — PlayQueue: Converted 'server://<redact>/com.plexapp.plugins.library/library/metadata/20202/children' to 'library://x/directory/%2Flibrary%2Fmetadata%2F20202%2Fchildren'
Jun 01, 2021 22:28:11.838 [0x7f2dec763b38] Debug — PlayQueue: 0 generated IDs compressed down to a 20 byte blob.
Jun 01, 2021 22:28:11.848 [0x7f2dec763b38] Debug — PlayQueue: Start index: 0 End index: 99 Count: 257
Jun 01, 2021 22:28:11.849 [0x7f2dec763b38] Debug — PlayQueue: 257 generated IDs compressed down to a 439 byte blob.
Jun 01, 2021 22:28:11.852 [0x7f2dec763b38] Debug — PlayQueue: Added 100 items in 0.0 sec.
Jun 01, 2021 22:28:11.881 [0x7f2dec763b38] Error — Exception handled: std::bad_cast
Jun 01, 2021 22:28:11.882 [0x7f2deddd2b38] Debug — Completed: [192.168.86.25:55592] 500 POST /playQueues?type=photo&uri=server%3A%2F%2F<redact>%2Fcom.plexapp.plugins.library%2Flibrary%2Fmetadata%2F20202%2Fchildren&key=%2Flibrary%2Fmetadata%2F20203&repeat=0&own=1&includeChapters=1&includeMarkers=1&includeGeolocation=1&includeExternalMedia=1 (9 live) TLS GZIP 45ms 530 bytes (pipelined: 3)

I’m fighting with this issue as well - I try to open a pic, and I get:

ERROR - Exception handled: std::bad_cast

Nothing else, but it’s consistent, obnoxious, and annoying. Happens in browsers, TV media players, mobile devices. Persists after at least 4 updates.