TransactionScope authentication / poorly documented!

Question

Ahhhhh Microsoft, the most important feature in 2.0 “Transactions” is poorly documented, and almost working, as it looks like the people who developed it got it to work under one scenario, and released it immediately, never tested completely.

It is like, hey, does windows xp connected to a windows 2003 DTC when bother are under the domain controller, and when we modify the settings to the DTC and remove the security? Yes , Ok, releaseeeeee

Does it run in other scenarios? Hmmm, maybe :-)

Ok, here is the problem

1- I am developing under a virtual machine, outside the domain controller. (Win2003).
2- My SQL server is under the domain controller. (Win2003).
3- I am using the SQL server authentication; it works fine if the transaction scope is not used.

But I cannot connect to the same SQL Server if the transaction scope is enabled.

Does it have something similar to the SQL Server authentication, when we can tell that transaction scope, hey, this is how to authenticate?

Answer 1

If your client machine is not part of the Windows domain, you will need to turn off the mutual auth. of the two MSDTC involved in the transaction. See http://blogs.msdn.com/florinlazar/archive/2004/06/18/159127.aspx for more info.

Answer 2

It is very helpful

 

Can you Please add it to the Service Pack 1 documentation fix of .NET :-) so the people after us will suffer less :-)

 

Thanks a lot