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

by

Troubleshooting Guide: SQL Server Error 3636

Why This Error Happens

Error 3636 occurs when SQL Server’s storage engine encounters an inconsistency while reading or writing file metadata for a specific database and file ID combination, typically pointing to on-disk corruption at the page or allocation map level. This can be triggered by abrupt power loss, faulty storage hardware, antivirus software locking database files mid-transaction, or a mismatch between the metadata cache and the actual file state after an improper shutdown. In some cases, insufficient NTFS permissions on the SQL Server service account can also prevent proper metadata validation during file access.

Step-by-Step Resolution Guide

Step 1: Verify Database and File Integrity

  • Open SQL Server Management Studio (SSMS) and run DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS; to identify the scope of corruption.
  • Cross-reference the file ID in the error message using SELECT file_id, name, physical_name FROM sys.master_files WHERE database_id = DB_ID('YourDatabaseName');
  • Check the SQL Server Error Log (C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for accompanying I/O or page-checksum errors.

Step 2: Rule Out Storage and Permission Issues

  • Confirm the SQL Server service account has full read/write permissions on the data/log file directory (typically D:\SQLData\ or D:\SQLLogs\).
  • Open Windows Event Viewer and check the System log for Disk or NTFS warnings correlating with the error timestamp.
  • Temporarily disable real-time antivirus scanning on the .mdf, .ndf, and .ldf file paths to rule out file-locking conflicts.

Step 3: Repair or Restore the Affected Database

  • If DBCC CHECKDB reports allocation errors, run DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS, REPAIR_ALLOW_DATA_LOSS; only after taking a full backup, since this option may discard corrupted data.
  • If a clean backup exists, prefer restoring from the last known-good full backup plus transaction log backups instead of running repair.
  • Take the database offline first with ALTER DATABASE YourDatabaseName SET OFFLINE; before attempting file-level repairs, then bring it back ONLINE.

Step 4: Patch and Restart SQL Server Services

  • Ensure SQL Server 2025 is updated with the latest Cumulative Update (CU) via SQL Server Setup > Maintenance, since file-metadata handling bugs are periodically patched.
  • Restart the SQL Server service via services.msc or net stop MSSQLSERVER && net start MSSQLSERVER to clear any stale in-memory metadata cache.

Alternative or Verification Steps

  • After remediation, re-run DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS; and confirm it returns zero allocation or consistency errors, then monitor the ERRORLOG for 24-48 hours to ensure Error 3636 does not recur.
  • If corruption persists after repair, restore the entire database from the most recent verified backup set onto a healthy disk volume as a fallback rather than continuing to repair in place.