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

by

Troubleshooting Guide: Error 5517 – FILESTREAM Container MAXSIZE Must Be Greater Than or Equal to 512 KB

Why This Error Happens

This error occurs when attempting to create or alter a FILESTREAM filegroup with a MAXSIZE value set below the minimum threshold of 512 KB, which SQL Server 2025 enforces to ensure the container has sufficient space for metadata and initial file allocation. It commonly happens due to a typo in the size unit (e.g., specifying bytes instead of KB/MB) or when scripts are copied from older configurations without validating size parameters. Additionally, automated deployment scripts or DevOps pipelines that dynamically calculate storage sizes may pass a zero or near-zero value if a prior calculation step failed silently.

Step-by-Step Resolution Guide

Step 1: Review the T-SQL Script or Command Causing the Error

  • Locate the ALTER DATABASE or CREATE DATABASE statement containing the FILESTREAM filegroup definition.
  • Check the MAXSIZE parameter syntax, for example: MAXSIZE = 1024MB or MAXSIZE = UNLIMITED.
  • Verify no leading zeros, missing units, or decimal values are causing a silent rounding error below 512 KB.

Step 2: Correct the MAXSIZE Value

  • Update the script to explicitly set a value equal to or greater than 512 KB, such as:
  ALTER DATABASE [YourDB] 
  MODIFY FILE (NAME = FileStreamGroup1, MAXSIZE = 5120KB)
  • If the intention was unlimited growth, replace the clause with MAXSIZE = UNLIMITED instead of a hard-coded KB value.
  • Save the corrected script to C:\Scripts\SQL\FileStreamConfig.sql for version control purposes.

Step 3: Validate FILESTREAM Feature Configuration in SQL Server

  • Open SQL Server Configuration Manager on Windows Server 2025.
  • Navigate to SQL Server Services > right-click your instance > Properties > FILESTREAM tab.
  • Ensure “Enable FILESTREAM for Transact-SQL access” is checked, as a misconfigured feature can sometimes surface misleading size-related errors.

Step 4: Re-run the Database Creation or Alteration Script

  • Execute the updated script via SQL Server Management Studio (SSMS) or sqlcmd.
  • Example command line execution:
  sqlcmd -S localhost -i C:\Scripts\SQL\FileStreamConfig.sql
  • Confirm no Error 5517 appears in the Messages tab of SSMS output.

Step 5: Check Windows File System Permissions for the Container Path

  • Navigate to the FILESTREAM data folder (e.g., D:\SQLData\FileStreamContainer).
  • Right-click > Properties > Security tab, and confirm the SQL Server service account has Full Control.
  • Insufficient NTFS permissions can sometimes mask as size-allocation errors during container initialization.

Alternative or Verification Steps

  • Run sp_helpfile or query sys.database_files in SSMS to confirm the FILESTREAM filegroup now reflects the corrected MAXSIZE value.
  • If the error persists after correcting syntax, drop the FILESTREAM filegroup entirely and recreate it from scratch using a minimum safe value of MAXSIZE = 10240KB to rule out metadata corruption from the failed attempt.