Hi All, Problem : We have a EXECUTE PACKAGE TASK in sequence in which say P1 is the master package, P1 invokes P2 and in turn P2 invokes P3(P1->P2->P3). In P3 there is a simple data flow task which has a straight forward SELECT statement as source and an oledb destination. When ever the P1 is executed, there is a problem in P3 dataflow task like the source spools 650 rows, the same is never inserted in the destination. The oledb destination remains yellow like forever. When we investigated we found that there is one UNIQUEIDENTIFIER column in the destination which is also NOT NULL field, but the corresponding column in the source coming as NULL. So the task should fail with proper message in execution result tab. But as I mentioned the task is neither failing nor completing at all. Then we tried to execute P3 individually but this time the package failed(as the data flow failed) with proper error message(as the case always should be). The only issue is that when the P1 is executed the P3 and as well as the data flow task in P3 remains yellow and P1 execution never ends. Please SOS....

Wait a minute. When you execute P1, how are you seeing the P3 Data Flow task to know it "turns yellow"? It should be running it hidden from the user. If I understand correctly, P1 has an Execute Package task that calls P2. P2 also has an Execute Package Task that calls P3. P3 has a Data Flow task that is hanging. Correct?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.