Network access for Distributed Transaction Manager (MSDTC) has been disabled
System.Transactions.TransactionManagerCommunicationException: Network access for Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for network access in the security configuration for MSDTC using the Component Services Administrative tool. —> System.Runtime.InteropServices.COMException (0×8004D024): The transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0×8004D024)
You can resolve this by following the steps below
Control Panel – Administrative Tools – Component Services – My Computer properties – MSDTC tab – Security Configuration tab – Network DTC Access (checked) / Allow Remote Clients (checked) / Allow Inbound (checked) / Allow Outbound (checked) / Enable TIP Transactions (checked)
REBOOT computer
March 26, 2009 at 10:41 am
I recently came across your blog and have been reading along. I thought I would leave my first comment. I don’t know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.
Joannah
http://2gbmemory.net
March 31, 2009 at 5:46 am
Please do not enable “TIP Transactions” — it is a very rarely used transaction protocol and enabling this will do nothing except open the attack area on the machine.
Likewise, enabling Remote Clients may also not be necessary depending on your needs.
Finally, a reboot should not be required for these settings to be put into affect. At most, a restart of services like MSDTC,SQL,MSMQ are all that’s required.
Some settings are discussed at length here: http://support.microsoft.com/?kbid=899191
Future questions can be directed to the Tx forum here: http://social.msdn.microsoft.com/forums/en-US/windowstransactionsprogramming/threads/
April 6, 2009 at 4:30 am
Great site this hspinfo.wordpress.com and I am really pleased to see you have what I am actually looking for here and this this post is exactly what I am interested in. I shall be pleased to become a regular visitor
April 11, 2009 at 12:28 pm
brill site this hspinfo.wordpress.com formidable to see you have what I am actually looking for here and this this post is exactly what I am interested in. I shall be pleased to become a regular visitor
May 21, 2009 at 11:20 pm
Пора переименовать блог, присвоив название связанное с доменами
может хватит про них?
September 5, 2009 at 2:30 am
My app and SQL server are on different machine. I quess I need to do this on SQL server machine as well. After that, I got following error:
System.Transactions.TransactionManagerCommunicationException: Communication with the underlying transaction manager has failed. —> System.Runtime.InteropServices.COMException (0×80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.
at System.Transactions.Oletx.IDtcProxyShimFactory.ReceiveTransaction(UInt32 propgationTokenSize, Byte[] propgationToken, IntPtr managedIdentifier, Guid& transactionIdentifier, OletxTransactionIsolationLevel& isolationLevel, ITransactionShim& transactionShim)
at System.Transactions.TransactionInterop.GetOletxTransactionFromTransmitterPropigationToken(Byte[] propagationToken)
For information, my SQL Server is on a Window 2008 server. And Distributed Transaction Coordinator service is running on both machine.
Any advice?
November 13, 2009 at 7:38 am
Thanks dude, i am able to fix this.
November 14, 2009 at 3:24 am
[...] then you have to do as it says and enable network access in the DTC on the server where the WCF service is hosted (and also on the database server I woul assume, but I haven't actually checked). Here's an instruction on how to do that: Network access for Distributed Transaction Manager (MSDTC) has been disabled [...]
December 16, 2009 at 2:55 pm
Woo it worked can but someone make me understand how it works and what is the use of it.