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

by

Troubleshooting Guide: Error 3972 — Incorrect TDS Protocol / Transaction Manager Event Length Mismatch

Why This Error Happens

Error 3972 occurs when the SQL Server Transaction Manager receives a Tabular Data Stream (TDS) packet whose declared event length does not match the actual byte length received, indicating protocol-level data corruption. This is typically caused by network-layer interference (such as a misconfigured firewall, proxy, or load balancer fragmenting packets), a mismatched or outdated network driver, or corrupted TDS packets resulting from an unstable connection between the client and the SQL Server instance. It can also surface after incomplete patching of SQL Server 2025 or when MS DTC (Distributed Transaction Coordinator) communication is interrupted mid-transaction.

Step-by-Step Resolution Guide

Step 1: Verify Network Integrity Between Client and Server

  • Run ping -t <ServerName> and tracert <ServerName> to check for packet loss or latency spikes during the error window.
  • Disable TCP Chimney Offload and TCP/IP Checksum Offload on the NIC, as these features are known to corrupt TDS packets on Windows Server 2025:
    Disable-NetAdapterChecksumOffload -Name "*" -TcpIPv4
  • Check Event Viewer under Applications and Services Logs > Microsoft > Windows > TCPIP for dropped packet warnings.

Step 2: Validate MS DTC Configuration

  • Open Component Services (comexp.msc) and navigate to Component Services > Computers > My Computer > Distributed Transaction Coordinator > Local DTC.
  • Right-click Local DTC, select Properties, and ensure Network DTC Access is enabled with both Allow Inbound and Allow Outbound checked.
  • Restart the MSDTC service:
    Restart-Service MSDTC -Force
  • Confirm the same DTC security settings are mirrored on both the application server and the SQL Server 2025 host.

Step 3: Update Network Drivers and SQL Native Client

  • Update the NIC driver via Device Manager (devmgmt.msc) or directly from the hardware vendor’s site (Intel/Broadcom/Mellanox drivers are common culprits).
  • Ensure the client application is using the latest Microsoft OLE DB Driver or ODBC Driver compatible with SQL Server 2025 (avoid legacy SQL Native Client 11.0 if still in use).
  • Apply the latest Cumulative Update (CU) for SQL Server 2025 from the Microsoft Update Catalog, as TDS parsing fixes are frequently shipped in CUs.

Step 4: Inspect and Reset the TCP/IP Stack

  • If the issue persists only on the Windows Server 2025 host, reset the TCP/IP stack to rule out stack-level corruption:
    netsh int ip reset
    netsh winsock reset
  • Reboot the server after running these commands, as a soft restart will not fully apply the reset.

Alternative or Verification Steps

  • To verify the fix, run a distributed transaction test query (e.g., BEGIN DISTRIBUTED TRANSACTION) from the client and confirm it commits without triggering Error 3972 in the SQL Server Error Log.
  • If the error persists after all steps, capture a network trace using Wireshark or Microsoft Network Monitor filtered on port 1433 to identify the exact packet where length mismatch occurs, then escalate to Microsoft Support with the trace file and PSSDIAG output.