Common mistakes in WCF distributed development (15): Communication with the underlying transaction manager has failed.

The error occurs today when debugging WCF transactions locally: Communication with the stable Transaction Manager has failed.

I did a lot of research to find out why. It’s because of MSDTC. This protocol USES a distributed transaction coordinator. Or the transaction protocol.

Solutions:

Modify the transaction communication protocol.

1. & lt; bindings>

& lt; netTcpBinding >

& lt; The binding name = “netTcpBindingTcp transactionFlow” = “true” & gt;

& lt; ! –transactionProtocol=”WSAtomicTransactionOctober2004″–> // Local debugging does not apply to this transaction protocol

& lt; ! –< reliableSession enabled=”true” ordered=”true”/>

& lt; security mode=”None”> < /security> –>

& lt; /binding>

& lt; /netTcpBinding>

& lt; /bindings>

2. Check MS DTC Settings. [Control Panel -& GT; Performance and Maintenance -& GT; Management Tools -& GT; Component Services -& GT; Computer -& GT; My Computer -& GT; Properties -& GT; MS-DTC TAB -& GT; Security Configuration.

See article links:

1. http://social.msdn.microsoft.com/forums/en-us/windowstransactionsprogramming/thread/71f7a219-c85d-4a04-973b-c73464f59606;

2.http://msforums.ph/forums/t/38399.aspx

3.http://www.cnblogs.com/ThinkCode/archive/2008/10/14/1311021.html

This article from frankxulei 51 cto blog, the original link: http://blog.51cto.com/frankxulei/320435, if you want to reprint, please contact our author

Read More: