InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 16:51:50 GMT20http://www.sqlservercentral.com/Forums/Topic1383658-391-1.aspxNot entirely but I feel less alone now! :-DThanksMon, 12 Nov 2012 07:59:28 GMTEric Mamethttp://www.sqlservercentral.com/Forums/Topic1383658-391-1.aspxI've seen this behaviour before, though it normally occured when the SSIS package files where copied and the GUID's didnt get reset.I think it had something to do with the way BIDS formed its stack, it was especially prevelant if one of the copied packages had been executed previously, it would then execute both packages, and if one completed first it would rase a completed back to the parent level even though the 'real' one was still running. I hope that made sense.Mon, 12 Nov 2012 07:53:39 GMTJason-299789http://www.sqlservercentral.com/Forums/Topic1383658-391-1.aspxInteresting...This only seems to affect the debugging via BIDS.When fired through SQL Server Agent or DEXECUI, it seems to behave as expected.Maybe by configuring my package on the fly in BIDS, I force the execution of the sub-package through an "out of process" execution, hence not synchronous?Oh well... Lets call this a SUCCESS then! :-PMon, 12 Nov 2012 07:48:10 GMTEric Mamethttp://www.sqlservercentral.com/Forums/Topic1383658-391-1.aspxI am slightly confused... Everything I read seems to indicate that executing a sub-package through the Execute Package Task is synchronous yet my parent package seems to behave the other way (asynchronous...).I have a "master" Package that has one control flow with a few Execute SQL Tasks followed by a few child packages that I was hoping would run sequentially before finishing my master package with a few more Execute SQL tasks.It looks like my master package runs through its "Execute SQL Tasks" as if the "Execute Package Tasks" did not exist... My last Execute SQL Task marks my "batch" (aka master package) as successful while a couple of the Execute Package Tasks are not yet started (see screenshot attached).Any idea why this might be?PS: I configure my child packages through a file connection modified at runtime via an expression (to point at the same folder as the parent package)Mon, 12 Nov 2012 06:23:19 GMTEric Mamet