Microsoft Distributed Transaction Coordinator (MSDTC) fails to auto-start. If you run “sc query msdtc” to see the status of MSDTC, the command returns the following output: STATE equals “1 STOPPED” . Cause.

SQL Server could not register with Microsoft Distributed Transaction Coordinator (MS DTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager.

The Microsoft Distributed Transaction Coordinator (MSDTC) service may stop unexpectedly on a computer that is running Windows Server 2012 or Windows Server 2008 R2 Service Pack 1 (SP1).

Symptoms. Assume that you use distributed transactions in Microsoft SQL Server together with MS DTC (Distributed Transaction Coordinator). You may sometimes notice lower throughput and long wait times for the DTC_STATE wait type if there are many concurrent distributed transactions.

Assume that you use Distributed Transaction Coordinator (DTC) transactions in SQL Server 2019 with Tempdb Memory-Optimized Metadata mode enabled. In some scenarios, DTC transactions involving tempdb metadata-related operations could fail internally, with an error related to transactions on memory-optimized tables not being supported in DTC ...

Microsoft Distributed Transaction Coordinator (MSDTC) is enabled in SQL Server 2017. Resolution. This improvement is included in the following cumulative update for SQL Server: Cumulative Update 16 for SQL Server 2017. About cumulative updates for SQL Server:

You create a clustered Microsoft Distributed Transaction Coordinator (MSDTC) resource on a Windows Server 2008-based failover cluster. You add some performance objects in Performance Monitor.

When an MSDTC transaction runs on a computer that is running Windows 7 or Windows Server 2008 R2, the Distributed Transaction Coordinator service (Msdtc.exe) may crash if slow network performance occurs. Additionally, the following events are logged:

For example, Microsoft Distributed Transaction Coordinator (MS DTC) is involved to start distributed transactions together with SET XACT_ABORT ON if the TransactionOption package level property is set to Required. Cause. This issue occurs because of an error in SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014. Resolution.

Symptoms. Assume that your application initiates a cross-database transaction that updates multiple tables in different databases in a manner that requires communication with Microsoft Distributed Transaction Coordinator (MSDTC). In this scenario, you receive an "Expired BLOB handle" error.