You would need to completely remove the failed instance of MSDTC from the SQL Server group to use another instance of MSDTC.
Likewise, if you create a mapping for SQL Server and the mapped instance of MSDTC fails, your distributed transactions will also fail.
Note that MSDTC is not required for Analysis Services-only instances.
On Windows Server 2008 and Windows Server 2008 R2, you can install multiple instances of MSDTC on a single failover cluster.
Link Id=112287 This method for qualifying clusters introduced several challenges for hardware partners.
Since the entire end-to-end solution had to be qualified, including every component down to the driver and firmware level, if just one component changed after the certification process, the entire solution had to be retested and submitted, because it was then considered to be a different solution.
The sections below describe the requirements to keep in mind when installing a SQL Server multi-subnet failover cluster.
After you install the operating system and configure your cluster, you must configure MSDTC to work in a cluster by using the Cluster Administrator.Make sure that your operating system is installed properly and is designed to support failover clustering.The following table is a list of SQL Server editions and the operating systems that support them.*SQL Server clusters are not supported in WOW mode.Failure to cluster MSDTC will not block SQL Server Setup, but SQL Server application functionality may be affected if MSDTC is not properly configured.In Windows Server® 2008 and Windows Server 2008 R2, the way that clusters are qualified is changing significantly with the introduction of the cluster validation wizard.
One common scenario was for a customer to check the Windows Server Catalog Web site, purchase a listed solution and then after a few months, find that the manufacturer had released a host bus adapter (HBA) driver that was recommended for installation.