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

by

Troubleshooting Guide: SQL Server Error 5184 – Clustered File Resource Dependency Failure

Why This Error Happens

Error 5184 occurs when SQL Server 2025, running as a clustered instance, attempts to create or access a database file located on a disk that is not registered as a dependency resource of the SQL Server cluster role. This typically happens during database creation, file moves, or restores where the target path points to a volume outside the cluster group’s ownership, or the physical disk resource has failed to come online in Failover Cluster Manager. Additionally, this can surface if Storage Spaces Direct (S2D) volumes or CSV (Cluster Shared Volumes) paths are misconfigured and not properly associated with the SQL Server resource dependency chain in Windows Server 2025.

Step-by-Step Resolution Guide

Step 1: Verify Disk Ownership in Failover Cluster Manager

  • Open Failover Cluster Manager on the active node.
  • Navigate to the specific Role hosting your SQL Server instance.
  • Check the Disks tab to confirm the target volume (e.g., E:\ or F:\) is listed as Online and owned by the current node.
  • If the disk is missing or offline, right-click it and select Bring Online.

Step 2: Add the Disk as a Dependency Resource

  • In Failover Cluster Manager, right-click the SQL Server resource (not the Network Name) under the Role.
  • Select Properties, then navigate to the Dependencies tab.
  • Click Insert and add the specific disk resource (e.g., “Cluster Disk 3”) that contains the path referenced in the error.
  • Click Apply and OK, ensuring no circular dependency errors are thrown.

Step 3: Correct the File Path in T-SQL

  • Verify the exact path syntax used in your CREATE DATABASE or ALTER DATABASE command.
  • Ensure the path matches the mount point exactly as seen in Disk Management (e.g., D:\MSSQL\Data\ vs. a nested mount point that isn’t clustered).
  • Re-run the query:
  ALTER DATABASE [YourDB] MODIFY FILE (NAME = YourDB_dat, FILENAME = 'D:\MSSQL\Data\YourDB.mdf');

Step 4: Restart the SQL Server Resource

  • Take the SQL Server resource offline via Failover Cluster Manager.
  • Bring the resource back online to force it to re-read the updated dependency tree.
  • Monitor the Cluster Events log for any immediate re-triggering of Error 5184.

Alternative or Verification Steps

  • Verification: Attempt a test failover of the SQL Server role to a secondary node; if the disk and database move successfully without manual intervention, the dependency is correctly configured.
  • Alternative: If the disk cannot be added as a cluster resource (e.g., it is a local, non-shared disk), move the database files to a Cluster Shared Volume (CSV) or a dedicated clustered disk resource instead of a local server path.