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.

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).

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.

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.

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

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:

You monitor the performance counter instance for the Distributed Transaction Coordinator performance object. This performance object provides information about the clustered MSDTC resource.

When you enable trace flag (TF) 3924 to clean orphaned Distributed Transaction Coordinator (DTC) transactions in sqlmin!XactMgr::CleanOrphanedXacts, you may notice that an access violation (AV) occurs. Additionally, you may receive a series of dump files.

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 ...

This article describes a conflict between Microsoft SQL Server and Microsoft Distributed Transaction Coordinator service (MSDTC) in Windows Server 2012 R2. A hotfix is available to fix this issue. The hotfix has a prerequisite.