I am rather new to DTS, and the problem I have seems to be rather odd.
I have a scheduled DTS Package (say Pkg-S) that simply executes a bunch
of other packages sequentially based on the workflow properties.

Pkg-S executes Pkg-A, Pkg-B and Pkg-C first.
Then, on success of Pkg-A, Pkg-D is executed, on success of Pkg-B,
Pkg-E is executed, and on success of Pkg-C, Pkg-F is executed.
So basically I want all the packages (A to F) to execute given that the
respective predecessor packages executed successfully.

The problem is, on schedule, Packages A to C execute without error,
however, Packages D to F don't even get started.

All packages executed without problem through the designer, and the
package log as well as the job log shows no errors. For testing
purposes I even added a simple package that would insert a field to a
table and set this package to execute "On Fail" for Pkgs A to C, and
even that does not seem to execute. In other words, Pkgs A to C seem to
neither complete successfully, nor fail, as far as the workflow is
concerned. And according to the logs, they complete without the
slightest problem.

None of the options about "Fail package on step fail", etc have been
turned on, and logging on the server is turned on for all packages.

Any help would be greatly appreciated.

See if this helps you:
http://support.microsoft.com/default...269074&sd=tech

Enable package log and see what error you are getting.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @ http://vyaskn.tripod.com/



"KGoradia" <kaushalgoradia (AT) gmail (DOT) com> wrote

Thank you Narayana for you quick response.

I apologise for not being more clear in my original post, but what I
meant to say is that all packages have logging turned on on them. And
all "Fail package on step fail" options have been turned off.

I have already been to the link you suggested and checked every
scenerio mentioned in that article without any success.

And that is the most interesting part of the problem; None of the
packages, the "primary" ones nor the ones that are executed upon the
successful completion of the "primary" ones, are reflected as having
failed in the slightest way.
The "primary" packages are shown as having executed successfully in
logs, etc. and the ones dependent on them show absolutely no sign of
having run at all.