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

by

Troubleshooting Guide: SQL Server Error 338 “READEXT” Failure

Why This Error Happens

Error 338 in SQL Server 2025 typically occurs when the READEXT (Read Extent) subsystem fails to retrieve data pages from disk due to corrupted database extents, misconfigured file system permissions, or interrupted I/O operations. This is often triggered by abrupt service termination, disk-level corruption, or antivirus software locking database files (.mdf/.ldf) during active read operations. In Windows Server 2025 environments, this can also stem from NTFS permission changes applied during OS updates that restrict the SQL Server service account from accessing extent-mapped storage locations.

Step-by-Step Resolution Guide

Step 1: Verify SQL Server Service Account Permissions

  • Open Services.msc and locate the SQL Server (MSSQLSERVER) service.
  • Confirm the service account has Full Control on the database directory (typically C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA).
  • Right-click the DATA folder → Properties → Security → Edit, and add the SQL Server service account if missing.

Step 2: Run DBCC CHECKDB to Identify Corruption

  • Open SQL Server Management Studio (SSMS) and connect to the affected instance.
  • Execute the following command against the impacted database:
  • DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • Review the output for extent allocation errors tied to Error 338.

Step 3: Exclude SQL Server Files from Antivirus Scanning

  • Navigate to Windows Security → Virus & Threat Protection → Manage Settings → Exclusions.
  • Add exclusions for the full DATA and LOG directories, as well as sqlservr.exe.
  • Restart the SQL Server service to release any locked file handles.

Step 4: Restore from Last Known Good Backup

  • If DBCC CHECKDB reports unrepairable corruption, stop the SQL Server service via SQL Server Configuration Manager.
  • Restore the last verified full backup using:
  • RESTORE DATABASE YourDatabaseName FROM DISK = 'D:\Backups\YourDatabase.bak' WITH REPLACE;
  • Reapply any transaction log backups if point-in-time recovery is required.

Step 5: Update SQL Server Cumulative Updates

  • Check for the latest Cumulative Update (CU) for SQL Server 2025 via Microsoft’s official Download Center.
  • Install the update package and reboot Windows Server 2025 to ensure the storage engine patches are fully applied.

Alternative or Verification Steps

  • Verify resolution by re-running DBCC CHECKDB and confirming zero allocation or consistency errors in the output.
  • If Error 338 persists, run sqlcmd -S localhost -Q "SELECT * FROM sys.dm_os_ring_buffers WHERE ring_buffer_type='RING_BUFFER_EXCEPTION'" to capture deeper diagnostic exception data for a Microsoft Support case.