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

by

Troubleshooting Guide: SQL Server Error 3939 — Uncommittable Transaction Due to FILESTREAM Request Failure

Why This Error Happens

Error 3939 occurs when a transaction involving a FILESTREAM operation encounters an I/O failure, permission issue, or filesystem-level conflict that SQL Server cannot resolve mid-transaction, forcing an automatic rollback. The most common root causes are NTFS permission mismatches between the SQL Server service account and the FILESTREAM data container, antivirus or backup software locking files in the FILESTREAM filegroup, or corruption/inconsistency in the FILESTREAM container directory structure. In Windows Server 2025 environments, this is frequently exacerbated by stricter default ACL inheritance settings and enhanced Windows Defender real-time scanning on data volumes.

Step-by-Step Resolution Guide

Step 1: Verify FILESTREAM is Properly Enabled at Both OS and Instance Level

  • Open SQL Server Configuration Manager → right-click your instance → Properties → FILESTREAM tab → confirm “Enable FILESTREAM for Transact-SQL access” and “Enable FILESTREAM for file I/O streaming access” are checked.
  • Run the following T-SQL to confirm instance-level configuration matches:
  EXEC sp_configure 'filestream access level';
  RECONFIGURE;
  • Ensure the value is set to 2 (full access), not 0 or 1.

Step 2: Audit NTFS Permissions on the FILESTREAM Data Container

  • Navigate to the physical path of your FILESTREAM filegroup (e.g., D:\SQLData\FileStreamContainer).
  • Right-click the folder → Properties → Security tab → confirm the SQL Server service account (e.g., NT Service\MSSQLSERVER) has Full Control.
  • Also verify the account has Modify and Write rights at the parent directory level, since inherited permissions in Windows Server 2025 can silently restrict child folder access.
  • Reset permissions if needed using an elevated PowerShell session:
  icacls "D:\SQLData\FileStreamContainer" /grant "NT SERVICE\MSSQLSERVER:(OI)(CI)F" /T

Step 3: Exclude FILESTREAM Directories from Antivirus and Backup Scanning

  • Open Windows Security → Virus & threat protection → Manage settings → Add or remove exclusions.
  • Add the full FILESTREAM container path and the mssqlsystemresource.mdf directory to exclusions.
  • If using third-party backup agents (e.g., Veeam, Commvault), confirm they are not holding file locks on FILESTREAM BLOBs during active transactions.

Step 4: Check for FILESTREAM Filegroup Corruption

  • Run a consistency check against the affected database:
  DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • If corruption is reported specifically in FILESTREAM pointers or the filestream.hdr file, restore the affected filegroup from a known-good backup rather than attempting an in-place repair.

Step 5: Review SQL Server Error Log for the Underlying I/O Exception

  • Open SQL Server Management Studio (SSMS) → Management → SQL Server Logs.
  • Look for accompanying errors such as 5120 (file access denied) or 823/824 (I/O errors) immediately preceding Error 3939 — these pinpoint the exact file-level failure triggering the rollback.

Alternative or Verification Steps

  • To verify the fix, re-run the original transaction or stored procedure that referenced FILESTREAM data and confirm no rollback occurs; check sys.dm_tran_active_transactions to ensure no orphaned transactions remain.
  • If the issue persists after permission and antivirus fixes, as a fallback, migrate the affected FILESTREAM filegroup to a new volume using ALTER DATABASE ... ADD FILE with a fresh container path, then transfer BLOB data via INSERT INTO ... SELECT to bypass the corrupted container entirely.