SSIS Parent Package Configuration Fails
If you have several parent configurations setup and one fails to find the variable in the parent, gives a warning, and then does NOT load the rest of the parent configruations. I realize order matters in how your configurations are processed, but I wouldn't expect the rest of my configurations to not work simply because it could not find one parent variable.
The problem only seems to come up when I'm dealing with multiple parent configurations. If I'm loading a variable from a config file and then loading the same variable from a parent variable the process works fine. This way I can handle both cases, when I'm debugging it pulls from the config file, when it's running in production it pulls from the parent variable.
Upvotes: 0<=-=Oct 12 2006 2:05PM=-=>
Thanks for reporting this issue, unfortunately we are not able to implement your suggestions (or fixes) in the Yukon timeframe; however we have considered this feedback useful enough that we have either:
1) Closed this bug as a duplicate of a (similar) parent tracking item in the next verison of our product, Katmai
2) Moved this bug into Katmai as a parent tracking-item and grouped other similar bugs underneath it.
Either way, we are listening to your ideas and considering them for the next version. In some circumstances we have actually made a few changes in SP2 to address some of these issues too.<=-=Oct 12 2006 2:08PM=-=>
Sorry – this bug was actually moved to SP3, not Katmai<=-=May 29 2007 9:52AM=-=>
Thank you for reporting this issue. It has been resolved for the Katmai release.