Scheduled task

ctd · Post by **ctd** » Wed Sep 29, 2010 6:12 am

Any chance you're doing this in VBA? I've noticed erratic/inconsistent behavior in macros I've written in the past and ultimately wasn't able to determine why, aside from the rationale that VBA was simply mischievous and tended to act out when I wasn't paying attention.

Perhaps try carrying out the process via a different paradigm or on a different machine?

jungle · Post by **jungle** » Wed Sep 29, 2010 11:18 am

Thanks for the replies.

Tradenator: I've already checked - it's not an issue with power saving settings.

CTD: code is in C#.

Hansi · Post by **Hansi** » Wed Sep 29, 2010 12:08 pm

Had a similar issue with a server running Win 2003. Code was in C# and the thread was set to sleep for x hours selectable by user. For some fucked up reason the server didn't define seconds from the C# code as 1000ms but as 770ms (used another app to clock it) so I wound up using Thread.Sleep(770 * 60 * 60 * hours). 1000ms worked fine on another server. Never found out what caused it because my boss just told IT to wipe the server and set it up fresh and then it worked fine.

aix · Post by **aix** » Wed Sep 29, 2010 12:16 pm

> Other times it starts late and doesn't run ok, i.e. the task never completes.

You're suggesting that "starts late" and "never competes" are related.

By "never completes", do you mean it dies or hangs?

If the latter, I'd try attaching a debugger to the hung process to figure out its state. This might shed some light on what's going on.

In either case, I'd add logging throughout the task to see if I can figure out how far it gets on those occasions when there's a problem.

aix · Post by **aix** » Wed Sep 29, 2010 12:38 pm

Also, do the executable or any dependencies (DLLs etc) live on a network share?

jungle · Post by **jungle** » Wed Sep 29, 2010 1:59 pm

By "never completes", I mean "hangs". I suspect that detailed debugging is probably the answer, though I was hoping I might be able to avoid that.

There are no DLLs on a network share, all of them are local.

jungle · Post by **jungle** » Wed Jan 26, 2011 7:24 pm

Update: running Scheduled Tasks when the PC has just been restarted (but I haven't logged in) seems to cause problems. There is obviously a quick 'n' easy workaround here!

aix · Post by **aix** » Wed Jan 26, 2011 7:47 pm

Is the Windows account under which the task is scheduled to run permissioned to Log on as batch job?