recordings not starting when scheduled

[securitnick]

I'm having a problem recording, but I'm not running VM Ware or any virtual machine. I'm running straight Windows 7 Pro 64bit. Using XBMC with NPVR as the PVR backend. I have an OTA antenna pulling in whatever channels it gets, and as far as live viewing, everything works great. I have the EPG working with an XML file that pulls data from (I think) where Windows Media Center actually gets it's EPG data (not pulling from WMC, but from the source it uses). When I attempt to record anything, whether it's a future program scheduled or even the program I'm currently watching (and this happens either in XBMC or in the NPVR client), a timer is created and looks right, but it just never actually records. In fact when it gets to the time for the recording (and after the time), it says, "next recording is..." whatever that timer was. So it's almost like something is just hanging up and the service doesn't realize it's the right time to record or something. I am fairly sure all my settings are correct, I've checked it over many times. I even played around with changing the recording directory to see if that was somehow the problem, but it still didn't work. I doubt this makes a difference, but I do have Windows and NPVR installed on a SSD drive and I have another larger hard drive that i'm using for storage. Any help would be great. I really like NPVR especially since I finally got my local channels and EPG working well with it.

[johnsonx42]

moved your post, since it had nothing to do with the thread you posted in. New users always seem shy to start a new thread, just post in some other thread, don't want to get too noticed right off...

it sounds like your recording service isn't actually running. please read post #2 of the sticky thread at the top of the forum, also linked in my signature, then post your logs.

[martint123]

Don't be shy we're all here to help
As requested, zip up all log files and attach here - it would also help if you mention the name/time of one of the failing recordings so we're sure we're looking at the right thing.

[securitnick]

See attached for my logs. I think you're right in that the recording service isn't running, but I'm missing on how to get it started. I would assume this process would start automatically, but I guess it's not. Let me know if you have any suggestions. Thank you.

[sub]

yes, it'd normally start automatically.

It looks like you database is broken. Did you upgrade from an earlier version, or is 3.1.1 the first version you've installed?

Try running "nextpvr.exe -updatedb" to see if it fixes it.

[johnsonx42]

Your database is missing a table (TEMP_FILE) which is causing the recording service to fail on certain functions. This is the second time we've seen this; was this a new install, or an upgrade? I'm not sure why this is happening.

You could try running "NextPVR.exe -updatedb" and see if that creates the missing table, I'm not sure if that would do it or not.

If that doesn't work and you don't mind starting over with your config, you can just exit NextPVR, stop the recording service (use the "Stop NPVR Service" icon in your NPVR program group), and then delete your "npvr.db3" file. Then if you "Start NPVR Service" it will create a new database that will have the correct tables and you go back into NextPVR->Settings and setup your config again.

@sub, why do you think some users are not getting this TEMP_FILE table added to their database? So far I think the two users who've reported this have been new installs, not upgrades.

(note: I started typing this before I saw sub's reply)

[sub]

@sub, why do you think some users are not getting this TEMP_FILE table added to their database? So far I think the two users who've reported this have been new installs, not upgrades.

If it had been new installs, then I'd suspect it's missing the table in the empty.db3 file, but I checked and it's definitely there.

[johnsonx42]

yes, I checked the same myself. I need to find the other thread where this was reported, see if theirs was a new install.

[johnsonx42]

yeah, you're right, the other one wasn't a new install. he'd been playing with 2.6.2, then upgraded to 3.1.1 and got the TEMP_FILE issue. it stuck in my head as a new install because he ended up just deleting the npvr.db3 as his installation was still "new" and had nothing worth worrying about in the database... not quite the same as a new install.

must just be something going wrong during the upgrade install, the updatedb process is getting missed somehow in a small minority of cases. happens with every upgrade.

[sub]

must just be something going wrong during the upgrade install, the updatedb process is getting missed somehow in a small minority of cases. happens with every upgrade.

It could also be a case of people backing up and restoring their npvr.db3 file (in effect removing the database updates).