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

by

Troubleshooting Guide: SQL Server Error 3061 – Restart-Checkpoint File Could Not Be Opened

Why This Error Happens

This error occurs when SQL Server 2025 attempts a backup or restore operation and cannot access the restart-checkpoint file, typically because the file path is unreachable, the file has been moved or deleted, or the SQL Server service account lacks the necessary NTFS permissions. It can also surface when the underlying storage volume (local disk, network share, or cloud-backed storage) is offline, disconnected, or experiencing I/O contention. In some cases, the file is locked by another process or antivirus/backup software is interfering with file access during the checkpoint operation.

Step-by-Step Resolution Guide

Step 1: Verify the File Path and Existence

  • Open File Explorer or a command prompt and navigate to the exact path referenced in the error message (the %ls placeholder in Error 3061).
  • Confirm the restart-checkpoint file (usually with a .chk or similar extension) actually exists at that location.
  • If the file is missing, check whether it was moved, renamed, or deleted by a cleanup script, retention policy, or manual intervention.
  • Run dir "C:\Path\To\Checkpoint\File" in Command Prompt to confirm visibility from the server’s perspective.

Step 2: Check and Correct NTFS Permissions

  • Right-click the folder containing the checkpoint file, select Properties > Security, and confirm the SQL Server service account (e.g., NT Service\MSSQLSERVER or a custom domain service account) has Read, Write, and Modify permissions.
  • If using a named instance, verify the correct service account under Services.msc (e.g., NT SERVICE\MSSQL$INSTANCENAME).
  • Apply permissions using PowerShell if needed:
  • icacls "C:\Backup\Checkpoint" /grant "NT SERVICE\MSSQLSERVER:(OI)(CI)F"
  • Restart the SQL Server service after applying permission changes.

Step 3: Validate Network Share and Storage Availability

  • If the checkpoint file resides on a UNC path (e.g., \\FileServer\Backups\), test connectivity using Test-NetConnection FileServer -Port 445 in PowerShell.
  • Ensure the network share is online and that the SQL Server service account has delegated access to the remote share (not just local NTFS permissions).
  • Check Windows Server 2025 Storage Spaces or SAN/NAS connectivity if using mapped drives or iSCSI targets, and confirm no drive letter remapping occurred after a reboot.

Step 4: Rule Out File Locks and Antivirus Interference

  • Use Process Explorer (Sysinternals) to check if another process (e.g., antivirus, backup agent) has an open handle on the checkpoint file.
  • Temporarily disable real-time antivirus scanning on the SQL Server backup/data directories to test if this resolves the issue.
  • Add SQL Server data, log, and backup directories to your antivirus exclusion list permanently to prevent future locking conflicts.

Step 5: Restart the Backup or Restore Operation

  • Once permissions, connectivity, and file locks are resolved, re-issue the original BACKUP or RESTORE T-SQL command.
  • Monitor SQL Server Error Logs (via SSMS Management > SQL Server Logs) to confirm Error 3061 no longer appears.

Alternative or Verification Steps

  • Run the backup/restore command manually in SSMS and check for successful completion without Error 3061 appearing in the SQL Server Error Log or Windows Event Viewer.
  • If the issue persists, specify a new, freshly created checkpoint file path with WITH CHECKPOINT = 'C:\NewPath\restart.chk' to bypass potential corruption in the original file location.