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

by

Troubleshooting Guide: Error 5598 — FILESTREAM Feature Not Supported on User Instances

Why This Error Happens

Error 5598 occurs because FILESTREAM functionality is architecturally incompatible with SQL Server User Instances, a lightweight instance type typically spun up by SQL Server Express for non-administrative users. Since User Instances do not have access to the full instance-level configuration required to manage FILESTREAM’s integration with the Windows NTFS file system, any attempt to enable or use FILESTREAM within this context is rejected. This is not a bug but a hard architectural limitation enforced by the SQL Server Database Engine on Windows Server 2025 / Windows 11.

Step-by-Step Resolution Guide

Step 1: Disable User Instance Connections

  • Locate your application’s connection string (often in web.config, app.config, or a .json settings file).
  • Remove or set the User Instance=True; parameter to User Instance=False;.
  • Example corrected string: Server=.\SQLEXPRESS;Database=MyDB;Integrated Security=True;User Instance=False;

Step 2: Enable FILESTREAM at the Instance Level

  • Open SQL Server Configuration Manager on Windows Server 2025 / Windows 11.
  • Navigate to SQL Server Services, right-click your target instance (e.g., SQL Server (MSSQLSERVER)), and select Properties.
  • Go to the FILESTREAM tab and check:
  • “Enable FILESTREAM for Transact-SQL access”
  • “Enable FILESTREAM for file I/O streaming access”
  • Click Apply, then restart the SQL Server service for changes to take effect.

Step 3: Configure FILESTREAM via T-SQL

  • Open SQL Server Management Studio (SSMS) and connect to a standard (non-user) instance.
  • Run the following script to enable FILESTREAM access level at the engine level:
  EXEC sp_configure filestream_access_level, 2;
  RECONFIGURE;
  • Ensure you are connecting via a standard named instance (e.g., SERVERNAME\SQLEXPRESS) rather than the |DataDirectory| user-instance shortcut often used in Visual Studio/Express projects.

Step 4: Migrate to a Standard Named Instance

  • If your project relies on a local .mdf file via User Instance for portability, migrate the database to a fully managed Standard or Express instance.
  • Use the Attach Database feature in SSMS to attach the .mdf and .ldf files to the standard instance manually.
  • Update your connection string to point directly to this new instance name rather than using the dynamic user-instance file path.

Alternative or Verification Steps

  • Verify the Fix: Run SELECT SERVERPROPERTY('FilestreamConfiguredLevel'); in SSMS. A return value of 2 or 3 confirms FILESTREAM is active at the instance level and ready for use.
  • Alternative Solution: If User Instances are required for your specific lightweight deployment scenario, consider storing large binary objects (BLOBs) using standard VARBINARY(MAX) columns instead of FILESTREAM, as this data type does not carry the same User Instance restrictions.