Diagnosing SQL Server Service Broker Queue Activation Issues on Windows 11 25H2

Symptoms

• SQL Server Service Broker queue activation stored procedures do not execute automatically
• Activation errors logged in SQL Server error log or Windows Event Viewer
• Delayed or missing message processing in Service Broker queues
• Related SQL Server services show stopped or error states

Likely causes

• Windows Service 'SQL Server (MSSQLSERVER)' or related SQL Server Agent service not running or unstable
• Insufficient permissions for SQL Server service account to access necessary system resources
• Corrupted or misconfigured Service Broker queue or activation stored procedure
• Interference from Windows Defender or third-party security software blocking SQL Server components

What FixWin checks

• Verify 'SQL Server (MSSQLSERVER)' and 'SQL Server Agent' services are running via Services MMC (services.msc)
• Check Windows Event Viewer under 'Application' and 'System' logs for SQL Server related errors
• Confirm that the SQL Server service account has appropriate permissions on local machine and database
• Review Service Broker queue status and activation stored procedure configuration using SQL Server Management Studio
• Inspect Windows Defender or third-party antivirus logs for blocked SQL Server processes or ports

AI diagnostic workflow

• Open Services MMC and ensure 'SQL Server (MSSQLSERVER)' and 'SQL Server Agent' are running
• Use Event Viewer to locate errors related to Service Broker activation under Application logs
• Connect to SQL Server instance with SQL Server Management Studio and query sys.transmission_queue and sys.dm_broker_activated_tasks
• Check stored procedure code linked to queue activation for errors or deadlocks
• Temporarily disable antivirus or Windows Defender Real-time Protection to test for interference

Related Windows entities

• SQL Server (MSSQLSERVER) service
  Primary Windows service hosting SQL Server instance and responsible for Service Broker operations.
• SQL Server Agent service
  Manages scheduled jobs and can influence activation stored procedure execution.
• Windows Event Viewer tool
  Centralized logging tool to identify errors and warnings related to Service Broker and SQL Server.
• Service Broker Queue component
  Core SQL Server component enabling asynchronous message processing and activation.
• Windows Defender component
  Built-in security software that may block SQL Server processes or network ports affecting Service Broker.

Repair logic

Begin by confirming that all relevant SQL Server services are running and stable. Next, analyze Windows Event Viewer logs for error messages related to Service Broker activation failures. Validate that the SQL Server service account has proper permissions both on the Windows system and within SQL Server. Inspect the Service Broker queue and the linked activation stored procedure for errors or misconfigurations using SQL Server Management Studio. Finally, rule out interference from Windows Defender or third-party antivirus software by temporarily disabling them and testing the activation process again.

FAQ

Why does my Service Broker activation stored procedure not run automatically on Windows 11 25H2?

This can be due to the SQL Server service or Agent not running, permission issues with the service account, errors in the stored procedure, or security software blocking necessary processes.

How can I check if Windows Defender is interfering with SQL Server Service Broker?

Review Windows Defender logs for blocked applications or network activity related to SQL Server. Temporarily disable real-time protection to see if activation behavior improves.

What logs should I examine to diagnose Service Broker queue activation problems?

Check the SQL Server error log via SQL Server Management Studio and the Windows Event Viewer Application log for Service Broker and SQL Server related error messages.

Related Windows problems

• Windows 11 25H2 Microsoft Graph PowerShell Authentication Popup Not Appearing