mingdynasty
Programmer
I have a DTS package that is scheduled to run twice a day. About a month ago, the morning jobs begain having intermittent problems. It would stop at a step and not continue. I can start the package manually and it runs fine manually.
The package consisted of several steps in the beginning that executed some stored procedures. The heavy lifting is at the beginning. At the end, it runs VBScript to create some files.
I turned on the logging of the package. From the log, it appears every step runs as expected but I can tell certain steps are being missed. I put in every step commands that insert a timestamp record every time the package reaches certain points of execution (i.e. "Beginning Step 15"). It is evident that it does not run everything because certain points are missing. Anybody else have any ideas how to track this problem further?
The package consisted of several steps in the beginning that executed some stored procedures. The heavy lifting is at the beginning. At the end, it runs VBScript to create some files.
I turned on the logging of the package. From the log, it appears every step runs as expected but I can tell certain steps are being missed. I put in every step commands that insert a timestamp record every time the package reaches certain points of execution (i.e. "Beginning Step 15"). It is evident that it does not run everything because certain points are missing. Anybody else have any ideas how to track this problem further?