My later addition of ON FAILURE sub-packages are not being
executed and yet there is failure.

Illustration:
Suppose package

A--success-->B--success-->c

is already pre-compiled/Executed (and is running fine).
On adding ON FAILURE D, E and F i.e

A--success-->B--success-->c

D does not execute when A fails, neither does E Execute
when B fails and the same applies to F when C fails.
The execution sequence shows D, E and F being placed after
C.
Isn't there some setting that I need to configure? I have
made sure that the work flow properties of D has Source
Step = A, Precedence = Failure and Destination Step = D
and the same configuration applies to E and F.

Jm

Joseph:

A little common problem when executing packages through the Execute Package
Task: You must check the "Fail package on first error" on the Logging tab
of the Package Properties for the callee (child package) for the failures to
propogate up to your caller package. Otherwise, the child package will
always return Success to the caller and your illustration will always
execute A then B then C no matter if the child packages succeed or fail.

Scott

"Joseph Mong" <anonymous (AT) discussions (DOT) microsoft.com> wrote

Thank you Scott:
I actually had to remove the "Fail package on first error"
because I needed the ON FAILURE child packages to execute.
Thanks again.

Joseph