My QNAP PMS still is recording shows even though I deleted the DVR. I had to completely shut down the PMS service to get it to stop.
It’s in media_provider_resources.
Be warned that after I did my database surgery it worked for a while, and then I ran into the empty guide problem. I had to completely redo my xTeVe config.
1 Like
Yep - ok - thanks - I also have some leftover entries in that table - I may try deleting those old ones out and see how things go over the next few days.
So far so good - I deleted only the entries that had url ip addrs that referred to old, deleted tuners no longer on my network. Since I did that yesterday - I have tested tuning to various live channels - no issues so far. It also successfully recorded 6 shows yesterday - some of which were overlapping - requiring a couple of simultaneous tuners - not the busiest day I have set up for recording - but a decent test… Also was able to successfully tune various live stations today…will see how this goes - it would typically fail to tune anything after a couple of days of successful running - so it will take a few more days of success before I think I can declare the problem I was seeing as fixed.
1 Like
The unable to tune errors due to the 5 second timeout seen mostly on PCIe and USB tuners (and also on networked tuners to an extent) has now been addressed in release 1.13.9.5456 which extended the timeout to 15 seconds
- (DVR) Extend initial timeout value for live TV tunes to avoid giving up on a tune too early (#9211)
Continued to be able to tune live TV with no issues. Also recorded 6 shows with no issues last night - several of them simultaneous. I am going to let it go one more night on the same level (5439) before updating to 5456 just to see if the deletions I did of those old dvr’s still seem to be helping avoid the “Unable to tune channel (no parts)” error that I was seeing after a couple of days from each restart of the server.
@sa2000, Still getting “Unable to Tune channel (No parts)” after upgrading to 1.13.9.5456. Logs are attached. I did some live TV viewing of different channels before 10:00 am. Recorded “Price is Right” at 10:00 am on channel 5.1. Believe I watched the live recording for a few moments on a client to test time shifting. Didn’t do anything else with Live TV or DVR.
At 2:09(ish) pm I tried watching Live TV on channel 5.1 and got the dreaded above error. Logs are attached. Plex Media Server Logs_2018-11-01_14-10-04.zip (5.4 MB)
Once I restart PMS, that channel will immediately work.
Is your server trying to use a ghost dvr device ? I had to delete couple of entries from HDHomeRun I had in my system in older PMS version that do not exist. See the messages above that tallk about that error.
I will give that a shot and see if I can still produce the error.
UPDATE: Deleting old entries in media_provider_resources did not fix anything.
Just updated to latest PMS on Nvidia shield, Still same issue when trying to watch LiveTV thru Apple TV plex client. HD homerun connect is hardwired. Wheel keeps spinning on ATV4 and NO LIVE TV for 3 weeks now!!! C’mon plex!!
BTW…its only an issue with the PMS on Nvidia shield. The PMS updated to 1.13.9.5456 on MBpro works just fine.
@sa2000 pretty sure I’ve seen some of those same dead tuner messages (in my case, I’d used a different model HDHomerun for a while and replaced it with a different model), and I’ve had quite a few problems with Live TV/DVR… is there an “approved” way to clear out the old tuner entries (they don’t appear in the GUI)?
Just another update since I manually deleted those old DVR entries from the database - successfully recorded 4 shows last night using up to 2 simultaneous tuners. I think I am going to stay on 5439 for a few more days - have some recordings scheduled of some upcoming football games over the weekend - will see how those fare.
I’ve upgraded to the latest version released 10/30. I tried to tune to live TV after upgrade and got the network error message. Restarted, failed again 2-3 more times. Restarted the last time and it worked. Unfortunately for me, the experience is and always has been inconsistent. I will try to attach logs later this evening.
I’m curious about stale DVR entries in the database. I am running PMS on Windows 10. Can someone tell me where the database is located so I can see if I have any entries that need to be deleted?
I also found this, after 3 restarts I could then play Live TV again. Not got any hopes up for it lasting, tempted to install a older version again.
Here’s some logs anyway:
Plex Media Server Logs_2018-11-02_21-42-42.zip (2.1 MB)
Back up your .db files before you change anything.
…Plex\Plex Media Server\Plug-in Support\Databases\com.plexapp.plugins.library.db
Back up your .db files before… you get the idea.
The table is called media_provider_resources.
I am so incredibly frustrated with Plex… I can’t tell you how many hours I have spent doing QA and debugging on their behalf.
They should pay ME a lifetime debug pass. It’s been five years, and half the ■■■■ doesn’t work even now.
“There was an unexpected error during playback. Please visit our forums if you continue to experience problems.”
Bwaaaaaaa-hahahaha. Right.
Sadness. 
My path to the .db file was different:
...Plex\Plex Media Server\Resources
When I opened the .db file with SQL Lite browser there was no table called media_provider_resources
After struggling for a year with Plex Live TV/DVR and multiple models of HDhomerun, I have decided to cancel my PlexPass. I am now using CHANNELS and it is rock solid. Instantly loads the channel and a great interface for the guide.
Maybe when Plex fixes the issues, I may revisit.
My issues are with an PR2100 nas and iOS devices(atv, mobile devices, Mac OS, windows 10)
Just wanted to add that I completely uninstalled Plex and re-installed creating a new database etc… After one day, I received my first missed recording and “Unable to tune channel (no parts)”.
Hope this helps for people that are trying to edit databases thinking that will solve the problem. This was a fresh install, fresh database, and still ran into the issue.
Did you physically remove your data - or did you assume the uninstall did that - because I seem to recall that an uninstall does not remove the data.
