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

by

Troubleshooting Guide: SQL Server Error 11279 – Corrupted Message in Service Broker Conversation

Why This Error Happens

Error 11279 occurs when Service Broker receives a message where the message type field is populated, but the protocol expects it to be unset for that particular message exchange. This typically happens due to network-level packet corruption, a mismatched or outdated Service Broker endpoint configuration, or interference from a middle-box (such as a proxy, load balancer, or firewall) that alters TCP packet payloads in transit. It can also arise from version mismatches between communicating SQL Server instances when one side sends a message formatted for a different Service Broker protocol revision.

Step-by-Step Resolution Guide

Step 1: Verify Service Broker Endpoint and Network Path

  • Check the Service Broker endpoint configuration using SELECT * FROM sys.service_broker_endpoints;
  • Confirm the TCP port (default 4022) is not being intercepted or modified by any network appliance, VPN, or NAT device.
  • Test raw connectivity with Test-NetConnection -ComputerName <RemoteServer> -Port 4022 on Windows Server 2025 / Windows 11.

Step 2: Inspect and Clean the Conversation Queue

  • Identify the problematic conversation using the Conversation ID from the error message:
  • SELECT * FROM sys.conversation_endpoints WHERE conversation_id = '<GUID-from-error>';
  • If the conversation is stuck or corrupted, end it manually:
  • END CONVERSATION '<GUID-from-error>' WITH CLEANUP;
  • Check the associated queue for poison messages using SELECT * FROM sys.transmission_queue;

Step 3: Rebuild the Service Broker Configuration

  • Disable and re-enable Service Broker on the affected database to reset internal message handlers:
  • ALTER DATABASE [YourDB] SET DISABLE_BROKER;
  • ALTER DATABASE [YourDB] SET ENABLE_BROKER;
  • Verify the Service Broker GUID is unique and not duplicated across restored databases:
  • SELECT is_broker_enabled, service_broker_guid FROM sys.databases WHERE name = 'YourDB';

Step 4: Update SQL Server Cumulative Updates

  • Navigate to Microsoft Update Catalog or use SQL Server Setup to confirm you are on the latest Cumulative Update (CU) for SQL Server 2025.
  • Apply the update via C:\SQLServer2025\Setup.exe in silent update mode if patching multiple nodes:
  • Setup.exe /Action=Patch /IAcceptSQLServerLicenseTerms /Quiet
  • This resolves known protocol-parsing bugs that can trigger false-positive corruption detection.

Step 5: Review Firewall and Antivirus Packet Inspection

  • Open Windows Defender Firewall with Advanced Security and check inbound/outbound rules for port 4022.
  • Temporarily disable deep packet inspection (DPI) features in third-party antivirus or endpoint protection tools to rule out payload tampering.
  • Re-test the conversation flow after adjusting these settings.

Alternative or Verification Steps

  • To verify the fix, initiate a fresh Service Broker conversation between the two endpoints and monitor sys.transmission_queue and the SQL Server Error Log for recurrence of Error 11279.
  • If the issue persists, capture a network trace (via netsh trace start capture=yes on Windows Server 2025) during message transmission and compare packet payloads against the expected Service Broker message format to isolate corruption at the network layer.