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

by

Troubleshooting Guide: Error 4347 – Restore Sequence Interrupted During Online Transition

Why This Error Happens

This error occurs when a SQL Server restore operation (typically involving NORECOVERY mode) is interrupted before it can complete the final transition to an online state, leaving the database in a RESTORING state indefinitely. Common causes include a terminated restore script, a dropped network connection during a long-running restore job, or an administrator manually cancelling the operation mid-process. The database engine detects that the transaction rollforward/rollback phase never finished, so it blocks access until the recovery process is explicitly completed or restarted.

Step-by-Step Resolution Guide

Step 1: Verify the Current Database State

  • Open SQL Server Management Studio (SSMS) or a query window and run: SELECT name, state_desc FROM sys.databases WHERE name = 'YourDatabaseName';
  • Confirm the state_desc column shows RESTORING.
  • Check the SQL Server Error Log (via EXEC sp_readerrorlog; or C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) to identify exactly when and why the previous restore was interrupted.

Step 2: Complete the Recovery Manually

  • Run the following T-SQL command to force the database to finish its transition to online: RESTORE DATABASE [YourDatabaseName] WITH RECOVERY;
  • Ensure no other restore jobs (via SQL Agent or third-party backup tools) are queued to run against this same database, as a conflicting job could trigger the interruption again.
  • If a backup chain is still incomplete (e.g., you intended to apply more differential or log backups), do not run this command yet, as WITH RECOVERY will prevent any further files from being restored to this database.

Step 3: Restart the Restore Sequence (If Recovery Fails)

  • If running WITH RECOVERY fails or the database remains inaccessible, drop the corrupted restore state by executing: RESTORE DATABASE [YourDatabaseName] FROM DISK = 'C:\Backups\YourFullBackup.bak' WITH REPLACE, NORECOVERY;
  • Re-apply any necessary differential or transaction log backups in the correct sequence (full → differential → log).
  • Finish the sequence immediately with: RESTORE DATABASE [YourDatabaseName] WITH RECOVERY; once all files are applied, without interruption this time.

Step 4: Check for Underlying System Interruptions

  • On Windows Server 2025/Windows 11, check Event Viewer under Windows Logs > System for unexpected service restarts (Event ID 7034 or 7036 for SQL Server (MSSQLSERVER)).
  • Verify there was no disk I/O timeout or storage disconnection in Windows Logs > Application during the original restore window, as this is a common cause of interrupted restores on virtualized or cloud-hosted instances.
  • Confirm the SQL Server Agent or backup service account has stable network connectivity if restoring from a UNC path or network share.

Alternative or Verification Steps

  • Verify the fix: Run SELECT state_desc FROM sys.databases WHERE name = 'YourDatabaseName'; again — a successful fix will show the state as ONLINE.
  • Alternative solution: If WITH RECOVERY continuously fails due to file corruption, restore the full backup to a new database name using WITH MOVE to validate backup file integrity before attempting to overwrite the original production database.