SchedulesDirect not updating automatically

[sub]

donschjr, after how many minutes of inactivity will your machine go to sleep?

The app tells the Windows that the machine is still in use immediately prior to requesting the data from SD, but it can still go to sleep if you've configured it to auto sleep in less minutes than it takes SD to respond.

[donschjr]

I have my pc set to sleep after 30 minutes. I think you misread my last post I changed my update time to 2 pm not am and my pc is recording my wife's soap at that time and the soap is an hour long. I made the change to that time last week but I'm still not getting updates.

[sub]

The logs you posted only show attempts to update the epg at 3am.

There is no longs showing it at 2pm. Did you restart the recording service after making that change?

[donschjr]

When I check settings it shoes 1400 as update time and I've even rebooted the pc since.

[rtangwai]

Just to update everyone, switching the update time to 6am EST from 2am EST seems to have fixed the problem for me. I deliberately picked 6am as it is after 2am PST so my NPVR box would not have to compete with the West Coast for SchedulesDirect updates. Switching to 6am has no personal effect on my schedule - fortunately for me I'm a firm believer in waking up at the crack of noon

[mikeh49]

I update at 4:00PM Pacific and have had no problems. There is virtually never a recording or watching at this time, so the box wakes up, updates, and goes back to sleep. My sleep timer is 5 minutes.

[sub]

When I check settings it shoes 1400 as update time and I've even rebooted the pc since.

You were missing the most recent nrecord.log in your log file, so you may have missed the logged that showed it at 1400.

[donschjr]

I've had successful updates the last couple days, I'll keep an eye on it for a while but hopefully this problem is solved and on to the next one.

[jamhandman]

I was having this issue and change my update hour to 10. Everything seems fine for now... I didn't actually check the logs to see if the server request was timed out, but if I do see this again I will check the logs.