The package I've been working on just hangs now without any errors in the execute process window or the application event log; running by either right clicking the master package and using "execute package" as well as double clicking on the master file and executing from the execute package utility. It just hangs, no red boxes just yellow and green ones if they change at all, no errors logged anywhere that I've found.
It has a three level hierarchy: master calls four (with more to come) packages each in a sequence container to use DTC, without any precedences for max. parallel execution, those four use another four packages which encapsulate repeated tasks writing to or updating common related tables. All packages use the same two DB connection managers for the local source and target databases.
The original all TSQL version of the same imports using a master and child sprocs ran without any deadlocks or hanging.
Because it's in SSIS now I thought it might be a new deadlock issue and have found checking deadlocks is a lot more complicated in SQL 2005 (having to export a deadlock grid xml from profiler and all that poop) but the xml file is empty and no deadlock events are being captured at all from what I can tell.
Anyone else get stuck in this corner? I searched here but didn't find anything hope this is not a re-post. Thanks all, this forum is a live saver!
Skål - jh