Hi There,

We have a package in production that has not been changed in awhile. It runs every day on a scheduler off hours. It run when there is no other interference on the server. This package at one day did not run three subsequent steps out of many it was supposed to run. The DTS log did not report any errors and did not report the first out of three steps was started, it just was not on the log. I do not have to say there was no trace of the other two steps. From the first look the log was clean as a vessel. I discovered the failure by comparing two subsequent logs. It behaved as if the first out of three steps was disabled. The steps do not have workflow scripts and their properties are not set via dynamic properties task, so they are static in nature.

If anyone experienced anything similar, please come forward and share.

Thanks,

Ilya

Hi All,

I do not know what it was, but after rebooting the server the issue has not come back.

Ilya
"Ilya Margolin" <ilya_no_spam_ (AT) unapen (DOT) com> wrote

Hi There,

We have a package in production that has not been changed in awhile. It runs every day on a scheduler off hours. It run when there is no other interference on the server. This package at one day did not run three subsequent steps out of many it was supposed to run. The DTS log did not report any errors and did not report the first out of three steps was started, it just was not on the log. I do not have to say there was no trace of the other two steps. From the first look the log was clean as a vessel. I discovered the failure by comparing two subsequent logs. It behaved as if the first out of three steps was disabled. The steps do not have workflow scripts and their properties are not set via dynamic properties task, so they are static in nature.

If anyone experienced anything similar, please come forward and share.

Thanks,

Ilya