Hi,

We have a fairly complicated set of DTS packages which are run nightly to
perform our ETL process for our reporting environment. In most cases, the
process runs successfully. However, occasionally, the parent package will
trigger multiple instances of one of the packages and we will get a deadlock
or unhandled exception because the package is tripping on itself. The
structure of the package is as below. Each of the packages and subpackages
are run sequentially and has logging and error checking between each.

Package 0
Package 1.00
Package 1.10
Package 1.20
Package 1.30
Etc..
Package 2.00
Package 2.10
Package 2.20
Package 2.30
Etc...
Etc...

Does anyone have an idea why DTS would kick off multiple instances of the
package and how to prevent it?

Thank you.