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

by

Troubleshooting Guide: SQL Server Error 3085 – Database Freeze Suspend Lock Failure

Why This Error Happens

This error occurs when SQL Server attempts to freeze I/O on a database (typically during a VSS snapshot backup operation) but cannot acquire the necessary suspend locks within the required timeout window. This is usually caused by another process holding conflicting locks on the database files, insufficient permissions for the SQL Server service account, or a VSS writer/provider conflict on Windows Server 2025. It can also occur if the database is under heavy transactional load, preventing the I/O freeze from completing in time.

Step-by-Step Resolution Guide

Step 1: Verify SQL Server VSS Writer Status

  • Open an elevated Command Prompt and run vssadmin list writers.
  • Confirm that “SqlServerWriter” is listed with a state of [1] Stable and no error.
  • If the writer shows a failed or retryable state, restart the SQL Server VSS Writer service via services.msc.
  • Run net stop "SQL Server VSS Writer" followed by net start "SQL Server VSS Writer" to reset it cleanly.

Step 2: Check for Blocking Transactions or Long-Running Queries

  • Execute sp_who2 or query sys.dm_exec_requests to identify sessions holding locks on the target database.
  • Look specifically for open transactions with sys.dm_tran_active_transactions that may be delaying the freeze.
  • Terminate or wait out any long-running transactions using KILL <session_id> if safe to do so.
  • Re-run the backup/snapshot operation immediately after clearing blocking sessions.

Step 3: Validate Service Account Permissions

  • Confirm the SQL Server service account has Backup Operator or sufficient NTFS permissions on the data/log file directories (commonly C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\DATA).
  • Open sqlservr.exe service properties in services.msc and verify it is running under the correct domain or managed service account.
  • Grant “Perform volume maintenance tasks” and “Back up files and directories” rights via secpol.msc > Local Policies > User Rights Assignment.

Step 4: Increase the Freeze Timeout and Retry

  • If using a third-party backup tool or VSS requester, check its configuration for a freeze/thaw timeout setting (default is often 10 seconds).
  • Increase this value to 60 seconds in the backup software’s advanced settings.
  • Restart the backup job and monitor the SQL Server error log (ERRORLOG in the MSSQL\Log folder) for Event ID 3085 recurrence.

Step 5: Restart SQL Server Service and Dependent Services

  • If the issue persists, restart the full SQL Server service stack: SQL Server (MSSQLSERVER), SQL Server Agent, and SQL Server VSS Writer.
  • Use PowerShell: Restart-Service -Name 'MSSQLSERVER','SQLSERVERAGENT' -Force.
  • Re-attempt the snapshot or backup operation to confirm locks are now acquired successfully.

Alternative or Verification Steps

  • To verify the fix, run vssadmin list writers again and confirm “SqlServerWriter” reports No error, then successfully complete a full VSS-based backup without Error 3085 appearing in the SQL ERRORLOG.
  • As an alternative, switch to a native SQL Server backup method (BACKUP DATABASE ... TO DISK) instead of VSS snapshot-based backups to bypass the freeze/thaw mechanism entirely if third-party tooling continues to fail.