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

by

Troubleshooting Guide: Error 7931 – FILESTREAM Directory ID Seen Two Times

Why This Error Happens

This error occurs when SQL Server’s internal consistency checker (DBCC CHECKDB) detects duplicate FILESTREAM directory GUIDs across partitions, indicating corruption in the FILESTREAM filegroup’s metadata structure. This typically results from improper shutdowns, storage-level corruption, or manual/external manipulation of files within the FILESTREAM data container outside of SQL Server’s control. It can also surface after a failed or interrupted restore/attach operation involving FILESTREAM-enabled databases.

Step-by-Step Resolution Guide

Step 1: Run a Full Consistency Check

  • Open SQL Server Management Studio (SSMS) or a query window connected to the affected instance.
  • Execute DBCC CHECKDB ('YourDatabaseName') WITH ALL_ERRORMSGS, NO_INFOMSGS; to get a complete list of corruption errors tied to Error 7931.
  • Note the specific partition ID and FILESTREAM directory GUID referenced in the output for cross-referencing.

Step 2: Inspect the FILESTREAM Data Container

  • Navigate to the FILESTREAM filegroup path (commonly found under a path like D:\SQLData\FileStreamContainer\).
  • Verify that no external processes (antivirus, backup agents, or manual file explorer actions) have modified, duplicated, or renamed the internal GUID-named folders.
  • Exclude the FILESTREAM container path from antivirus real-time scanning via Windows Security settings to prevent file-lock conflicts that can cause metadata mismatches.

Step 3: Restore from a Clean Backup

  • Since FILESTREAM directory corruption is rarely repairable via REPAIR_ALLOW_DATA_LOSS without losing the affected BLOB data, locate the most recent verified-clean full backup.
  • Use RESTORE DATABASE [YourDatabaseName] FROM DISK = 'E:\Backups\YourDB.bak' WITH REPLACE, RECOVERY; to restore the database to a consistent state.
  • Ensure the destination server has the FILESTREAM feature enabled via SQL Server Configuration Manager before initiating the restore.

Step 4: Rebuild the FILESTREAM Filegroup (If Restore Is Not Viable)

  • If no backup exists, create a new FILESTREAM filegroup and file group container using ALTER DATABASE YourDatabaseName ADD FILEGROUP FileStreamGroup2 CONTAINS FILESTREAM;.
  • Migrate accessible BLOB data from the corrupted filegroup to the new one using INSERT INTO NewTable SELECT * FROM OldTable WHERE DocumentID NOT IN (SELECT DocumentID FROM CorruptedRows);.
  • Drop the old corrupted filegroup once data migration is confirmed complete.

Alternative or Verification Steps

  • Re-run DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS; after remediation to confirm Error 7931 no longer appears in the output.
  • If the issue persists on Windows Server 2025, check the underlying storage subsystem (SAN/NAS or local disk) for hardware-level errors using chkdsk D: /f /r on the volume hosting the FILESTREAM container.