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

by

Troubleshooting Guide: SQL Server Error 10919 – Resource Governor Configuration Read Failure

Why This Error Happens

This error occurs when SQL Server 2025 fails to read the Resource Governor metadata stored in the master database, typically during startup, ALTER RESOURCE GOVERNOR RECONFIGURE, or when querying sys.resource_governor_configuration. The most common root causes are corruption in the master database’s system catalog, insufficient permissions on the Resource Governor DDL/metadata objects, or an incomplete/interrupted upgrade that left the Resource Governor configuration tables in an inconsistent state. In rare cases, this is triggered by manual edits to system tables or a failed in-place upgrade from an older SQL Server version to SQL Server 2025.

Step-by-Step Resolution Guide

Step 1: Verify Master Database Integrity

  • Open SQL Server Management Studio (SSMS) or sqlcmd and connect to the instance using an account with sysadmin privileges.
  • Run DBCC CHECKDB ('master') WITH NO_INFOMSGS, ALL_ERRORMSGS; to check for corruption in system pages.
  • Review the output for allocation errors or consistency errors specifically referencing Resource Governor internal tables (e.g., sys.sysrsrvgovcfg).
  • If corruption is found, restore master from a known-good backup taken before the error started occurring.

Step 2: Validate Permissions on Resource Governor Objects

  • Confirm the login attempting the operation has CONTROL SERVER or ALTER ANY RESOURCE GOVERNOR CONFIGURATION permission.
  • Run the following query to check current permissions:
SELECT * FROM fn_my_permissions(NULL, 'SERVER');
  • If permissions are missing, grant them explicitly:
GRANT ALTER ANY RESOURCE GOVERNOR CONFIGURATION TO [YourLogin];
  • Restart the SQL Server service via services.msc or Restart-Service MSSQLSERVER in PowerShell on Windows Server 2025 for permission changes to take effect.

Step 3: Reset Resource Governor to Default Configuration

  • Open a new query window in SSMS with elevated/sysadmin rights.
  • Execute the following to disable and reset Resource Governor to its default state:
ALTER RESOURCE GOVERNOR DISABLE;
ALTER RESOURCE GOVERNOR RESET STATISTICS;
ALTER RESOURCE GOVERNOR RECONFIGURE;
  • If the RECONFIGURE statement still throws Error 10919, proceed to rebuild the configuration manually by dropping custom workload groups and pools, then recreating them.

Step 4: Check for Incomplete Upgrade Artifacts

  • Navigate to C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ (adjust version folder for SQL Server 2025) and open the latest ERRORLOG file.
  • Search for entries related to “Resource Governor” or “upgrade script” failures that occurred during installation.
  • If an upgrade failure is detected, run the SQL Server Setup repair option from Control Panel > Programs > Microsoft SQL Server 2025 > Repair.
  • After repair completes, restart the SQL Server service and re-run ALTER RESOURCE GOVERNOR RECONFIGURE;.

Step 5: Rebuild System Databases (Last Resort)

  • If corruption persists and no valid backup exists, use the SQL Server 2025 installation media to run setup.exe /ACTION=REBUILDDATABASE to rebuild the master, model, and msdb databases.
  • Reapply all server-level configurations, logins, and linked servers manually after the rebuild since this action resets master to default.
  • Restore user databases separately, as they are not affected by the master rebuild.

Alternative or Verification Steps

  • To verify the fix, run SELECT * FROM sys.resource_governor_configuration; and confirm it returns data without errors, then check the SQL Server Error Log for the absence of Event ID 10919 after a service restart.
  • As an alternative, if the issue is isolated to a specific workload group or pool, export the current Resource Governor DDL script (if accessible), fully disable Resource Governor, drop all custom pools/groups, and reapply the script incrementally to isolate the corrupted object.