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

by

Troubleshooting Guide: Error 9694 – Service Broker Manager Could Not Start

Why This Error Happens

Error 9694 occurs when SQL Server’s Service Broker manager fails to initialize during database startup, typically because the Service Broker GUID is missing, duplicated, or corrupted in the sys.databases catalog. This can also happen if the master key used for Service Broker encryption is inaccessible, the endpoint configuration is invalid, or a TCP port conflict prevents the Broker listener from binding. Additionally, file-level corruption in the database or a mismatch after a restore/attach operation (where the broker GUID collides with another database) is a common trigger.

Step-by-Step Resolution Guide

Step 1: Check the SQL Server Error Log and Windows Event Viewer

  • Open SQL Server Management Studio (SSMS) and navigate to Management > SQL Server Logs.
  • Look for accompanying errors near Error 9694, such as 9692 (GUID conflict) or 15466 (master key issues).
  • Cross-reference with Windows Event Viewer under Windows Logs > Application for OS-level network or socket errors.

Step 2: Verify and Reset the Service Broker GUID

  • Run the following query to check the current Broker GUID and status:
  SELECT name, service_broker_guid, is_broker_enabled FROM sys.databases;
  • If the database was restored or copied and shows a GUID conflict, reset it using:
  ALTER DATABASE [YourDatabaseName] SET NEW_BROKER WITH ROLLBACK IMMEDIATE;
  • Alternatively, if you want to preserve existing conversations, use SET ENABLE_BROKER instead of NEW_BROKER.

Step 3: Check for Port Conflicts on the Service Broker Endpoint

  • Identify the TCP port assigned to the Service Broker endpoint (default is 4022):
  SELECT name, port FROM sys.tcp_endpoints WHERE type_desc = 'SERVICE_BROKER';
  • Use netstat -ano | findstr "4022" in an elevated PowerShell/Command Prompt on Windows Server 2025 to confirm no other process is binding to that port.
  • If a conflict exists, either stop the conflicting process or reassign the Broker endpoint to a different port via ALTER ENDPOINT.

Step 4: Validate the Service Master Key and Database Master Key

  • Ensure the Service Master Key is intact by running:
  OPEN MASTER KEY DECRYPTION BY PASSWORD = 'YourStrongPassword';
  • If the key is corrupted or missing, regenerate it using:
  ALTER SERVICE MASTER KEY FORCE REGENERATION;
  • Restart the SQL Server service via Services.msc or net stop MSSQLSERVER && net start MSSQLSERVER after regeneration.

Step 5: Restart SQL Server and Monitor Startup

  • Restart the SQL Server (MSSQLSERVER) service through the Services console on Windows Server 2025/Windows 11.
  • Immediately check the error log again for confirmation that Service Broker initialized without the 9694 error.
  • If the issue persists, run SQL Server in a command-line startup trace mode (sqlservr.exe -c -T3608) to isolate the exact failure point.

Alternative or Verification Steps

  • Confirm the fix by querying SELECT is_broker_enabled FROM sys.databases WHERE name = 'YourDatabaseName'; — a value of 1 confirms Broker is active and running.
  • If the primary steps fail, consider restoring the database from a known-good backup prior to the corruption event, then re-apply the NEW_BROKER command to ensure a clean GUID state.