Configuring MSDTC is key in multi server BizTalk server environment configuration. Typically the following procedure should be followed in all BizTalk servers in a multi server environment. When you are installing BizTalk360 on a stand-alone (separate) server, you need to follow the exact procedures, since the underlying admin API's will rely on MSDTC.


To enable MSDTC on Windows Server 2008 and above:

  1. Click Start, click Run, type dcomcnfg and then click OK to open Component Services
  2. In the console tree, click to expand Component Services, click to expand Computers, click to expand My Computer, and click to expand Distributed Transaction Coordinator
  3. Right click Local DTC, and click Properties to display the Local DTC Properties dialog box. 
  4. Click the Security tab. 
  5. In the Security Settings section, click Network DTC Access
  6. In the Client and Administration section, select Allow Remote Clients and Allow Remote Administration
  7. In the Transaction Manager Communication section, select Allow Inbound and Allow Outbound
  8. In the Transaction Manager Communication section, select Mutual Authentication Required (if all remote machines are running Windows Server 2003 SP1 or Windows XP SP2 or higher), select Incoming Caller Authentication Required (if running MSDTC in a cluster), or select No Authentication Required if some of the remote machines are pre-Windows Server 2003 SP1 or pre-Windows XP SP2. No Authentication Required is the recommended selection. 
  9. Select Enable XA Transactions, and then click OK


If the MSDTC is configured correctly, there is a chance that the firewall is blocking the transactions. You can try using the DTC Tester tool: https://support.microsoft.com/en-us/kb/293799 and DTCPing Tool https://www.microsoft.com/en-gb/download/details.aspx?id=2868