Distributed transaction problem

I'm having problems with distributed transactions. I know this has been descussed a lot before, but i haven't been able to solve my problems anyway.

So, what do I try to do? I try to recieve data from one server (source) to a destination server with an integration services package using a transaction. The source server is a Windows 2003 server running SQL 2000. The destination server is a SQL 2005 Cluster on Windows 2003 Server. Both machines has MSDTC running and allowing both inbound and outbound transactions. I have run DTCPing and DTCTester successfully in both directions.

A bit simplified, my SSIS package looks like this.

Execute SQL Task (Delete old data on the destination server)

Data Flow Task

Get data from source using an OLE DB Source

Write data to destination using an OLE DB Destination

This works just fine if I in my topmost container set TransactionOption to supported, but if I change it into Required, my package fails with the error message:

Error: The SSIS Runtime has failed to start the distributed transaction due to error 0x8004D01B "The Transaction Manager is not available.". The DTC transaction failed to start. This could occur because the MSDTC Service is not running.

Could the fact that the destination is a cluster be a prolem here? I'm pretty sure I have successfully done operations like this in other environments, but without clusters involved.

Oh, one last thing. No firewall what so ever is runnig on or between the servers.

regards Andreas

Does anyone have any ida before I use one of our support cases and call Microsoft support?|||

It seems as tho DTC is creating the problem. I don't know much about configuring that but I'm sure Google can help. Here's some links that may also help:

http://blogs.conchango.com/paulmcmillan/archive/2005/10/17/2277.aspx

http://blogs.msdn.com/florinlazar/archive/2005/09/16/469064.aspx

-Jamie

|||

What?!?!?

I was doing one last test to confirm the problem once more before reporting a case to MS and..... woala... now it worked. I can't remember changing anything since last time, but what the heck... Let's cross our fingers and hope the problem stays away! =)