IaaS servers cloned from a template where DTC was already installed contain duplicate identifiers for DTC, which prevents communication among the nodes.
The IaaS Manager Service fails and posts the following error to the manager service log.
Communication with the underlying transaction manager has failed. ---> System.Runtime.InteropServices.COMException: The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers.
When you clone an IaaS server that already has DTC installed, the clone contains the same unique identifier for DTC as the parent. Communication between the two machines fails.
- On the clone, open a command prompt as Administrator.
- Run the following command.
- Restart the clone.
- Open another command prompt, and run the following command.
msdtc -install manager-service-host-FQDN