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

by

Troubleshooting Guide: Error 11293 – “Forwarded Message Dropped Because a Transport Is Shutdown”

Why This Error Happens

This error typically occurs within SQL Server’s Service Broker component, where a transport layer responsible for forwarding messages between dialogs is terminated mid-operation. The most common root cause is an abrupt restart or shutdown of the SQL Server service while Service Broker transport connections are still actively routing messages. This can also stem from network instability, endpoint misconfiguration, or forced termination of the sqlservr.exe process that interrupts the message forwarding pipeline before completion.

Step-by-Step Resolution Guide

Step 1: Verify Service Broker Status and Configuration

  • Open SQL Server Management Studio (SSMS) and run SELECT name, is_broker_enabled FROM sys.databases; to confirm Service Broker is enabled on the affected database.
  • Check for orphaned or disabled endpoints using SELECT * FROM sys.service_broker_endpoints;.
  • If is_broker_enabled returns 0, re-enable it with ALTER DATABASE [YourDB] SET ENABLE_BROKER;.

Step 2: Inspect SQL Server Error Logs and Event Viewer

  • On Windows Server 2025 / Windows 11, open Event Viewer and navigate to Windows Logs > Application.
  • Filter for Event ID 11293 and note the timestamp to correlate with any service restarts or crashes.
  • Cross-reference with the SQL Server error log located at C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG for additional context around transport shutdown events.

Step 3: Restart the SQL Server Service Gracefully

  • Avoid force-killing sqlservr.exe via Task Manager, as this directly causes transport shutdown errors.
  • Use SQL Server Configuration Manager or run net stop MSSQLSERVER followed by net start MSSQLSERVER in an elevated PowerShell/Command Prompt.
  • Ensure no pending transactions or active Broker conversations exist before restarting, using SELECT * FROM sys.conversation_endpoints WHERE state <> 'CD';.

Step 4: Rebuild or Reset Broker Conversations

  • If stale conversations persist, end them manually with END CONVERSATION 'conversation_handle' WITH CLEANUP;.
  • Rebuild the Service Broker GUID if corruption is suspected: ALTER DATABASE [YourDB] SET NEW_BROKER; (use with caution as this breaks existing conversations).

Step 5: Check Network and Firewall Stability

  • Verify that Windows Firewall or any third-party security software isn’t intermittently blocking the Service Broker TCP port (default 4022).
  • Run netstat -ano | findstr 4022 in PowerShell to confirm the port is listening and not being reset.

Alternative or Verification Steps

  • To verify the fix, monitor the SQL Server error log and Event Viewer over the next 24-48 hours to confirm Event ID 11293 no longer appears during routine operations or service restarts.
  • If the issue persists, consider failing over to a secondary replica (if using Always On Availability Groups) and rebuilding Service Broker routes from scratch using CREATE ROUTE with updated transport addresses.