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

by

Troubleshooting Guide: SQL Server Error 11273 – Corrupted Message Padding in Service Broker

Why This Error Happens

This error occurs when Service Broker encounters a message whose encrypted body fails to conform to the expected padding standard, typically indicating data corruption during transmission or storage. This can result from network-level packet corruption, a mismatched or outdated Service Broker certificate used for dialog encryption, or inconsistencies introduced by antivirus/firewall software intercepting TDS packets between endpoints. In rarer cases, it stems from a damaged transmission queue or msdb database corruption affecting the conversation’s cryptographic context.

Step-by-Step Resolution Guide

Step 1: Identify the Affected Conversation and Isolate the Queue

  • Run the following query to locate the problematic conversation using the Conversation ID from the error message:
  • SELECT * FROM sys.conversation_endpoints WHERE conversation_id = '<GUID-from-error>';
  • Check the transmission_status column for additional clues tied to the corrupted message.
  • Temporarily disable the queue to prevent further processing attempts: ALTER QUEUE [YourQueueName] WITH STATUS = OFF;

Step 2: Validate Service Broker Certificates and Encryption Keys

  • Verify certificates used for the dialog are not expired or mismatched between initiator and target databases:
  • SELECT * FROM sys.certificates WHERE name LIKE '%ServiceBroker%';
  • Re-issue or re-import the certificate pair if expiration or a checksum mismatch is found.
  • Ensure the master key is open and accessible: OPEN MASTER KEY DECRYPTION BY PASSWORD = 'YourStrongPassword';

Step 3: Clear Corrupted Messages from the Transmission Queue

  • Identify stuck or malformed messages sitting in the sys.transmission_queue system view.
  • SELECT * FROM sys.transmission_queue WHERE conversation_handle = '<Handle-ID>';
  • If the message is unrecoverable, safely end the conversation to clear the corrupted payload:
  • END CONVERSATION '<Conversation-Handle>' WITH CLEANUP;

Step 4: Check Network and Antivirus Interference on Windows Server 2025

  • Inspect Windows Defender Firewall or third-party antivirus logs for packet inspection/modification on the SQL Server port (default 4022 for Service Broker).
  • Add an exclusion rule for sqlservr.exe and the Service Broker port in Windows Defender settings.
  • Restart the SQL Server service after applying exclusions: Restart-Service -Name 'MSSQLSERVER'

Step 5: Restore from a Known Good Backup (If Corruption Persists)

  • If the msdb database itself shows signs of corruption, run DBCC CHECKDB (msdb); to confirm integrity issues.
  • Restore msdb from the most recent verified backup if repairallowdata_loss is required and acceptable.

Alternative or Verification Steps

  • To verify the fix, re-enable the queue (ALTER QUEUE [YourQueueName] WITH STATUS = ON;) and monitor sys.transmission_queue for 24 hours to confirm no new Error 11273 entries appear in the SQL Server error log.
  • As an alternative, if certificate issues persist, drop and recreate the Service Broker endpoint entirely using CREATE ENDPOINT with fresh certificate authentication to rule out a corrupted security context.