These errors in the server logs all of a sudden started happening and the dashboard will mostly never start. Nothing has changed with the server except an IP issue that has long been corrected which should have no affect on the SQL DB or server
Do you use Anti Virus software?
If so, create an exemption in its preferences so it doesn’t interfere in the Plex data folder.
Get back into your Dashboard, if you can or edit the Preferences.xml file directly with PMS stopped.
The “AllowedNetworks” you specified has invalid network definitions and/or characters in it
ul 03, 2017 09:35:58.851 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:58.861 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:58.871 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:58.881 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:58.893 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:59.077 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:59.140 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
Jul 03, 2017 09:35:59.273 [6596] ERROR - Error parsing allowedNetworks '': An invalid argument was supplied
It’s driving everything else nuts because it’s impacting all networking (internal and external).
As to your database itself, It does look damaged.
If you can drill down into and repair the database by switching to a backup copy, the issue should go away when done in conjunction with the networking issue above
https://support.plex.tv/hc/en-us/articles/201100678-Repair-a-Corrupt-Database
Just deleted my two IP subs I was using for Allowed Networks. Restarted and still no dashboard. Videos, movies and tv all come up but its JUST the original dashboard that gives you options, suggestions, etc. What else can i try.
New Logs after reset:
Jul 03, 2017 20:15:23.986 [4460] INFO - Plex Media Server v1.7.5.4035-313f93718 - Microsoft PC x64 - build: windows-i386 english - GMT -07:00
Jul 03, 2017 20:15:23.986 [4460] INFO - Windows version: 6.3 (Build 9600), language en-US
Jul 03, 2017 20:15:23.987 [4460] INFO - 8 3998 MHz processor(s): Architecture=0, Level=6, Revision=15363 Processor Identifier=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
Jul 03, 2017 20:15:25.483 [7160] INFO - Successfully retrieved OCSP response
Jul 03, 2017 20:15:31.575 [6324] INFO - Refreshing paths watched by LibraryUpdateManager
Jul 03, 2017 20:15:35.369 [7052] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_315E0djmVuy6Th8) - The system cannot find the path specified.
Jul 03, 2017 20:15:35.369 [7052] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:15:35.369 [7052] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:15:35.371 [7052] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:15:35.529 [6008] INFO - AutoUpdate: no updates available
Jul 03, 2017 20:15:35.886 [3652] INFO - Sync: downloaded 2 sync list(s) with 7 sync items(s): 0 new, 0 updated, 0 deleted
Jul 03, 2017 20:15:38.128 [0352] ERROR - PlexClient::downloadContainer: expected MediaContainer element, found html
Jul 03, 2017 20:15:38.129 [0352] ERROR - IVA: Error downloading trailers for source 1.
Jul 03, 2017 20:15:38.651 [1220] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_9D5ZmuGRyT6a1oz) - The system cannot find the path specified.
Jul 03, 2017 20:15:38.651 [1220] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:15:38.652 [1220] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:15:38.655 [1220] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:15:42.020 [7052] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_42Mkvo8HJifa0b0) - The system cannot find the path specified.
Jul 03, 2017 20:15:42.021 [7052] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:15:42.021 [7052] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:15:42.024 [7052] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:15:42.732 [3156] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (dc18e572-974d-49dd-81ef-66f315a2b5fe, expected 1d483d77-66fa-4908-8400-c6673ab042c0)
Jul 03, 2017 20:15:43.499 [3156] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (a40b5181-a174-466c-889b-1a7d65673a86, expected 276a9f69-4ece-406b-b5b0-8f617b4a611b)
Jul 03, 2017 20:15:43.500 [3156] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (48f9f359-2c51-4467-848d-fe5df2b1bc72, expected 276a9f69-4ece-406b-b5b0-8f617b4a611b)
Jul 03, 2017 20:15:43.867 [3156] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (1d483d77-66fa-4908-8400-c6673ab042c0, expected 276a9f69-4ece-406b-b5b0-8f617b4a611b)
Jul 03, 2017 20:15:46.756 [3852] WARN - PubSubManager: Connection to 109.237.24.233 failed: Unknown error.
Jul 03, 2017 20:15:47.163 [6460] INFO - AutoUpdate: no updates available
Jul 03, 2017 20:16:09.410 [5628] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_DEbvx0K1WN18Juo) - The system cannot find the path specified.
Jul 03, 2017 20:16:09.410 [5628] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:16:09.410 [5628] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:16:09.413 [5628] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:17:33.227 [5836] INFO - AutoUpdate: no updates available
Jul 03, 2017 20:17:34.954 [5836] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_kNB8pIphbFnehbO) - The system cannot find the path specified.
Jul 03, 2017 20:17:34.955 [5836] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:17:34.955 [5836] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:17:34.958 [5836] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:17:38.172 [6396] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_y0yf4l2eDq8FOsp) - The system cannot find the path specified.
Jul 03, 2017 20:17:38.173 [6396] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:17:38.173 [6396] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:17:38.176 [6396] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:17:39.360 [6396] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_psSImCsGfa9BgGz) - The system cannot find the path specified.
Jul 03, 2017 20:17:39.360 [6396] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:17:39.360 [6396] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:17:39.363 [6396] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:17:40.325 [7052] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_5C4hZlNElHQEEN6) - The system cannot find the path specified.
Jul 03, 2017 20:17:40.325 [7052] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:17:40.325 [7052] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:17:40.328 [7052] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:20:05.846 [6396] INFO - AutoUpdate: no updates available
Jul 03, 2017 20:20:06.702 [6396] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_zIxwJXJ7fTc0qPu) - The system cannot find the path specified.
Jul 03, 2017 20:20:06.702 [6396] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:20:06.703 [6396] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:20:06.706 [6396] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:20:10.668 [0780] ERROR - SQLITE3:90E481CE, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_58UwJ4fOdATOg33) - The system cannot find the path specified.
Jul 03, 2017 20:20:10.669 [0780] ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 03, 2017 20:20:10.669 [0780] ERROR - SQLITE3:90E481CE, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’, media_items.library_section_id as ‘media_items_library_section_id’, media_items.section_location_id as 'media_items_section_locatio
Jul 03, 2017 20:20:10.671 [0780] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 03, 2017 20:20:14.800 [6396] INFO - AutoUpdate: no updates available
Would you please just grab the entire set and post the ZIP? It’s much easier for us to see what’s going on. We cannot see much at all from that fragment.
Way too much to look for which isn’t included there
Sure! Here it is! Sorry I figured that same thing right when I posted that:)
So I just found a fix! I started noticing the errors here:
ERROR - SQLITE3:90E481CE, 14, cannot open file at line 41850 of [fc49f556e4]
Nothing had changed on my server at all or my database. It just started happening. So I though the only thing I did between now and a few days ago was Optimize a movie for a friend so they could stream it on a smaller device. I went to my optimized movies and deleted that single movie and rebooted the server for good measure.
Now My Dashboard/suggestions/etc shows up!!
I am going to change the title of this thread if possible to to help anyone that may have the same random issue. As ALWAYS, I appreciate the help form the members on this forum.
OK I should elaborate further… This DID fix the issue with the dashboard not showing when on the server but when I test on some of my Rokus, the dashboard doesn’t show! I feel like I was on the right track but not yet completed. Any ideas?
Update: The Fix I had listed earlier only corrected the issue on the server for a day. It is now back where I started. Does anyone have any suggestions?
My dashboard has not worked well on initial ‘hit’ to the server for well over 6 months. Subsequent requests for the dashboard work okay. This issue has come up from time to time in the forums, but I’ve yet to see a fix. 
I’ve optimized my database until I’m blue in the face. Hoping something gets figured out on this issue. I suspect your issue is the same one that is plaguing other users.
yep… I ended up, after optimizing, repairing etc, reloading an old backup and it worked and today this afternoon it was loading the dashboard just fine and all of a sudden, its Broken again!! This only started happening as far as I know with the new update.
Please tell me we are not the only two seeing this!?
I have just got the same error occurring. Never had it before
There was an unexpected error loading the dashboard
Please visit our forums if you continue to experience problems
PMS Version 1.7.5.4035
[edit] the error appears to have been caused by a lack of available drive space on the PMS drive. A quick clean up and I’ve returned to normal ops.
I am on the same version as well but I have plenty of space. I am testing out a theory about the antivirus real time protection and making exclusions. The Antivirus has never affected it before now so I am not sure this is the proper fix…will keep this updated.
UPDATE: I have noticed the blocking of certain folders with the Antivirus does not fix the problem. I did start looking into the SQLITE database and noticed it keeps complaing about reading a certain line from a file the cannot be found. Example:
ERROR - SQLITE3:7613717F, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\2\etilqs_1ittInWUDZ0qnZq) - The system cannot find the path specified.
Jul 16, 2017 22:04:57.527 [5044] ERROR - SQLITE3:7613717F, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 16, 2017 22:04:57.527 [5044] ERROR - SQLITE3:7613717F, 14, statement aborts at 668: [select distinct media_items.id as ‘media_items_id’,
C:\Users\ADMINI~1\AppData\Local\Temp\2---- this got me curious and I looked into this folder and to m surprise it did not exist.
Seeing as how this is in the temp folder and if you were to clean up/defrag your OS drives, this would be deleted.
I manually created the folder “2” that was missing from the Temp folder and the Dashboard is back up and running. Will monitor further and keep you updated.
Not a windows user but sa2000 was working with a user and discovered a mp\1 was actually a remote desktop temp folder and was causing problems.
If this means anything to you , then good.
I have no context or knowledge at this level. I’m only passing along a conversation fragment from debugging & another user thread.
@ChuckPA said:
Not a windows user but sa2000 was working with a user and discovered amp\1was actually a remote desktop temp folder and was causing problems.If this means anything to you , then good.
I have no context or knowledge at this level. I’m only passing along a conversation fragment from debugging & another user thread.
Do you know the specific thread for this or how I can search his posts?
This may not have any relevance but it may help and I will do the research. the “tmp” and “Temp” folder are a little different depending on where they are in the windows file structure. Also, I have noticed that my last “fix attempt” by creating the “2” folder, while it did fix it for now, I notice no files have been placed in this folder by Plex or anything else.
Thank you for your help and anything you can do further.
I often RDP into my server, but it is configured to auto login, and auto launch Plex at the console after reboot. I don’t recollect manually launching Plex via RDP recently. I’ve had to do it countless versions back, due to Plex instability where it would crash. But I’ve not had to do that recently.
If there is residual gunk in the configs or database due to launching Plex via RDP connection, unless there is some sort of guide or tool to fix this, I’ll just have to live with the dashboard failing to launch. Working in a database is far from my area of knowledge.
I shared what I have heard. I don’t have any knowledge in this realm. It seems to me that WIndows Remote Desktop has options where this is set/controlled (each desktop session gets its own tmp directory). If completely stuck, ping @sa2000 in a post . I suspect multiple tmp directories is a common thing given it’s windows and google probably has the answer as well.
