Checkpoint & Distributed Transaction Error

• Brandie Tarvin

  SSC Guru

  Points: 173105

  More actions

  September 10, 2008 at 6:48 am

  #131183

  Using SP1 right now.

  SSIS package worked fine until I enabled Checkpoints on it. Now I'm getting the following output results:

  Information: 0x40016045 at MyPkgLoad: The package will be saving checkpoints to file "\\MyServer\CheckpointFiles\MyPkgLoad_ChkPt.xml" during execution. The package is configured to save checkpoints.

  Information: 0x4001100A at MyPkgLoad: Starting distributed transaction for this container.

  Error: 0xC001402C at MyPkgLoad, Connection manager "MyServer": The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction manager has disabled its support for remote/network transactions.".

  Error: 0xC0202009 at MyPkgLoad, Connection manager "MyServer": An OLE DB error has occurred. Error code: 0x8004D024.

  Error: 0xC00291EC at TruncateTables, Execute SQL Task: Failed to acquire connection "MyServer". Connection may not be configured correctly or you may not have the right permissions on this connection.

  What's weird is if I run Execute Task on the TruncateTables task, it functions fine. It's only if I try to debug the package now that it has checkpoints enabled that I have errors.

  Pkg properties are set as:

  CheckpointUsage - IfExists

  SaveCheckPoints - True

  CheckpointFileName - \\MyServer\CheckpointFiles\MyPkgLoad_ChkPt.xml

  I'm debugging locally from my desktop. I set all containers to FailPackageOnFailure - True.

  Any thoughts?

  Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

• Brandie Tarvin

  SSC Guru

  Points: 173105

  More actions

  September 12, 2008 at 12:32 pm

  #871263

  Oddly enough, I think this issue is a cluster problem.

  The cluster administrator says MSDTC is running on the cluster (on our V1 node), but my report server is on the V2 node, where MSDTC is NOT running locally (and can't be started locally, I tried). Which means I might only be able to use checkpoint files on SSIS packages that are attached to the V1 node.

  Anyone every heard of problems with MSDTC on an active/active/active/passive cluster? (4 servers, BTW).

  Thanks for those few who have read this thread. I appreciate the interest in the problem at least.

  Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.