Windows Task Scheduler kills tasks that appears to be non-responsive

[mariobiron]

Hello,

I have scheduled a program to run every morning that will pull data out of our SQL server (the tool is "Toad"). I want to have that data ready when I come in the morning.
Problem is, at that time, there are other tasks running on the SQL server making in slower to spit the data out, but it eventually sends it, always. Windows 7 (or the Task Scheduler itself, I am not sure which one) seems to think that the program has become unresponsive and stops it.
When I look at the history of the task, it says the last execution status is "(0x0)" meaning completed successfully. I know it did not because the Excel spreadsheets that receives the data is still open and hasn't received all the data it should - it nevers stops at the same point so it is not an issue with my retrieval scripts.
If I launch the task manually during the day, when the SQL server will respond in a timely manner, the task will complete successfullly.
If I use the tool itself, it never gets killed, and I haven't seen Window complain it has become unresponsive even when it runs for a long time.
So if anyone else experienced this issue and has solved it, how did you do it?
Otherwise, anyone knows of any settings that would prevent Windows or Task Scheduler to kill what it thinks are unresponsive tasks or at least, change the delay before it thinks so?
Thanks!

 

[oreo27]

Hello oreo27!
Thanks for the quick reply and suggestion; I did indeed open a new thread after I answered this one, but I wanted to maximize my chances of getting an answer by doing both since he appeared to have suffered the same issue I did!
If by any chance you can remember what the registry key is, my new thread is here: http://www.sevenforums.com/performa...duler-kills-tasks-appears-non-responsive.html

Thank you!

Well, as for the registry key I lucked out. I just can't seem to find it.

However, there might be a silver lining in this program:

Ultimate Windows Tweaker, a TweakUI for Windows 7 & Vista

Go to the Performance tab.

There is an option there to change the kill time for non responsive tasks. I believe the maximum option is 5 seconds as opposed to the default of 4. I know that's not much gain but maybe if you can find the exact registry key it edits, you can manually edit that.

Another thing is a checkbox that says "Auto-end non-responding applications". On my system however, that is already unchecked. I'm not sure if I changed that at any given point in time so I would assume that's by default.

I can't vouch for the effectiveness of that app as I barely used it, only to customize OEM info before.