recording service suddenly fails to start

[sub]

I noticed in config.xml that I had duplicate entries of tuners, so I deleted them all and then ran my batch file which kills all NPVR related items and restarts them. I right-clicked in NextPVR, selected Settings, verified the Devices info, then clicked ok and got the attached crash.

That error is just saying the recording service isn't running.

[Wakalaka]

Everything was working fine until tonight. I have not deleted any devices recently. I did add the PCIe Radeon 7750 video card on the weekend, but that shouldn't make any difference.

I manually updated the EPG and nothing changes, not even "nrecord.exe RUN"

[sub]

If you zip and attach your npvr.db3, hopefully it'll show the same error when I try to run it here.

[Wakalaka]

SQLiteSpy to the rescue! I looked at the SCHEDULED_RECORDINGS table, saw a bunch of capture_source_oid that didn't match the oid values in config.xml, and ran "delete from SCHEDULED_RECORDINGS where oid > 11000". Restarted all NPVR apps, everything is now happy. I have to recreate all of my Recurring recordings so proper oid values are used, but that's no big deal. Recreating them appears to be working because items are now in Pending. (I use TV Listings plugin).

The mystery is "why did capture_source_oid values change"? I did not yank any tuner devices from the pc or network, did not touch config.xml, did not mess with NPVR Settings -> Devices. WTF?

[sub]

The mystery is "why did capture_source_oid values change"? I did not yank any tuner devices from the pc or network, did not touch config.xml, did not mess with NPVR Settings -> Devices. WTF?

I dont know. I've not seen any other reports of this problem.

Glad you got it sorted though.

[Wakalaka]

I did power off my system, disconnected all cables, and installed a PCIe video card. Could reconnecting the network cable have made NextPVR think it detected new devices? Have you tested this scenario?

[sub]

I did power off my system, disconnected all cables, and installed a PCIe video card. Could reconnecting the network cable have made NextPVR think it detected new devices?

No, it wont be related.

Have you tested this scenario?

Installing a new video card? No, that isn't a scenario I'd actively test. I have installed a new video card in my systems in the past though, and not had this problem. I'm sure plenty of other users have installed new video cards in the past too.

[Wakalaka]

Is it possible to make NextPVR more robust with the following:

1. Check capture_source_id values against config.xml values.
   
2. If any oids do not match, prompt user with this info.
   
3. Tell user solution will be to delete all scheduled recordings that do not match tuner oids.
   
4. Delete the bad scheduled recordings for user.
   
5. Dump deleted recordings to a text file so user can reference it.
   

It was pretty nasty to get recording service crashes, then search to find "nrecord.exe RUN" as a test for more debugging info, then edit config.xml to delete tuners so they get redetected and use sql command to delete bad scheduled recordings as my solution.

Your SW is superior to other solutions but could use an increase in robust level. I just set up my neighbor with NextPVR and EventGhost after I convinced him to dump his 15 year old PC and get a new one, along with dumping his tube tv and replace it with a big modern TV. I'm reminding him to send in his donation.

[sub]

Do you still have the database that causes the crash so I can see the problem myself?

Given we've only had a single report of this ever happening, it's probably not worth doing anything.

[Wakalaka]

I don't have my old npvr.db3 file. You can reproduce it by making the capture_source_oid values in SCHEDULED_RECORDINGS not match oid values in config.xml <Tuners> entries.