Recordings Failed due to date change?

[dinki]

Last night I wanted to watch something that was supposed to be recorded yesterday and found that the recording had failed. I looked at my recordings screen in EWA and found that I had very many failed recordings, all of which were on future dates. I deleted all of these and also deleted the recurring recordings associated with these. I tried to reschedule these recordings but I received a failure for the upcoming recordings. I'm guessing it's because these recordings are marked as deleted? I scheduled a new recording for a program I've never recorded and it recorded just fine. Also, I rescheduled some of the recurring recordings on a different channel (I have multiple NBC, CBS, ABC affiliates) and they scheduled fine as well.

Recently I mistakenly changed my gbpvr box's date to one month in the future (August). I rebooted, did a few things and then changed the date back to what it should have been.

Any ideas on what can be done to fix this? Will this 'auto correct' itself and only affect the recordings that were scheduled that had information in the database at the time of the time change, or is this not the problem at all?

Many thanks.

[martint123]

It should sort itself out.
My machine recently got an incorrect date from time-a.nist.gov where I point my time grabber - it got 27th July instead of 7th July - it made a real mess of pending recordings. I ended up doing an 'empty epg' within config, deleting 'failed recordings', reloading the EPG and then keeping my eyes on it.
A bit of a nightmare at the time.

[sub]

Recordings Failed due to date change?

Yes.

When the recording service see it has pending recordings for a date in the past, it assumes it was turned off at the time the recording was supposed to occur, so marks the recording as failed.

[Jim_]

Last night I wanted to watch something that was supposed to be recorded yesterday and found that the recording had failed. I looked at my recordings screen in EWA and found that I had very many failed recordings, all of which were on future dates. I deleted all of these and also deleted the recurring recordings associated with these. I tried to reschedule these recordings but I received a failure for the upcoming recordings. I'm guessing it's because these recordings are marked as deleted? I scheduled a new recording for a program I've never recorded and it recorded just fine. Also, I rescheduled some of the recurring recordings on a different channel (I have multiple NBC, CBS, ABC affiliates) and they scheduled fine as well.

Recently I mistakenly changed my gbpvr box's date to one month in the future (August). I rebooted, did a few things and then changed the date back to what it should have been.

Any ideas on what can be done to fix this? Will this 'auto correct' itself and only affect the recordings that were scheduled that had information in the database at the time of the time change, or is this not the problem at all?

Many thanks.

Unfortunately the failed recordings will be in the database until their time has passed.

Unless somethings changed, you’ll need to manually edit the sql or mdb database and delete the “RECORDING_SCHEDULE” entries that have a “status” of 3.

Or if you have sqlite3.exe in your gbpvr folder (and you’re using the sql database), you can create a batch file that will do it for you.
I run the example command in UpdateEPG.bat each evening to avoid overlapped listing in the guide.

DeleteFailed.bat

Code:

sqlite3 -separator ": " "C:\Program Files\DEVNZ\Gbpvr\GBPVR.DB3" " SELECT status, filename, manual_start_time FROM RECORDING_SCHEDULE where status = 3" >>"C:\Program Files\Devnz\GBPVR\logs\DeleteFailed.log"
sqlite3 "C:\Program Files\DEVNZ\Gbpvr\GBPVR.DB3" " DELETE FROM RECORDING_SCHEDULE where status = 3"

Pause

You can delete more than one recording type at a time by adding more types to the script.
Example:
sqlite3 -separator ": " "C:\Program Files\DEVNZ\Gbpvr\GBPVR.DB3" " SELECT status, filename, manual_start_time FROM RECORDING_SCHEDULE where status = 3 or status = 5 or status = 6" >>"C:\Program Files\Devnz\GBPVR\logs\DeleteConflicts.log"
sqlite3 "C:\Program Files\DEVNZ\Gbpvr\GBPVR.DB3" " DELETE FROM RECORDING_SCHEDULE where status = 3 or status = 5 or status = 6"



STATUS_PENDING = 0
STATUS_IN_PROGRESS = 1
STATUS_COMPLETED = 2
STATUS_COMPLETED_WITH_ERROR = 3 <failed
STATUS_PLACE_HOLDER = 4
STATUS_CONFLICT = 5
STATUS_DELETED = 6

[dinki]

Thanks for all the info guys!

Jim, I tried your script but it doesn't appear to have worked. The log file is 0bytes and the deleted entries are still there. Is the status 3 or is it 6? When I was trying to clean things up I deleted the entries from the EWA recordings page.

[Jim_]

Forgot about the EWA’s option to delete failed recordings. If you deleted them in EWA, they should be gone and their wouldn’t be anything for the script to do.

As in my post above, Failed = 3
A user "canceled" recording = 6

[dinki]

I tried with 6 as well. I then dumped the EPG data and reimported and everything seems to be in order again. Thanks to all for the help.