SchedulesDirect not updating automatically

[rtangwai]

I'm in the Eastern time zone. I have already changed my update time to 6am and so far it hasn't failed, so you theory is looking good right now.

[Zeb]

Sounds good, but if update should fail again, please post logs. I would've expected your log to show SchedulesDirect timing out rather than yielding invalid data, but perhaps that was just a fluke. In any case, there's no reason to think it was a problem with NPVR software.

[steve232]

Sub, the guide has been fine since I moved my update time, like others have offered.

Thanks
Steve

[sub]

Great - I was sure it was a problem at the Schedules Direct end rather than NextPVR.

[donschjr]

I moved my update time again to 2 pm when my pc records my Wife's show but I still don't get auto update of the guide. I had moved my update time before without success but I thought having it update during a recording would fix it, apparently not.

[sub]

I moved my update time again to 2 pm when my pc records my Wife's show but I still don't get auto update of the guide.

As others mentioned above, 2am is a pretty busy time at schedules direct, and several people had timeouts in their logs. I'd try some other time.

[Zeb]

Sub, maybe you should take another look at this case. The rather old Nrecord logs posted by donschjr above appear to show error-free updates at 3am on March 3 and March 4, but then something went wrong at 3am on March 5:

2013-03-05 03:00:02.507 [DEBUG][8] Pre EPG Update
2013-03-05 03:00:08.144 [DEBUG][4] Resuming...
2013-03-05 03:00:15.016 [DEBUG][7] Recording service noted the system was resuming...
2013-03-05 03:00:15.016 [DEBUG][7] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2013-03-05 03:00:16.523 [DEBUG][5] cycling MVP servers
2013-03-05 03:01:32.511 [DEBUG][8] About to update EPG
2013-03-05 03:01:32.527 [DEBUG][8] Updating EPG...
2013-03-05 03:01:32.550 [DEBUG][8] No C:\Users\Public\NPVR\Scripts\UpdateEPG.bat file found
2013-03-05 03:01:32.550 [DEBUG][8] Checking for any Schedules Direct listings
2013-03-05 03:01:32.785 [DEBUG][8] Processing ScedulesDirect LISTINGS
2013-03-05 03:01:32.785 [DEBUG][8] Requesting listings for the period: 2013-03-05T00:00:00Z to 2013-03-19T23:59:59Z
2013-03-05 03:01:32.785 [DEBUG][8] Requesting listings from Schedules Direct
2013-03-05 08:45:02.893 [DEBUG][16] Resuming...
2013-03-05 08:45:02.963 [DEBUG][16] Resuming...
2013-03-05 08:45:03.135 [DEBUG][7] Recording service noted the system was resuming...
2013-03-05 08:45:03.135 [DEBUG][7] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2013-03-05 08:45:04.229 [ERROR][8] Unexpected error getting listings from schedules direct: System.Net.WebException: The operation has timed out.
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
at System.Net.WebClient.UploadData(String address, String method, Byte[] data)
at NShared.SchedulesDirectEPGSource.LoadChannelsUsingSAX(IEPGUpdateCallback callback, DateTime epgStartDate, DateTime epgEndDate)
2013-03-05 08:45:04.229 [DEBUG][8] The operation has timed out.

An even older Nrecord log shows the same error at 3am on March 2. I'm barely beyond the newbie stage, but looks like a failure to awake, perhaps related to another ongoing thread:

http://forums.nextpvr.com/showthread.php...rding-why&

[johnsonx42]

those logs just mean that it never got anything from Schedules Direct, and eventually got bored waiting and fell asleep.

[Zeb]

I can't really argue with a senior member, but merely note that logs of successful updates do not include (line 2) Resuming... or (line 4) No C:\Users\Public\NPVR\Scripts\Wakeup.bat. Of course 3am Eastern time equals 2am Central - another time zone with considerable population served by SchedulesDirect. Better choices might be 1 am or 6 am.

[johnsonx42]

you're always free to argue with a senior member, we can be wrong. even sub was wrong once I think... just once

successful updates happen in just a few minutes, so the machine doesn't have time to fall asleep during the update. in the log snippet you posted, note that the line "Requesting udpates from Schedules Direct" happens at 03:01am, and then the following line "Resuming" doesn't happen until 8:45am, nearly 6 hours later. all this means that NRecord sat there waiting for the SD server to respond and got nothing, and then the sleep timeout expired so the system went back to sleep.