I have a package with a container and three "execute SQL tasks" (SELECT 1, SELECT 2/0 and SELECT 3) in it. The middle task has SELECT 2/0 SQL and so this have to go wrong. Container: Transaction = required FailpackageOnFail= true Task: transaction = supported FailparentOnFailure = True I've a checkpoint configured. The behaviour without a eventhandler is that the whole container is executed again from Task SELECT 1 after a error is corrected. With the event handler ONError the container starts at task SELECT 2/0(without /0). I think i know the answer already but i want to confirm my thoughts by you. When i add an OnError handler in the package for logging the error, the behaviour of the container differs when i DON'T add the eventhandler. I want to log the error AND i want restartability of the container(start at task SELECT 1). After correcting the error the package is restarted as if there isn't a transaction on the container and i don't want that. I can imagine that it isn't logical to have a transaction on the error handling because logging the error will also be rolled back. This may be a functional question but SSIS is behaving differently with an event oand no event handling and therefore i conclude that there are also technical reasons?! Is there a way to have a transaction working on the container and a proper error handling with the event ONError? Thx Hennie

what did you set for CheckPointUsage ?http://www.rad.pasfu.com

checkpointfilename C:\tmp\bla.txt Cechpointusage Ifexists Savecheckpoints True

Anyone?