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

by

Troubleshooting Guide: SQL Server Error 1432 – Database Mirroring Page Repair Request

Why This Error Happens

This error occurs when SQL Server detects a corrupted or unreadable physical page in a mirrored database and automatically attempts to self-heal by requesting a clean copy of that page from the mirroring partner. The root cause is typically underlying storage corruption caused by faulty disk hardware, a failing RAID controller, or an improperly shut down volume on the Windows Server 2025 host. While Error 1432 itself is informational (indicating the automatic page repair process has started), it signals that something is actively damaging data pages at the I/O subsystem level.

Step-by-Step Resolution Guide

Step 1: Confirm the Page Repair Outcome

  • Check the SQL Server Error Log and Windows Event Viewer (Application Log) for a follow-up message, either Error 1433 (repair succeeded) or Error 1479/3414 (repair failed).
  • Run the following query to inspect the repair history:
SELECT * FROM msdb.dbo.suspect_pages;
  • If event_type = 5, the page was successfully repaired and no further action is needed.

Step 2: Run DBCC CHECKDB to Assess Full Database Integrity

  • Open SQL Server Management Studio (SSMS) or a terminal with sqlcmd on the Principal server.
  • Execute a full consistency check to rule out additional corruption beyond the single flagged page:
DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • Review the output for allocation or consistency errors that may require REPAIR_ALLOW_DATA_LOSS (only as a last resort on a non-mirrored copy).

Step 3: Inspect the Underlying Storage Subsystem

  • Navigate to Windows Server Manager > Tools > Event Viewer > Windows Logs > System, and filter for Disk, Ntfs, or iScsiPrt source warnings/errors.
  • On Windows Server 2025, run Get-PhysicalDisk | Get-StorageReliabilityCounter in PowerShell to check for read/write error counts on the drive hosting the .mdf/.ldf files.
  • If using virtualized storage, verify the underlying SAN/NAS or vDisk health through the hypervisor management console (e.g., Hyper-V Manager or VMware vCenter).

Step 4: Validate the Mirroring Endpoint and Network Health

  • Confirm the mirroring endpoint is healthy by checking sys.database_mirroring_endpoints on both Principal and Mirror instances.
  • Ensure no firewall rules on Windows Server 2025 (Windows Defender Firewall with Advanced Security) are intermittently blocking the mirroring port (default 5022), which can delay page-repair data transfer.
  • Verify the mirroring session state using:
SELECT mirroring_state_desc, mirroring_safety_level_desc FROM sys.database_mirroring;

Step 5: Patch and Update SQL Server 2025

  • Apply the latest Cumulative Update (CU) for SQL Server 2025 via Microsoft Update or the SQL Server Installation Center, as page-repair logic and storage I/O handling are frequently refined in servicing releases.
  • Restart the SQL Server service (net stop MSSQLSERVER / net start MSSQLSERVER) after patching to ensure the update takes effect.

Alternative or Verification Steps

  • Verify the fix by re-running DBCC CHECKDB on the affected database and confirming zero allocation/consistency errors, and query msdb.dbo.suspect_pages to ensure no new rows are added over a 24-48 hour monitoring window.
  • If automatic page repair continues to fail repeatedly, consider failing over to the Mirror server (ALTER DATABASE YourDatabaseName SET PARTNER FAILOVER) and performing a full disk/hardware diagnostic on the original Principal server before failing back.