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

by

Troubleshooting Guide: SQL Server Error 13084

Why This Error Happens

Error 13084 in Microsoft SQL Server 2025 typically occurs when the Service Broker or internal activation task encounters an issue writing data to the message queue or transport layer, often due to insufficient disk space, corrupted database files, or restrictive file system permissions on the SQL Server data directory. This can also surface when Windows Server 2025 security policies (such as Controlled Folder Access or third-party antivirus software) block SQL Server’s write operations to its default data path. In some cases, a mismatch between the SQL Server service account permissions and the NTFS ACLs on the database files prevents the write transaction from completing successfully.

Step-by-Step Resolution Guide

Step 1: Verify Disk Space and File System Health

  • Open File Explorer and check available space on the drive hosting your SQL Server data files (commonly C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA).
  • Run chkdsk C: /f /r from an elevated Command Prompt to scan for and repair file system corruption.
  • Restart the server if chkdsk requires a reboot to complete the scan.

Step 2: Check and Reset NTFS Permissions on SQL Data Directory

  • Right-click the SQL Server DATA folder, go to Properties > Security, and confirm the NT SERVICE\MSSQLSERVER account has Full Control.
  • If permissions are missing, click Edit, add the service account, and grant Full Control.
  • Apply changes recursively using: icacls "C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA" /grant "NT SERVICE\MSSQLSERVER:(OI)(CI)F" /T

Step 3: Disable Controlled Folder Access or Antivirus Interference

  • Navigate to Windows Security > Virus & threat protection > Manage ransomware protection.
  • Turn off Controlled Folder Access temporarily, or add sqlservr.exe as an allowed app.
  • If using third-party antivirus, add the SQL Server DATA and LOG directories to the exclusion list.

Step 4: Restart SQL Server Services and Validate Configuration

  • Open SQL Server Configuration Manager, right-click SQL Server (MSSQLSERVER), and select Restart.
  • Check the SQL Server Error Log (ERRORLOG file in the LOG directory) for confirmation that Error 13084 no longer appears.
  • Run DBCC CHECKDB against the affected database to confirm there is no underlying corruption.

Alternative or Verification Steps

  • Run a test write transaction via SQL Server Management Studio (SSMS) using INSERT INTO on a sample table and confirm it commits without triggering Error 13084 in the logs.
  • If the issue persists, restore the affected database from a known-good backup and reapply transaction logs to rule out deep-seated file corruption.