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

by

Troubleshooting Guide: SQL Server Error 10922

Why This Error Happens

Error 10922 (%ls failed. Rerun the statement.) typically occurs when SQL Server encounters a transient failure while executing a DDL or metadata operation, often due to a schema lock conflict, insufficient permissions on system catalog views, or a brief I/O interruption on the underlying storage. This is commonly seen during concurrent index rebuilds, statistics updates, or when the Database Engine cannot immediately acquire the required internal resources to complete the statement. In rare cases, it can also indicate underlying corruption in system metadata or a failing storage subsystem that intermittently delays write confirmations.

Step-by-Step Resolution Guide

Step 1: Simply Rerun the Statement

  • As the error message suggests, this is often a transient issue; execute the exact same query again.
  • Check SQL Server Management Studio (SSMS) Activity Monitor for blocking sessions before rerunning.
  • If using a script, wrap the statement in a retry loop with a WAITFOR DELAY '00:00:05' before retrying.

Step 2: Check for Blocking and Schema Locks

  • Run sp_who2 or query sys.dm_exec_requests to identify sessions holding schema locks (Sch-M) on the affected object.
  • Terminate long-running blocking transactions using KILL <session_id> if safe to do so.
  • Ensure no concurrent ALTER INDEX, CREATE INDEX, or UPDATE STATISTICS jobs are running on the same table.

Step 3: Verify Database and Disk Integrity

  • Run DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS; to rule out corruption.
  • Check Windows Event Viewer (Windows Logs > System) for Disk or NTFS warnings correlating with the SQL error timestamp.
  • Confirm the storage volume hosting the .mdf/.ldf files has sufficient free space and is not nearing capacity.

Step 4: Validate SQL Server Service Account Permissions

  • Open Services.msc on Windows Server 2025 and confirm the SQL Server service account has “Log on as a service” rights.
  • Verify the account has db_owner or appropriate ALTER permissions on the target database via SSMS > Security > Logins.
  • Restart the SQL Server service (net stop MSSQLSERVER && net start MSSQLSERVER) if permissions were recently modified.

Step 5: Update SQL Server Cumulative Updates

  • Navigate to Microsoft Update Catalog and check the installed build version via SELECT @@VERSION;.
  • Apply the latest Cumulative Update (CU) for SQL Server 2025, as this error has known fixes related to metadata handling in early builds.
  • Reboot the Windows Server 2025 instance after patching to ensure services reload cleanly.

Alternative or Verification Steps

  • Re-execute the original failing query and confirm it completes without the 10922 error; cross-check the SQL Server Error Log (Management > SQL Server Logs in SSMS) for recurrence.
  • If the error persists, run the statement during an off-peak maintenance window to rule out resource contention, or failover to a secondary replica (if using Always On Availability Groups) to isolate whether the issue is node-specific.