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

by

Troubleshooting Guide: SQL Server Error 5577 (FILESTREAM Access Level Change)

Why This Error Happens

Error 5577 is an informational message that occurs when the FILESTREAM access level is modified via SQL Server Configuration Manager, sp_configure, or SSMS, but the change has not yet been fully applied because the SQL Server service has not been restarted. SQL Server caches the FILESTREAM access level at startup, so any modification to this registry/configuration value only partially applies until the service is cycled. This often happens after an administrator enables FILESTREAM support for Transact-SQL access or remote client access but forgets to restart the instance, leaving the server in an inconsistent state where new FILESTREAM operations may fail intermittently.

Step-by-Step Resolution Guide

Step 1: Verify the Current FILESTREAM Configuration Level

  • Open SQL Server Management Studio (SSMS) and connect to the Windows Server 2025 / Windows 11 instance.
  • Run the following query to check the current system-level setting:
  EXEC sp_configure 'filestream access level';
  • Confirm the run_value matches the intended level (0 = Disabled, 1 = T-SQL access enabled, 2 = Full access enabled for local and remote clients).

Step 2: Reconcile the Configuration Manager and SQL Setting

  • 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., SQL Server (MSSQLSERVER)) > Properties > FILESTREAM tab.
  • Ensure the checkbox for “Enable FILESTREAM for Transact-SQL access” (and “Enable remote client access” if needed) matches the sp_configure value set in Step 1.
  • Click Apply to sync the Windows-level and SQL-level settings.

Step 3: Restart the SQL Server Service

  • Open Services.msc or use Configuration Manager to restart the instance.
  • Alternatively, use PowerShell as Administrator:
  Restart-Service -Name 'MSSQLSERVER' -Force
  • If using a named instance, replace MSSQLSERVER with MSSQL$<InstanceName>.

Step 4: Confirm FILESTREAM Registry Settings (If Error Persists)

  • Open regedit and navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL17.MSSQLSERVER\Filestream
  • Verify the EnableLevel DWORD value matches the level set in SSMS (0, 1, or 2).
  • If mismatched, manually correct the DWORD value and restart the SQL Server service again.

Alternative or Verification Steps

  • Run EXEC sp_configure 'filestream access level'; again after the restart to confirm config_value and run_value are now identical—this confirms the change is fully active.
  • If the error recurs on every restart, check for Group Policy Objects (GPOs) or third-party security tools on Windows Server 2025 that may be reverting the FILESTREAM registry key, and exclude the SQL Server registry path from policy enforcement.