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

by

Troubleshooting Guide: SQL Server Error 7125

Why This Error Happens

Error 7125 in SQL Server typically occurs when the image_text or off-row data structure linked to a BLOB column (text, ntext, or image) is corrupted or references invalid page allocations. This often results from abrupt shutdowns, storage-level corruption, or disk I/O failures that disrupt the write operations to the LOB (Large Object) pages. In SQL Server 2025 running on Windows Server 2025/Windows 11, this can also surface due to mismatched file system permissions (NTFS ACLs) following an OS upgrade, which prevents the Database Engine service account from properly accessing legacy BLOB storage paths.

Step-by-Step Resolution Guide

Step 1: Verify Database Consistency

  • Open SQL Server Management Studio (SSMS) and connect to the affected instance.
  • Run the following command to identify the scope of corruption:
  DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • Look specifically for errors referencing “text, ntext, and image page” allocation errors in the output log.

Step 2: Check NTFS Permissions and Service Account Access

  • Navigate to the SQL Server data directory, typically located at:
    C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA\
  • Right-click the .mdf and .ldf files, select Properties > Security, and ensure the NT SERVICE\MSSQLSERVER account has Full Control.
  • If permissions were reset during a Windows Server 2025 update, restore them via PowerShell:
  icacls "C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA" /grant "NT SERVICE\MSSQLSERVER:(OI)(CI)F" /T

Step 3: Restore from a Clean Backup (If Corruption is Severe)

  • If DBCC CHECKDB reports unrepairable allocation errors, failover to the last known good backup.
  • Use the following T-SQL syntax to restore the database, replacing paths as necessary:
  RESTORE DATABASE YourDatabaseName 
  FROM DISK = 'D:\Backups\YourDatabaseName.bak' 
  WITH REPLACE, RECOVERY;
  • Ensure the backup predates the specific “Getting Data” query failure to avoid re-importing corrupted BLOB pointers.

Step 4: Rebuild Corrupted Indexes

  • For tables containing the affected text/image columns, rebuild the clustered index to force a reallocation of page structures.
  • Execute the following command for the specific table:
  ALTER INDEX ALL ON YourTableName REBUILD;

Alternative or Verification Steps

  • Verification: Re-run the specific query or application action that triggered the “Getting Data” symptom to confirm the BLOB data retrieves without throwing Error 7125.
  • Alternative: If the error persists only on specific rows, use DBCC CHECKTABLE with the REPAIR_ALLOW_DATA_LOSS option as a last resort, understanding that this will remove the specific corrupted BLOB chain rather than recovering it.