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

by

Troubleshooting Guide: SQL Server Error 5544 (FILESTREAM Remote Access Enabled)

Why This Error Happens

This message is logged when the FILESTREAM feature on SQL Server 2025 is configured with an “effective level” that permits remote client access to FILESTREAM data, typically because the FILESTREAM access level was set to a value of 2 (full remote access) either via SQL Server Configuration Manager or through the sp_configure 'filestream access level' setting. While technically informational rather than a fatal error, it often surfaces unexpectedly when a Group Policy Object (GPO) or a Windows Server 2025 security baseline forces a Windows Firewall rule change, or when the FILESTREAM share is exposed on a network interface that administrators did not intend to expose. This typically indicates a mismatch between the intended security posture (local-only access) and the actual running configuration (remote access enabled), which can trigger compliance or security scanning alerts.

Step-by-Step Resolution Guide

Step 1: Verify the Current FILESTREAM Configuration Level

  • Open SQL Server Management Studio (SSMS) and connect to the instance reporting Error 5544.
  • Run the following query to check the current server-level setting:
  • EXEC sp_configure 'filestream access level';
  • A run_value of 2 confirms remote access is currently enabled, matching the error message.

Step 2: Adjust the FILESTREAM Access Level via Configuration Manager

  • Open SQL Server Configuration Manager (search for SQLServerManager17.msc on Windows Server 2025/Windows 11).
  • Navigate to SQL Server Services, right-click your instance (e.g., MSSQLSERVER), and select Properties.
  • Go to the FILESTREAM tab and uncheck “Allow remote clients to have streaming access to FILESTREAM data” if remote access is not required.
  • Click Apply, then restart the SQL Server service for the change to take effect.

Step 3: Synchronize the Database Engine Configuration

  • Back in SSMS, run the T-SQL equivalent to match the Configuration Manager setting:
  • EXEC sp_configure 'filestream access level', 1; (use 1 for local-only, 0 to disable entirely, or 2 to intentionally keep remote access)
  • RECONFIGURE;
  • Restart the SQL Server (MSSQLSERVER) service via services.msc or net stop MSSQLSERVER && net start MSSQLSERVER.

Step 4: Review Windows Firewall and Share Permissions

  • If remote access is genuinely required, ensure Windows Firewall on Windows Server 2025 allows traffic on the File Server Remote Management (SMB-In) rule rather than opening all SMB ports broadly.
  • Check the FILESTREAM share name via sp_configure or Configuration Manager’s “Windows share name” field and confirm NTFS/Share permissions are scoped only to required service accounts.

Alternative or Verification Steps

  • After restarting the service, re-run EXEC sp_configure 'filestream access level'; and confirm the run_value column matches your intended setting (0, 1, or 2).
  • If the error persists in the SQL Server Error Log despite configuration changes, check for conflicting Group Policy settings under Computer Configuration > Administrative Templates > Windows Components that may be overriding local FILESTREAM share settings on reboot.