I have a fairly complex SSIS package, organized into stages. A primary package calls 4 secondary packages, each of which then in turns calls a large number of tertiary packages. The package has worked in a developer environment, but when deployed for user testing the package is failing in an odd way.
From the console logging, you can see the primary package validate, then execute the first secondary package. The secondary package validates, then executes the first tertiary package - the first package with an actual data flow. The tertiary package validates, and then executes to completion (all data is put in place correctly) and without error. But, the secondary package then reports that the execution of the tertiary package failed, and since this is an error and it is not supposed to ignore any errors, it aborts as failed as well.
There is absolutely nothing in the logs that suggests an error. What could be causing the parent package to believe that the child package had an error, when the child package correctly executed and did not log an error?
Any advice at all would be greatly appreciated?