Upgraded to 1.8.0.4109 - Now "There was an unexpected error loading the dashboard"

I upgraded to version 1.8.0.4109 this morning and now none of my videos will play, and I get the following message on my dashboard, “There was an unexpected error loading the dashboard”. When I attempt to play a video, I get a popup with the message, “sorry there was a problem playing this item”. My Plex server is completely dead. Nothing will play. Please help!

I searched for the error, and tried a registry fix that worked for some, but it doesn’t work for me. I also added a “2” folder to my temp folder to see if that would help.

As an FYI, my server is a re-purposed desktop with Windows 10 64-bit, 16 Gig’s of RAM, and an Intel i5 processor. It’s been working great for the past year. It only stopped working when I updated to the new version this morning.

Grab the server logs and post them here for review. Get all of the server logs (might be up to 5 of them), zip them up, and attach to your next post.

Also, are you running a Windows 10 Insider build?

Thanks kegobeer. I attached my server logs. Should I also include my database? Oh… and I’m using Windows 10 Home Edition. Nothing fancy.

@SmithPlex said:
Thanks kegobeer. I attached my server logs. Should I also include my database? Oh… and I’m using Windows 10 Home Edition. Nothing fancy.

Looks like a database issue. Not seen it before. It is either database corruption or a bug. I will discuss with the development team
SQLITE3:FC23ACA3, 1, no such column: tags.parent_id

May be problem with the database schema migration. What version did you update from?

Would you have any old logs ? or logs for first launch of 1.8.0.4109?

@SmithPlex said:
Thanks kegobeer. I attached my server logs. Should I also include my database? Oh… and I’m using Windows 10 Home Edition. Nothing fancy.

could you get a zipped copy of the database sent to me by private message please
if it is too big, please upload on dropbox or other service and send me a link

I still need to know what version you updated from

I have the same issue. Upgraded to 1.8.0.4109 this morning from 1.7 and now my dashboard won’t load.

edit: I’m running Plex on Ubuntu 16.04.

@ahenriksen said:
I have the same issue. Upgraded to 1.8.0.4109 this morning from 1.7 and now my dashboard won’t load.

edit: I’m running Plex on Ubuntu 16.04.

1.7.?
There were several 1.7.x releases

@sa2000 said:
1.7.?
There were several 1.7.x releases

Sorry… 1.7.5.4035.

@ahenriksen said:

@sa2000 said:
1.7.?
There were several 1.7.x releases

Sorry… 1.7.5.4035.

Thanks - would like logs please and zip of the database sent to me by private message

If you have logs for the first launch of version 1.8.0!that would be helpful

@sa2000 said:
Thanks - would like logs please and zip of the database sent to me by private message

If you have logs for the first launch of version 1.8.0!that would be helpful

Sent you the entire Logs folder and database.

@ahenriksen said:
I have the same issue. Upgraded to 1.8.0.4109 this morning from 1.7 and now my dashboard won’t load.

edit: I’m running Plex on Ubuntu 16.04.

Your problem is not the same - where did you see this error SQLITE3:FC23ACA3, 1, no such column: tags.parent_id

You appear to have issues with logs being rotated before reaching 5Mb and missing log entries and potential corrupt database - looks like to do with disk issues - either disk failures or you have run out space

Aug 02, 2017 12:35:43.493 [0x7ff5cdffe700] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database or disk is full

Could you check diskspace on
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/
And also see if there were any disk errors

Your previous version was 1.7.6.4058-8fa494d15 and not 1.7.5.4035

You were running on 1.7.6 before 2nd August 06:41am

The launch of 1.8.0 appears to have been at about 06:41 am on 2nd August. Don’t have Plex Media Server log files for that time.

There was an issue in that when the update to 1.8.0 happened some plex media server processes did not get shutdown - specifically Plex Tuner Service 1.7.6 process appears to having a process running whilst the 1.8.0 upgrade happened.

Wow you are very thorough. It appears that I have run out of disk space for that directory tree. I will get it corrected and should be good to go. Thank you very much for your help!! I sincerely appreciate it.

Adam

I’ve just updated to server version 1.8.0.4109 through the LinuxServer.io container. I am also seeing SQL errors in my logs. An example snippet is below

