Hi Libor,
After the change this weekend, I did encounter more errors, which says to me that this change did not resolve the problem.
There is one thing change though that I decided to make, which has helped significantly. Basically, I realized that the tasks that were getting this shut down message had other toad tasks running and starting at the exact same time. Therefore, I decided to move the start times up a few minutes to ensure nothing started exactly the same. At this point, I've seen this issue only once more on a task that runs every hour. I'm going to keep looking into this one, as it's hour may run into another time at some point.
I'm not saying this fixes it, but it seems like it sure helps.
With that said though, I realize spacing the tasks out a few minutes is probably always helpful, but should this still be an issue with the toad data point application? I understand it makes these temp files when the task is started and is running, but is there an issue somewhere that maybe needs looked at, regarding how maybe these tasks are causing possible issues with two tasks starting at the same time, maybe trying to access the same temp file instead of its own unique set of files?
I don't know how this process works, but I'd think that the application should be able to support tasks running at the same time regardless, simply because of some end users may need this type of availability with many so many tasks needing ran at a certain time.
Just wanted to get your thoughts and suggestions on this.
Thanks!
Chad