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

by

Troubleshooting Guide: Error 3223 – Backup To URL Failed to Write Status Messages

Why This Error Happens

Error 3223 occurs when SQL Server 2025 cannot write backup progress and status messages to the Windows operating system error log, typically because the SQL Server service account lacks sufficient permissions on the event log or the target log file is locked, full, or corrupted. This issue is also commonly triggered when the Backup To URL operation is running against a blocked or unreachable Azure Blob Storage endpoint, causing the logging subsystem to time out while attempting to record status updates. In some cases, Windows Event Log service itself may be disabled, throttled, or experiencing disk space constraints on Windows Server 2025, preventing any application—including SQL Server—from writing new entries.

Step-by-Step Resolution Guide

Step 1: Verify SQL Server Service Account Permissions

  • Open Services.msc and confirm the account running “SQL Server (MSSQLSERVER)” has local administrator or “Generate security audits” rights.
  • Navigate to Local Security Policy > User Rights Assignment and ensure the service account is listed under “Manage auditing and security log.”
  • Restart the SQL Server service after applying permission changes.

Step 2: Check Windows Event Log Service Health

  • Run Get-Service EventLog in PowerShell to confirm the Windows Event Log service is running.
  • If stopped, restart it using Start-Service EventLog or via services.msc.
  • Check available disk space on the volume hosting C:\Windows\System32\winevt\Logs\ — ensure at least 500MB free.
  • Clear or archive old logs using wevtutil cl Application if the log file has reached its maximum size.

Step 3: Validate Backup To URL Network and Credential Configuration

  • Confirm the SQL Server Credential object used for Backup To URL is valid by running:
  SELECT * FROM sys.credentials WHERE name = 'YourCredentialName';
  • Test connectivity to the Azure Blob Storage endpoint using Test-NetConnection -ComputerName yourstorageaccount.blob.core.windows.net -Port 443.
  • Re-issue the backup command with WITH STATS = 10 to monitor incremental progress and isolate where logging fails.

Step 4: Repair or Reset the Application Event Log File

  • Navigate to C:\Windows\System32\winevt\Logs\Application.evtx.
  • Rename the corrupted file to Application.evtx.old while the Event Log service is stopped.
  • Restart the Windows Event Log service to regenerate a fresh Application.evtx file automatically.

Step 5: Update SQL Server 2025 Cumulative Update

  • Check the currently installed build number using:
  SELECT @@VERSION;
  • Download and apply the latest Cumulative Update (CU) from Microsoft, as early SQL Server 2025 builds contained a known logging race condition with Backup To URL operations.

Alternative or Verification Steps

  • After applying fixes, run a manual BACKUP DATABASE ... TO URL command and confirm Error 3223 no longer appears in SQL Server Error Log (via EXEC sp_readerrorlog) or Event Viewer > Windows Logs > Application.
  • As an alternative, redirect backup logging temporarily to a local disk backup (BACKUP DATABASE ... TO DISK) to confirm whether the issue is isolated to the URL/Blob Storage logging path rather than general OS log write failures.