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

by

Troubleshooting Guide: Error 5561 — FILESTREAM Garbage Collector Operation Aborted

Why This Error Happens

This error occurs when SQL Server’s FILESTREAM garbage collector is interrupted before it can finish removing orphaned FILESTREAM data files from the filesystem. The most common root causes are a database shutdown, failover, or backup/restore operation occurring mid-cleanup cycle, as well as insufficient NTFS permissions on the FILESTREAM data container that prevent the garbage collector thread from deleting stale files. In some cases, antivirus or third-party backup agents locking files inside the FILESTREAM container can also abort the operation.

Step-by-Step Resolution Guide

Step 1: Verify FILESTREAM Service and Share Configuration

  • Open SQL Server Configuration Manager and confirm FILESTREAM is enabled for the relevant SQL Server 2025 instance under the FILESTREAM tab.
  • Ensure “Allow remote clients access to FILESTREAM data” is checked if accessed over the network.
  • Restart the SQL Server service only if a configuration change was made: net stop MSSQLSERVER && net start MSSQLSERVER.

Step 2: Check NTFS Permissions on the FILESTREAM Container

  • Navigate to the physical path of the FILESTREAM filegroup (e.g., D:\SQLData\FileStreamContainer\).
  • Right-click the folder, go to Properties > Security, and confirm the SQL Server service account has Full Control.
  • Also verify the NT SERVICE\MSSQLSERVER account is not blocked by inherited Group Policy restrictions on Windows Server 2025.

Step 3: Manually Trigger Garbage Collection

  • Run CHECKPOINT followed by a manual garbage collection trigger using the internal stored procedure: 
  EXEC sp_filestream_force_garbage_collection N'YourDatabaseName';
  • Monitor SQL Server error logs for confirmation the GC cycle completed without a new abort message.

Step 4: Rule Out File Locking by External Processes

  • Temporarily exclude the FILESTREAM data folder from antivirus real-time scanning.
  • Check for open file handles using Resource Monitor or handle.exe (Sysinternals) against the FILESTREAM container path.
  • Pause any third-party backup agents during the next scheduled GC window to confirm they aren’t holding file locks.

Step 5: Rebuild or Repair Orphaned FILESTREAM Data (If Persistent)

  • If the error recurs consistently, take the database offline, run DBCC CHECKDB with FILESTREAM validation, and inspect for orphaned pointers.
  • As a last resort, detach and reattach the database, allowing the garbage collector to perform a full consistency pass during the next automatic cleanup cycle.

Alternative or Verification Steps

  • Check the SQL Server Error Log and Windows Event Viewer (Application log) to confirm Error 5561 no longer appears after the next automatic FILESTREAM GC cycle (typically triggered on checkpoint).
  • If the issue persists, as an alternative, migrate the FILESTREAM filegroup to a new volume with fresh NTFS permissions and re-run sp_filestream_force_garbage_collection to validate cleanup completes successfully.