Can you try modifying your package and testing it in these configurations, which will tell us which part, or combinations of parts, are causing the problem:

1. Remove the ADO.Net Destination,...

I'm afraid that you can't force SSIS to release the cache file. It opens the connection, then maintains it (like any other Connection Manager) until the package completes execution.

You...

I'm not sure about that one - my initial thought would be to use a File System Task to delete the file before your Data Flow executes.

Is this 2008 server the same bitness as your 2005 servers?

If your 2008 server is 64-bit, the precompile option must be set ON for it to execute - see the...

Please provide some more details on your setup. List the name (or just refer to it as DEV) of your development machine, OS version/bitness, SQL version/bitness. Please do...

For anyone happening through this thread, these articles may be useful for you:

Conversion Between Unicode and Non-Unicode Data Flow Pattern

Convert Several Columns in SSIS With Fewer Clicks

Did you refresh your data source in the Data Flow? If you just changed the data type - no column name changes - then I don't think the source...

The problem is the default ProtectionLevel that packages get built with in BIDS - EncryptSensitiveWithUserKey. You can execute the package find in BIDS, because YOU are doing it, and...

I wouldn't recommend attempting to manually fix this issue - run through the SQL Installer and "repair" the installation.

Thanks for letting us know what you tried - but it would be nice to know what the errors were when you tried those things. Can you post them?

I'm afraid most of the posts in that thread refer to protectionlevel, not bitness. And most information posted on the internet about running packages as 32-bit on 64-bit architectures...

Unfortunately, the question didn't ask for the "best" answer - it asked "which statement is true". BOTH statements are true. I can prove that they are.

Saying "Tasks inside...

You should REALLY not be doing it that way. Win32 API is not the way to get this done - you should be using the included .Net Framework libraries...

Without seeing how you're adding that clause to the "end" of the statement, I can't say for certain - but I will say that you can't place parameters inside a...

If I were a betting man, I'd bet your server was 64 bit. Read up: SSIS in 32- and 64-bits. Hope that helps - if not, please post...