Overview
There is sometimes an issue on the BizTalk Server, often following an operation such as an operating systems service pack installation, where the MSDTC settings can be reset from those that BizTalk requires to work.
MSDTC - Microsoft Distributed Transaction Coordinator - is a transaction manager which permits client applications to include several different sources of data in one transaction and which then coordinates committing the distributed transaction across all the servers that are enlisted in the transaction. MSDTC runs on all Windows platforms and is installed by applications which need to use it, such as the Microsoft"s Personal Web Server, or Microsoft SQL Server.
Most BizTalk Server runtime operations require MSDTC support to ensure that the operations are transactionally consistent. If MSDTC transaction support is not available, then the associated BizTalk Server runtime operations cannot proceed. The components of BizTalk that are commonly affected when MSDTC transaction support is not configured correctly include (but are not limited to) the Single Sign-On Service, BizTalk host instances, and any SQL Server instances that are connected to by BizTalk Server.
Errors
Errors similar to the following may occur on BizTalk Server when MSDTC transaction support is not configured correctly on the computers in a BizTalk environment:
"A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. The transaction manager has disabled its support for remote/network transactions".
"A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. The transaction has already been implicitly or explicitly committed or aborted".
"Error Code: 0x8004d00a, New transaction cannot enlist in the specified transaction coordinator".
"Could not retrieve transport type data for Receive Location 'MySample ReceiveLocation' from config store. Primary SSO Server 'MyServer' failed. The RPC server is unavailable".
"Error Code: 0x8004d025, The partner transaction manager has disabled its support for remote/network transactions".
"Error Code: 0xc0002a24, Could not import a DTC transaction. Please check that MSDTC is configured correctly for remote operation".
"0x8004d01c [0x1705] There was a failure creating the internal work item. Make sure that SQL Server is running."
Enabling MSDTC
If you think that you are suffering from a case of reset MSDTC settings follow these steps:
- Open Component Services from within Administrative Tools
- In the left pane of Component Services:
- expand Component Services
- expand Computers
- right-click My Computer and select Properties
- In the Properties dialog box:
- select the MSDTC tab
- in the Transaction Configuration section click Security Configuration
- In the Security Configuration dialog box:
- enable Network DTC Access, Allow Remote Clients, and Allow Remote Administration
- enable Allow Inbound and Allow Outbound
- select No Authentication Required.
- Click Enable XA Transactions.
- Click OK.
- In the Properties dialog box click OK
Links
How to Enable MSDTC on the BizTalk Server
Troubleshooting Problems with MSDTC