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

by

Troubleshooting Guide: SQL Server Error 8360 – SQL Trace Event Notification Failure

Why This Error Happens

Error 8360 occurs when SQL Server’s Service Broker, which handles event notification delivery for SQL Trace, is unable to queue or send a message due to insufficient memory, worker thread exhaustion, or a full transmission queue. This is typically a symptom of underlying resource pressure on the server, such as high memory consumption by other processes or an undersized max server memory configuration. In some cases, this can also occur if the msdb database or the Service Broker queues associated with event notifications have become corrupted or disabled.

Step-by-Step Resolution Guide

Step 1: Verify Server Resource Availability

  • Open Task Manager or Performance Monitor (PerfMon) on Windows Server 2025 to check current memory and CPU utilization.
  • Check the SQLServer:Memory Manager counter for “Memory Grants Pending,” as a high value indicates active memory starvation.
  • Review the SQL Server Error Log (via SSMS > Management > SQL Server Logs) for concurrent Out of Memory (OOM) warnings that often accompany Error 8360.

Step 2: Adjust SQL Server Memory Configuration

  • Open SQL Server Management Studio (SSMS) and connect to the instance via the Query Editor.
  • Run sp_configure 'max server memory (MB)' to check the current limit.
  • Ensure the value leaves at least 4GB to 10% of total RAM (whichever is greater) available for the Windows Server 2025 OS to prevent paging.
  • Execute: EXEC sp_configure 'show advanced options', 1; RECONFIGURE; EXEC sp_configure 'max server memory', 16384; RECONFIGURE; (Adjust the MB value based on your total system RAM).

Step 3: Check and Repair Service Broker Status

  • Verify that Service Broker is enabled for the msdb database, as it is required for internal trace event notifications.
  • Run the following query to check the status: SELECT name, is_broker_enabled FROM sys.databases WHERE name = 'msdb';
  • If the result returns 0, enable it by running: ALTER DATABASE msdb SET ENABLE_BROKER;
  • Restart the SQL Server (MSSQLSERVER) service via the Services console (services.msc) to clear any hung Broker queues.

Step 4: Switch to File-Based Tracing (If using SQL Trace specifically)

  • Since SQL Trace relies on Service Broker for notifications, consider migrating critical traces to Extended Events, which is natively more resource-efficient in SQL Server 2025.
  • If you must continue using the legacy Trace, redirect the output to a local file system path (e.g., D:\SQLTraces\) rather than relying on event notifications to reduce overhead.

Alternative or Verification Steps

  • Verification: After implementing the memory fix, monitor the SQL Server Error Log for 24–48 hours to confirm Error 8360 does not recur during peak load times.
  • Alternative: If the error persists despite available resources, run DBCC CHECKDB('msdb') to rule out corruption in the system database hosting the Service Broker objects.