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

by

Troubleshooting Guide: SQL Server Error 8563 — RPCSS Service State Determination Failure

Why This Error Happens

This error occurs when SQL Server 2025 attempts to query the Remote Procedure Call (RPC) subsystem—specifically the RPCSS (Remote Procedure Call Service)—to determine its running state, often as part of service enumeration, WMI queries, or Service Control Manager (SCM) interactions during startup or clustering operations. The underlying cause is typically a permissions mismatch where the SQL Server service account lacks sufficient rights to query the SCM or WMI namespace, a transient timing issue where RPCSS has not fully initialized before SQL Server polls it, or DCOM/WMI repository corruption on Windows Server 2025 / Windows 11. Despite its alarming appearance in the SQL Server error log, Microsoft explicitly flags this as informational, meaning SQL Server successfully handled the failed call and continued normal operation.

Step-by-Step Resolution Guide

Step 1: Confirm RPCSS Service Health

  • Open services.msc and locate “Remote Procedure Call (RPC)” — confirm Status is “Running” and Startup Type is “Automatic”.
  • Run sc query RpcSs from an elevated Command Prompt to verify STATE returns 4 RUNNING.
  • Check Event Viewer under Windows Logs > System for any RPCSS-related crash or restart events around the same timestamp as the SQL error.

Step 2: Validate Service Account Permissions

  • Open Component Services (dcomcnfg.exe), navigate to Component Services > Computers > My Computer > DCOM Config.
  • Right-click the computer object, select Properties > COM Security tab, and ensure the SQL Server service account has “Remote Launch,” “Remote Activation,” and “Local Launch” permissions under Launch and Activation Permissions.
  • Confirm the SQL Server service account is a member of the local Distributed COM Users group via lusrmgr.msc.

Step 3: Rebuild the WMI Repository (If Corruption Suspected)

  • Stop the Windows Management Instrumentation service: net stop winmgmt.
  • Rename the repository folder: ren %windir%\System32\wbem\Repository Repository.old.
  • Restart WMI: net start winmgmt, then allow it to rebuild automatically on next query.
  • Restart the SQL Server service and monitor the error log for recurrence.

Step 4: Apply Latest Windows Server 2025 / Windows 11 Updates

  • Navigate to Settings > Windows Update and install all pending cumulative updates, as this error has known fixes tied to RPC/DCOM timing bugs in early Windows Server 2025 builds.
  • Specifically check for updates referencing “RPCSS,” “DCOM,” or “Service Control Manager” in the update notes.
  • Reboot the server after installation to ensure RPCSS initializes cleanly on next boot.

Step 5: Adjust SQL Server Service Startup Dependencies

  • Open an elevated Command Prompt and run sc qc MSSQLSERVER to view current dependencies.
  • If RPCSS is not listed, add it manually: sc config MSSQLSERVER depend= RPCSS.
  • This forces Windows SCM to guarantee RPCSS is fully started before SQL Server attempts its state query, eliminating the race condition.

Alternative or Verification Steps

  • Restart the SQL Server service and review SQL Server Error Log (via SSMS > Management > SQL Server Logs) to confirm Error 8563 no longer appears, or appears without recurring frequency.
  • If the message persists but SQL Server operations (connectivity, failover, Agent jobs) remain unaffected, treat it as benign per Microsoft documentation and suppress it from alerting rules in your monitoring tool (e.g., SCOM, SolarWinds) since it is explicitly informational.