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

by

Troubleshooting Guide: SQL Server Error 5592 – FILESTREAM Access Not Enabled

Why This Error Happens

Error 5592 occurs when an application or T-SQL statement attempts to use FILESTREAM functionality, but the feature has not been enabled at the Windows OS level and/or within the SQL Server instance configuration. By default, FILESTREAM is disabled during a standard SQL Server 2025 installation because it requires explicit file system access permissions that Windows does not grant automatically for security reasons. Without enabling both the SQL Server Configuration Manager setting and the corresponding sp_configure database engine option, SQL Server blocks any attempt to create or access FILESTREAM-enabled filegroups.

Step-by-Step Resolution Guide

Step 1: Enable FILESTREAM in SQL Server Configuration Manager

  • Open SQL Server Configuration Manager (search for sqlservermanager16.msc or locate it via Start Menu on Windows Server 2025/Windows 11).
  • 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:
  • Enable FILESTREAM for Transact-SQL access
  • Enable FILESTREAM for file I/O streaming access
  • Allow remote clients access to FILESTREAM data (if network access is required)
  • Set the Windows share name (default is MSSQLSERVER) and click Apply.

Step 2: Enable FILESTREAM Access Level via T-SQL

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

Step 3: Restart the SQL Server Service

  • Restart the SQL Server service to apply the configuration changes:
Restart-Service -Name 'MSSQLSERVER' -Force
  • If using a named instance, replace MSSQLSERVER with MSSQL$<InstanceName>.
  • Verify Windows Firewall rules are not blocking the file share path (\\<ServerName>\MSSQLSERVER) if remote access is enabled.

Step 4: Validate Folder and Share Permissions

  • Ensure the SQL Server service account has Full Control permissions on the FILESTREAM data folder path.
  • Check via File Explorer → right-click the target folder → Properties → Security tab, and confirm the service account (e.g., NT SERVICE\MSSQLSERVER) is listed with appropriate permissions.

Alternative or Verification Steps

  • Run SELECT SERVERPROPERTY('FilestreamConfiguredLevel'); in SSMS — a return value of 2 confirms FILESTREAM is fully enabled.
  • If the error persists, try creating a test database with a FILESTREAM filegroup using a local path (e.g., C:\FSData) to rule out network share or permission conflicts as the alternative root cause.