Exactly as explained in the article - transactions are controlled by the TransactionOption property. What problems are you experiencing?
-Jamie
Hi Jamie
Following scenarios we tried with TransactionOption :
Package= Required
SequenceContainer=Supported
All the 4 Tasks = Supported
The following is the error i am getting
[Slowly Changing Dimension [6136]] Error: The AcquireConnection method call to the connection manager "conApplnData" failed with error code 0xC0202009.
[DTS.Pipeline] Error: component "Slowly Changing Dimension" (6136) failed the pre-execute phase and returned error code 0xC020801C.
Note: "conApplnData" is the connection manager for database table. I am using Slowly Changing Dimension for the 4 different tasks to load data in to tables from same extract.
Thanks
Kumaran
That's nothing to do with transactionOption. I am guessing you will get that if you have transactions turned off - unless of course you are having trouble enlisting in MS DTC - but i expect it would tell you if that were the case.
-Jamie
Hi Jamie
After i got the above said error message,i am also getting this below error.
[Execute SQL Task] Error: Failed to acquire connection "conApplnData". Connection may not be configured correctly or you may not have the right permissions on this connection.
But i am not getting any error message related to MS DTC.
Could you please confirm me that the transaction properties i assigned is fine or should i need to change the transaction property in any of the component.
Thanks
Kumaran
Like i said before, have you tested it WITHOUT trying to run a transaction? I doubt this problem is related to transactions.
-Jamie
Hi Jamie
I executed the package with the default settings for the transactions option.
I.e for Package -- Supported , Container - Supported , Task - Supported.
The package is executed fine and executed each of the 4 tasks and loaded data in to 4 different tables without any issues.
Once i changed the default transactionsoption property only, i started getting errors.
Could you provide me more info.
Thanks
Kumaran
My best guess is that MS DTC isn't configured properly. You should try and configure that correctly. My colleague Paul Mcmillan has a useful blog post here. http://blogs.conchango.com/paulmcmillan/archive/2005/10/17/2277.aspx
-Jamie
Hi Jamie
As you said, i checked the MS DTC in services of the client machine.
The configuration seems to be OK and is as below:
Service Name: Distributed Transaction Coordinator
Status : Started
Start Up : Automatic
Log On As : NT AUTHORITY\NetworkService
Should i need to check the MS DTC in server machine too.
Please provide me some more info.
Thanks
Kumaran