Hi, I have a package which calls a child package. The child package has some error handling. In the error handling I have a max error count of 100 and failparent to false. When I run my child package on its own I get at the end a Success result as I have up to 100 errors flexibility. The problem is in the parent, the call package step fails, which then triggers a failure. Of course I can change the parent step to have the same error flexibility, but then the parent is the child of another package (3 layers) and I don't want to fudge my process. There could be similar situations in other places so looking for the real cause. Does anyone know what's the recommended way? I am running 2008 R2 (no SP yet). I also found this article but doesn't say where is fixed. Thank you. http://connect.microsoft.com/SQLServer/feedback/details/381681/ssis100-failparentonfailure-failpackageonfailure-are-erroneously-regarded-to-be-always-true Panos

This may be relevant: http://www.bimonkey.com/2009/08/preventing-sql-agent-jobs-calling-ssis-reporting-failure/ Cheers, JamesJames Beresford @ www.bimonkey.com SSIS / MSBI Consultant in Sydney, Australia SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex

This may be relevant: http://www.bimonkey.com/2009/08/preventing-sql-agent-jobs-calling-ssis-reporting-failure/ Cheers, JamesJames Beresford @ www.bimonkey.com SSIS / MSBI Consultant in Sydney, Australia SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex

Hi Panlodon: Up to todate, there is no solution for this: Created a suggestion on connect here. https://connect.microsoft.com/SQLServer/feedback/details/762038/create-the-propagateerrortoclient-property-to-handle-errors-in-parent-child-scenariosAlejandro Leguizamo