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

by

Troubleshooting Guide: Error 3637 — Parallel Operation Cannot Be Started from a DAC Connection

Why This Error Happens

Error 3637 occurs because the Dedicated Administrator Connection (DAC) in SQL Server 2025 is intentionally restricted to a single-threaded, serial execution context to guarantee administrators can always connect and diagnose a server even under severe resource pressure. When a query submitted through the DAC requires a parallel execution plan (due to MAXDOP settings, query complexity, or Resource Governor workload group configuration), the engine blocks it rather than allowing parallelism on this restricted connection. This typically surfaces when a DBA runs complex diagnostic queries, large joins, or maintenance scripts directly over the DAC port (1434 or dynamically assigned) instead of a standard connection.

Step-by-Step Resolution Guide

Step 1: Force a Serial Execution Plan on the Query

  • Add the query hint OPTION (MAXDOP 1) to the end of the problematic statement before executing it via DAC.
  • Example: SELECT * FROM sys.dm_exec_requests OPTION (MAXDOP 1);
  • This is the fastest fix and requires no server configuration changes.

Step 2: Verify and Adjust the Server-Level MAXDOP Setting

  • Open SQL Server Management Studio (SSMS) and connect via a normal (non-DAC) connection.
  • Run EXEC sp_configure 'max degree of parallelism'; to check the current value.
  • If it is set higher than 1 and DAC queries continue triggering parallel plans, consider setting a Resource Governor workgroup specifically for DAC sessions with MAX_DOP = 1.
  • Apply changes with RECONFIGURE;.

Step 3: Check Resource Governor Classification for DAC Sessions

  • Navigate to Management > Resource Governor in SSMS Object Explorer on the instance.
  • Confirm the DAC connection is not being misclassified into a workload group that permits parallelism.
  • If using a classifier function, inspect its logic located under Resource Governor > Classifier Function Name and ensure DAC logins route to the default group with MAX_DOP explicitly set to 1.
  • Run ALTER WORKLOAD GROUP [groupname] WITH (MAX_DOP = 1); ALTER RESOURCE GOVERNOR RECONFIGURE; if adjustments are needed.

Step 4: Restart the SQL Server Service to Clear Cached Plans (If Needed)

  • Open Services.msc on Windows Server 2025 / Windows 11.
  • Locate SQL Server (MSSQLSERVER) or the named instance service.
  • Right-click and select Restart to clear any cached execution plans that may still force parallelism.
  • Alternatively, run DBCC FREEPROCCACHE; from a standard connection to avoid a full restart.

Step 5: Reconnect via DAC and Re-Test the Query

  • Use the syntax sqlcmd -S ADMIN:ServerName -U sa -P password from Command Prompt to re-establish the DAC session.
  • Re-run the original diagnostic or maintenance query and confirm Error 3637 no longer appears.

Alternative or Verification Steps

  • Verify the fix by querying sys.dm_exec_query_stats or re-running the original failing script through the DAC connection — it should now complete without error 3637.
  • If the issue persists, run the query through a standard SSMS connection instead of DAC, since DAC should only be used for lightweight diagnostics, not heavy parallel workloads.