Resolution. To fix this issue, install Cumulative Update for Windows 10 Version 1607 and Windows Server 2016: December 9, 2016 (KB3201845). Resolves a problem that occurs when you set up a new system in which the MSDTC service does not start after you apply an image and run Sysprep.

Symptoms. 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). Additionally, one of the following events is logged in the Application log: Cause.

You restart the Microsoft Distributed Transaction Coordinators (DTC) service. Assume that you execute Distributed Transaction in the AG enabled database. In this situation, you may notice that the transaction fails with errors that resemble the following: Msg 8510, Level 20, State 3, Line LineNumber.

Symptoms. Consider the following scenario: 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. You monitor the performance counter instance for the Distributed Transaction Coordinator performance object.

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: Cause. This issue occurs because MSDTC logs a warning.

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.

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. Note TF 3924 is introduced in KB 3145492 to clean up orphaned DTC transactions. Status.

You run Distributed Transaction Coordinator (DTC) transactions in Microsoft SQL Server 2017. A transaction is started, and SQL Server successfully prepares the transaction. A transaction commit request is sent to SQL Server. The database that is involved in the transaction is restarted.

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. Symptoms. Consider the following scenario: You're using SQL Server in combination with MSDTC.