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

by

Why This Error Happens

Error 6114 occurs when SQL Server receives a KILL request for a distributed transaction’s Unit of Work (UOW), but the Microsoft Distributed Transaction Coordinator (MSDTC) reports that another session or resource manager still owns that UOW, or the transaction has already transitioned into an in-doubt/prepared state that cannot be interrupted by a standard KILL. Common root causes include:

  • A client application or linked server session still holding the enlistment open
  • MSDTC service communication failure or restart between the time the transaction was created and the KILL was issued
  • An orphaned or in-doubt transaction left behind after a network interruption between SQL Server and the distributed transaction coordinator
  • Insufficient permissions on the MSDTC service account to manage the transaction manager

These causes must be confirmed against the SQL Server error log and MSDTC transaction list before taking corrective action.

Step-by-Step Resolution Guide

Step 1: Identify the Owning Session and UOW

  • Open a new query window in SQL Server Management Studio (SSMS) connected to the affected instance.
  • Run the following to map the UOW to an active session:
SELECT da.transaction_id, da.name, da.transaction_uow, st.session_id, es.status, es.login_name
FROM sys.dm_tran_active_transactions AS da
JOIN sys.dm_tran_session_transactions AS st ON da.transaction_id = st.transaction_id
JOIN sys.dm_exec_sessions AS es ON st.session_id = es.session_id
WHERE da.transaction_uow = 'PASTE-UOW-GUID-HERE';
  • Record the session_id returned; this is the session SQL Server believes owns the transaction.

Step 2: Check the Transaction State

  • Run DBCC OPENTRAN('YourDatabaseName'); to confirm whether the oldest active transaction matches the UOW and whether it is marked as distributed.
  • If the transaction shows as “in-doubt,” it means MSDTC has lost contact with one of the resource managers and the transaction cannot be resolved by a normal KILL.

Step 3: Verify MSDTC Service and Permission Context

  • Confirm the Distributed Transaction Coordinator service is running:
Get-Service MSDTC
  • If stopped, start it with:
Start-Service MSDTC
  • Open the Component Services console to inspect the transaction manager directly: run comexp.msc, then navigate to Component Services > Computers > My Computer > Distributed Transaction Coordinator > Local DTC > Transaction List.
  • Confirm the MSDTC service account (default is NT AUTHORITY\NetworkService) has not been changed and has the required local security rights; record the account shown on the Log On tab of the MSDTC service properties in services.msc.

Step 4: Review the SQL Server Error Log

  • Open the current error log at:
C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG

(adjust the instance folder name MSSQL17.MSSQLSERVER if the instance was installed with a named, non-default instance ID)

  • Alternatively, query the log directly from SSMS:
EXEC sys.xp_readerrorlog 0, 1, N'UOW';
  • Look for entries referencing the same UOW GUID, MSDTC communication failures, or enlistment errors occurring around the same timestamp as the 6114 error.

Step 5: Resolve the Stalled Transaction

  • If the owning session from Step 1 is confirmed safe to terminate, retry the kill using the exact UOW string, quoted as required by SQL Server:
KILL 'PASTE-UOW-GUID-HERE';
  • To check kill progress without re-issuing it:
KILL 'PASTE-UOW-GUID-HERE' WITH STATUSONLY;
  • If the KILL still fails because MSDTC shows the transaction as in-doubt, abort it directly from the Component Services console (Local DTC > Transaction List, right-click the transaction, select Abort).
  • If the transaction still does not clear, restart the MSDTC service as a last resort:
Restart-Service MSDTC -Force
  • Only restart the SQL Server service itself if the UOW persists after the MSDTC restart, since this will drop all other active connections.

Alternative or Verification Steps

  • Verify the fix: Re-run the query from Step 1 and DBCC OPENTRAN to confirm the UOW no longer appears in sys.dm_tran_active_transactions, then retry the original distributed operation and confirm Error 6114 does not recur.
  • Alternative if the primary steps fail: Collect the UOW GUID, the full error log excerpt from Step 4, the MSDTC Transaction List screenshot, and the service account details, then escalate to your DBA team or open a case with Microsoft Support referencing Error 6114 and the MSDTC transaction manager state.