I have gone through quite a number of threads where people had similar
problem: parent package calls child package, a step in child fails,
child completes anyway, parent doesnt fail.

As per the other threads, I have set the following logging properties:

In child package / package properties / logging tab:
- Fail Package on First Error

In parent package / execute package task / workflow properties /
options:
- Join Transaction if Present
- Rollback Transaction on Failure


The issue doesnt go away, though. Parent/child still happily
completes.


....I've also iterated and tried a number of additional things
including:
- Execute on Main Package Thread (in parent / workflow prop / options)
- Fail Package on First Error (in parent properties)


The issue doesnt go away, though. Parent/child still happily
completes.




....HELP!!...


-Blair.

No matter the result of the child package the package task in the parent will
always show a success (apart for times that the child dosn't exist) because
it has run it. A solution would be for the child to generate a global
variable indicating its result and hte parent using it to decide wheter to
contine or not.


"Blair" wrote:

A-HA!!!! Man, this was a tough one to solve.

Bottom line was that there were a few things happening. The main
issue was that my parent package was calling the OLDEST version of my
child package, not the NEWEST one (which had my fixes).

Recall that DTS stores history and uses Package Version IDs to
distinguish the various versions. This ID must be updated to point to
a NEWER version of a child package, or alternatively, you can remove
all old versions of child packages so that only one version remains so
that the parent will unambiguously call that package.

Specifically, if you go into Parent Package's Execute Package Task /
Properties / General Tab you will see the child package listed along
with its specific Version ID (e.g.
{4A4A3A19-01E2-47EE-805A-FCE8EFE273A6}). You will want to make sure
this points to correct child package.

Go into child package's Package Properties / General Tab and you will
see the Version GUID. If it's different (such as
{D8DE860D-684C-4296-A9B2-E01A495AE561}) then you know the parent isn't
calling the child that you're thinking it's calling and you need to do
one of two things:
1) go into Disconnected Edit and "re-point" the Execute Package Task
to the correct Version GUID of the version of the child you want, or
2) remove all history (except most recent versions) of all your child
packages.


Without doing this, it can drive you nuts (as it did me) as it appears
nothing you're doing in child package is fixing the problem or making
a difference.

Then, once you're sure you have the parent calling the right version
of the child, then just follow the instructions of a dozen other
threads to ensure that it fails on first error, etc....


-Blair.
blair.nicolle (AT) gmo (DOT) com


blair.nicolle (AT) gmo (DOT) com (Blair) wrote in message news:<be9c550c.0411021439.48a62e5 (AT) posting (DOT) google.com>...

True....luckily someone told me about this on an early stage....would be
nice if you were informed of this when saving child package in a new
version...that there is a link to another package and could choose to update
this link automatically without opening the father package.

"Blair" <bnicolle (AT) orbisfinancial (DOT) com> wrote