One of the suggestions was to use the NT Performance Monitor to monitor threads and handles. The collected information could provide the clue to what is leading to the handing and from that we can figure out how to avoid it. If you were able to collect the performance data please let me know. On other hand if you provide more information on the jobs and environment it may also help in figuring out if you are having job with side effect or you are experiencing something else. It is a good idea to send all log and performance files as well as the job database file to support@softtreetech.com for throughout analysis. You might be able to see the root of your problems in the job setup or job performance statistics. : Please see my previous posts entitled "24 x 7 just stops for no : reason" before reading this: The saga continues. : I made all the changes you suggested. The 24 x 7 scheduler version 3.1.3 just : stoped again. There is nothing within statistics to indicate that memory : was low. It was at about 94% when the job ran the night before. It just : discontinued running. : Any other suggestions?
|