How to fix Error 3431 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 3431 – Database Recovery Failure Due to Unresolved MS DTC Transactions

Why This Error Happens

This error occurs when SQL Server attempts to recover a database during startup but finds one or more transactions that were prepared under MS DTC and never received a final commit or rollback instruction. This typically happens because the MS DTC service was stopped, uninstalled, or its transaction log was corrupted/reset while distributed transactions were still in-flight. Without access to the original DTC transaction manager state, SQL Server cannot determine whether to commit or roll back the prepared transaction, so it halts database recovery to prevent data inconsistency.

Step-by-Step Resolution Guide

Step 1: Verify MS DTC Service Status

  • Open Services.msc on the affected Windows Server 2025 / Windows 11 machine.
  • Confirm Distributed Transaction Coordinator is set to “Running” and Startup Type is “Automatic.”
  • If stopped, start it manually: net start msdtc
  • Check Event Viewer under Applications and Services Logs > Microsoft > Windows > MSDTC for related failures.

Step 2: Identify the In-Doubt Transaction

  • Open SQL Server Management Studio (SSMS) and run:
SELECT * FROM sys.dm_tran_database_transactions WHERE database_id = DB_ID('YourDBName');
  • Alternatively, check for orphaned transactions using:
EXEC sp_configure 'in-doubt transaction';
  • Note the Transaction UOW (Unit of Work) ID returned by DTC, found via msdtc Component Services snap-in under Transaction List.

Step 3: Manually Resolve the Transaction

  • Open Component Services (dcomcnfg.exe), navigate to Distributed Transaction Coordinator > Local DTC > Transaction List.
  • Locate the transaction matching the UOW ID from Step 2.
  • Right-click and choose Commit or Abort depending on business logic (if unsure, Abort is safer to prevent partial writes).
  • If the transaction doesn’t appear in the DTC list (orphaned reference), force resolution in SQL Server:
KILL '<transaction UOW GUID>' WITH ROLLBACK IMMEDIATE;

Step 4: Rebuild or Reset MS DTC (If Corrupted)

  • If MSDTC logs are corrupted, reset the DTC configuration:
msdtc -uninstall
msdtc -install
net start msdtc
  • Restart the SQL Server service afterward to re-attempt database recovery:
net stop MSSQLSERVER
net start MSSQLSERVER

Step 5: Bring the Database Back Online

  • Once the in-doubt transaction is resolved, attempt to bring the database online:
ALTER DATABASE YourDBName SET ONLINE;
  • Monitor the SQL Server Error Log (Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) to confirm successful recovery.

Alternative or Verification Steps

  • Run DBCC CHECKDB('YourDBName') after bringing the database online to confirm no structural corruption resulted from the forced rollback.
  • If the database still fails to recover, restore from the last known good backup and manually reapply transactions logged outside the DTC scope to avoid repeated in-doubt transaction errors.