I ran into this problem recently after moving Plex from one server to another. I found that it was happening on accounts that had content restrictions. I fixed it by removing and re-adding the content restrictions. Hope this helps.
That was fixed today in a hot fix beta release 1.11.1.4768
I also am now having this same problem since the last update. I have optimized my database (many times), cleaned bundles, and emptied trash but still can not get the dashboard to come up.
Constant database corruptions and lack of solutions from Plex.
Everyone is well aware that Plex are right now focused on getting Plex onto as many devices, operating systems and streaming boxes as possible which is a good thing. And they have added some useful features recently.
But they blatantly ignore core issues that are always there and need to be addressed, such as:
The never ending database corruption issue; why does this happen ALL THE TIME!
The fact that repairing the database is way more complicated then it needs to be and should be an automated process, just like ârepair databaseâ
When you click on repair database it seems to either fail or do nothing, where is the feedback in status about what its doing? is the database corrupt or isnât it? Is it repairing?
I could go on but I wonât cause what I say will just be lost in the ether anywayâŠ
Uninstall everything Plex related and head on over to Emby.
Its come on leaps and bounds recently and their support is superb.
Plex Support dont give a toss - all they care about is attracting as many new paying subscribers as possible and not giving a â â â â about existing subscribers or all those free loaders that dont subscribe.
Hello. I just did a fresh install on Windows 10. And the first welcome message I receive is this âThere was an unexpected error loading the dashboardâ.
I donât even know how to start looking for a fix. Found this thread but this one seems to be focused on people who got Plex up and running and later faced this issue. I have just installed it. I also read something about looking at the LOGs. I found them, but there are too many and I dont really know what is the problem. There are lots of error messages all over them.