SSIS: work package crashes after migrating to SQL Server 2012

I have an SSIS package that works fine on SQL2008R2 using environment variables pointing to a configuration file for connection strings. Using VS2010 Shell, I updated the package for our SQL Server 2012 database. The package is still in the package deployment model. The ProtectionLevel parameter of the package is set to DontSaveSensitive. Run64BitRuntime = False. When I try to execute a package in VS, I get the following errors:

[OLE DB Destination [2]] Error: SSIS error code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call for the DB_Connection connection manager ended with error code 0xC0202009. Before this, error messages may appear with additional information about why the AcquireConnection method call failed. **

[SSIS.Pipeline] Error: In the OLE DB Destination, the pre-execution phase failed and error code 0xC020801C was returned. **

With full login, I see the first crash here:

Diagnostics, [ComputerName], OFFICE \ username, DB_Connection, {5AD75239-D546-4AAF-963E-E195FC2F0C1E}, {9EC48106-DDBD-40E9-8FBB-942BCF025EEE}, 3/26/2013 10:35:21 AM 26/2013 10:35:21 AM, 0, (null), ExternalRequest_post: "ITransactionJoin :: JoinTransaction failed". External request completed. **

, , , "DB_Connection" " SQL". , , .

\ . , DTC , . , SQL2012 , .

, , , . , .

+5
1

. TransactionOption , , , , . , SQL2008R2, SQL2012. , .

+6

All Articles