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

by

Troubleshooting Guide: Error 4010 – Incorrect TDS Protocol Stream (Query Notification Header)

Why This Error Happens

This error occurs when the Query Notification request sent to SQL Server contains a malformed TDS header, typically caused by an outdated or mismatched SQL Server Native Client driver on the client application. It can also result from network packet corruption introduced by a misconfigured proxy, firewall, or load balancer sitting between the client and the SQL Server 2025 instance. In some cases, custom applications manually constructing TDS notification requests (via SqlDependency or Service Broker) send improperly formatted message bodies, triggering this validation failure on the server side.

Step-by-Step Resolution Guide

Step 1: Verify and Update Client Drivers

  • Confirm the application is using the latest Microsoft OLE DB Driver or ODBC Driver compatible with SQL Server 2025.
  • On Windows 11 / Windows Server 2025, check installed driver versions via Control Panel > Programs and Features.
  • Update outdated drivers using the official Microsoft Download Center package for “Microsoft ODBC Driver for SQL Server.”
  • Restart the application pool or service after updating to ensure the new driver binaries are loaded.

Step 2: Inspect Service Broker and Query Notification Configuration

  • Open SQL Server Management Studio (SSMS) and connect to the instance.
  • Run the following to confirm Service Broker is enabled on the target database:
  SELECT is_broker_enabled FROM sys.databases WHERE name = 'YourDatabaseName';
  • If disabled, enable it with:
  ALTER DATABASE YourDatabaseName SET ENABLE_BROKER;
  • Validate that the SqlDependency.Start() call in application code is not being invoked multiple times with conflicting connection strings, as this can corrupt the notification queue.

Step 3: Capture and Analyze the TDS Stream

  • Use SQL Server Profiler or Extended Events to capture the raw TDS traffic at the time the error occurs.
  • Filter for Error 4010 events and inspect the packet payload for truncation or unexpected byte sequences.
  • Cross-reference the capture timestamp with any network hardware (firewall, load balancer) logs to rule out mid-stream packet tampering.

Step 4: Check for Network Layer Interference

  • On Windows Server 2025, open Windows Defender Firewall with Advanced Security and confirm no rules are fragmenting or inspecting TCP port 1433 traffic deeply.
  • Disable any third-party antivirus or deep packet inspection (DPI) proxy temporarily to test if the error persists.
  • If using a load balancer, ensure it is configured for raw TCP pass-through rather than TDS-aware inspection, since SQL Server 2025 TDS packets can be rejected if re-encapsulated incorrectly.

Step 5: Reinstall or Repair SQL Server Native Client Components

  • Navigate to Settings > Apps > Installed Apps on Windows 11, search for “SQL Server Native Client.”
  • Select Repair, or uninstall and reinstall using the latest setup package from Microsoft.
  • Re-test the Query Notification subscription after the repair completes.

Alternative or Verification Steps

  • Re-run the application’s notification subscription logic and confirm no Error 4010 entries appear in the SQL Server Error Log (Management > SQL Server Logs in SSMS) over a 24-hour monitoring window.
  • If the issue persists after driver updates, bypass Query Notifications temporarily by switching to a polling-based data refresh mechanism to isolate whether the root cause is TDS-specific or application logic-specific.