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

by

Troubleshooting Guide: SQL Server Error 5597 — FILESTREAM Feature Could Not Be Initialized

Why This Error Happens

This error occurs because FILESTREAM is disabled at the Windows operating system level, even though it may be enabled within SQL Server itself via sp_configure. SQL Server 2025 requires the FILESTREAM access level to be enabled at both the SQL Server Configuration Manager (OS integration) layer and the instance-level configuration layer for the feature to initialize correctly. When these two layers are out of sync—most commonly after a fresh install, an OS upgrade to Windows Server 2025/Windows 11, or a restored configuration—the instance fails to initialize FILESTREAM and throws Error 5597.

Step-by-Step Resolution Guide

Step 1: Enable FILESTREAM in SQL Server Configuration Manager

  • Open SQL Server Configuration Manager (search for SQLServerManager17.msc or the version-specific equivalent for SQL Server 2025).
  • Navigate to SQL Server Services, right-click your instance (e.g., SQL Server (MSSQLSERVER)), and select Properties.
  • Go to the FILESTREAM tab and check all three boxes as needed:
  • “Enable FILESTREAM for Transact-SQL access”
  • “Enable FILESTREAM for file I/O streaming access”
  • “Allow remote clients to have streaming access to FILESTREAM data” (if required)
  • Click Apply, then OK.

Step 2: Enable FILESTREAM at the SQL Server Instance Level

  • Open SQL Server Management Studio (SSMS) and connect to the affected instance.
  • Run the following T-SQL to enable FILESTREAM access at the instance level:
EXEC sp_configure 'filestream access level', 2;
RECONFIGURE;
  • Value 2 enables full Transact-SQL and Win32 streaming access; use 1 for T-SQL only access.

Step 3: Restart the SQL Server Service

  • Return to SQL Server Configuration Manager.
  • Right-click the SQL Server instance under SQL Server Services and select Restart.
  • Alternatively, restart via PowerShell with elevated privileges:
Restart-Service -Name 'MSSQLSERVER' -Force

Step 4: Verify Windows Group Policy and Local Security Settings

  • On Windows Server 2025/Windows 11, confirm no Group Policy Object (GPO) is blocking filesystem-level streaming or WMI access required by Configuration Manager.
  • Check Local Security Policy > Local Policies > User Rights Assignment to ensure the SQL Server service account has sufficient privileges (e.g., “Log on as a service”).
  • If running in a domain environment, confirm with the Active Directory administrator that no domain-level policy is overriding local FILESTREAM settings.

Step 5: Check File System Share Name Conflicts

  • If FILESTREAM still fails, verify there isn’t a naming conflict with the Windows file share used for FILESTREAM data.
  • Open Computer Management > Shared Folders > Shares and ensure no duplicate or orphaned shares conflict with the FILESTREAM share name configured in SQL Server.

Alternative or Verification Steps

  • Verify the fix by running SELECT * FROM sys.configurations WHERE name = 'filestream access level'; in SSMS — the value_in_use column should reflect 1 or 2 matching your Configuration Manager setting.
  • If the error persists after a restart, check the SQL Server Error Log (ERRORLOG file, typically located in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\) for additional details on which layer (OS vs. instance) is still misconfigured.