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

by

Troubleshooting Guide: SQL Server Error 1480 – Database Role Change Due to Failover

Why This Error Happens

Error 1480 is an informational message, not a critical failure, and is logged whenever a database participating in a Database Mirroring session or an Availability Group (AG) transitions roles (e.g., from Primary to Secondary) due to an automatic or manual failover. This typically occurs because of a loss of connectivity between replicas, a manual failover triggered by an administrator, a Windows Server Failover Clustering (WSFC) quorum event, or the primary replica becoming unresponsive due to resource exhaustion (CPU, memory, or I/O). While the message itself requires no action, frequent, unexpected occurrences often point to underlying network instability or health detection thresholds being too sensitive.

Step-by-Step Resolution Guide

Step 1: Confirm the Failover Was Expected

  • Open the SQL Server Error Log or Always On Dashboard in SSMS to check the timestamp of the role change.
  • Cross-reference the time with any planned maintenance, patching via Windows Update, or manual failover commands (ALTER AVAILABILITY GROUP ... FAILOVER).
  • If the failover was intentional (e.g., patching Windows Server 2025 nodes), no further action is needed.

Step 2: Investigate Network Latency and Cluster Health

  • Check the Windows Server Failover Cluster (WSFC) logs located via Get-ClusterLog -Destination C:\ClusterLogs in PowerShell to look for missed heartbeats between nodes.
  • Verify the network connection between the Primary and Secondary replicas is stable by running Test-Connection or ping -t to the partner server during peak load times.
  • Review the Lease Timeout and Session Timeout settings in the Availability Group properties; a default of 10 seconds might be too aggressive for high-latency WAN environments.

Step 3: Review Resource Utilization on the Former Primary

  • Open Performance Monitor (PerfMon) on the server that lost primary status and check counters for Processor Time, Available MBytes, and Avg. Disk sec/Transfer around the time of the event.
  • If the server was unresponsive due to high memory pressure, adjust the max server memory setting in SQL Server Configuration Manager to leave sufficient headroom for the OS.
  • Check Windows Event Viewer under System logs for any corresponding hardware or driver-level errors (Event ID 153 or 157) that might explain the unresponsiveness.

Step 4: Adjust Flexible Failover Policy (If Applicable)

  • Navigate to the Availability Group properties in SSMS and select the Backup Preferences or Failure Conditions tab.
  • If failovers are happening too easily due to transient issues, consider changing the Flexible Failover Policy from a lower level (e.g., “On any qualified failure condition”) to “On server down” (Level 1) to reduce sensitivity.
  • Apply the changes and restart the SQL Server Agent service to ensure the new policy takes effect immediately.

Alternative or Verification Steps

  • Verify the Fix: Query the DMV sys.dm_hadr_database_replica_states on the current primary replica to confirm is_local and role_desc columns show the expected “PRIMARY” status with a synchronization_health of “HEALTHY.”
  • Alternative Check: If failovers continue intermittently, use sp_server_diagnostics to capture internal component health states, which can reveal if the SQL Server resource DLL is flagging false positives to the Cluster service.