Aug 02, 2017 20:22:04.686 [0x7f6aff3fe700] ERROR - SQLITE3:0x10, 1, no such column: tags.parent_id
Aug 02, 2017 20:22:04.687 [0x7f6aff3fe700] ERROR - Uncaught exception running threadpool task: sqlite3_statement_backend::prepare: no such column: tags.parent_id for SQL: select tags.id as 'tags_id', tags.parent_id as 'tags_parent_id', tags.metadata_item_id as 'tags_metadata_item_id', tags.tag as 'tags_tag', tags.tag_type as 'tags_tag_type', tags.tag_value as 'tags_tag_value', tags.user_thumb_url as 'tags_user_thumb_url', tags.user_art_url as 'tags_user_art_url', tags.user_music_url as 'tags_user_music_url', tags.created_at as 'tags_created_at', tags.updated_at as 'tags_updated_at', tags.extra_data as 'tags_extra_data',taggings.id as 'taggings_id', taggings.metadata_item_id as 'taggings_metadata_item_id', taggings.tag_id as 'taggings_tag_id', taggings.'index' as 'taggings_index', taggings.text as 'taggings_text', taggings.time_offset as 'taggings_time_offset', taggings.end_time_offset as 'taggings_end_time_offset', taggings.thumb_url as 'taggings_thumb_url', taggings.created_at as 'taggings_created_at', taggings.extra_data as 'taggings_extra_data' from tags   join taggings on taggings.tag_id=tags.id   join metadata_items as items on taggings.metadata_item_id=items.id  where taggings.metadata_item_id=? and  (case when tags.tag_type=? and (taggings.`index`<1000 or taggings.`index`>?) then 0 else 1 end)  order by tags.tag_type,taggings.`index`

I am unable to load dashboard, or play any media item from my library. I also have ~ 200 GB of disk space left, so running out of room for transcoding / DB / Logs is not an issue.

A 2nd restart of my application container seems to have solved the issue.

@jmlw said:
I’ve just updated to server version 1.8.0.4109 through the LinuxServer.io container. I am also seeing SQL errors in my logs. An example snippet is below

Aug 02, 2017 20:22:04.686 [0x7f6aff3fe700] ERROR - SQLITE3:0x10, 1, no such column: tags.parent_id
Aug 02, 2017 20:22:04.687 [0x7f6aff3fe700] ERROR - Uncaught exception running threadpool task: sqlite3_statement_backend::prepare: no such column: tags.parent_id for SQL: select tags.id as 'tags_id', tags.parent_id as 'tags_parent_id', tags.metadata_item_id as 'tags_metadata_item_id', tags.tag as 'tags_tag', tags.tag_type as 'tags_tag_type', tags.tag_value as 'tags_tag_value', tags.user_thumb_url as 'tags_user_thumb_url', tags.user_art_url as 'tags_user_art_url', tags.user_music_url as 'tags_user_music_url', tags.created_at as 'tags_created_at', tags.updated_at as 'tags_updated_at', tags.extra_data as 'tags_extra_data',taggings.id as 'taggings_id', taggings.metadata_item_id as 'taggings_metadata_item_id', taggings.tag_id as 'taggings_tag_id', taggings.'index' as 'taggings_index', taggings.text as 'taggings_text', taggings.time_offset as 'taggings_time_offset', taggings.end_time_offset as 'taggings_end_time_offset', taggings.thumb_url as 'taggings_thumb_url', taggings.created_at as 'taggings_created_at', taggings.extra_data as 'taggings_extra_data' from tags   join taggings on taggings.tag_id=tags.id   join metadata_items as items on taggings.metadata_item_id=items.id  where taggings.metadata_item_id=? and  (case when tags.tag_type=? and (taggings.`index`<1000 or taggings.`index`>?) then 0 else 1 end)  order by tags.tag_type,taggings.`index`

I am unable to load dashboard, or play any media item from my library.

I have now seen 3 of these. Please let me know what version you upgraded to 1.8.0 from and if there was an issue on first launch

Do you still have logs of first launch of Plex Media Server version 1.8.0?

Please send me zip of the database by PM and all logs that you have.
I will look at it tomorrow morning

@jmlw said:
A 2nd restart of my application container seems to have solved the issue.

may be an error during database migration. If you have logs for first launch and subsequent launch that would be good to see. full logs please

I just pm’d you the database. I don’t have any additional logs and upgraded from whatever the prior version was.

@SmithPlex said:
I just pm’d you the database. I don’t have any additional logs and upgraded from whatever the prior version was.

no attachment in message - if you used mail interface then that would drop attachments

and presumably in your case a restart does not resolve the problem

@sa2000 I do have debug logging enabled however with rotation at 5MB, and only 5 rotated stored, I only have since some time yesterday. Also because I pull the latest docker image available about every couple weeks, I’m not sure what previous version I was running but it was most likely one of the 1.7.5 or 1.7.6 releases. I will upload an archive and PM you the link of what I have though.