New
#1
Windows Task Scheduler kills tasks that appears to be non-responsive
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!