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

by

Troubleshooting Guide: SQL Server Error 886 — Resilient Buffer Pool Extension

Why This Error Happens

Error 886 is an informational message rather than a critical failure. It occurs when SQL Server 2025 detects that the Resilient Buffer Pool Extension (RBPEX) feature is already in an enabled state or is currently in the process of initializing during startup or recovery. This typically happens when a configuration script or startup trace flag attempts to re-enable the feature while a prior instance restart or failover (in an Always On Availability Group) has not yet fully completed the initialization handshake.

Step-by-Step Resolution Guide

Step 1: Verify Current Buffer Pool Extension Status

  • Open SQL Server Management Studio (SSMS) and connect to the instance.
  • Run the following query to check the current state:
  SELECT * FROM sys.dm_os_buffer_pool_extension_configuration;
  • Look at the state_description column; if it shows RUNNING, no action is required as the system is functioning as intended.

Step 2: Check for Redundant Startup Configurations

  • Navigate to the SQL Server configuration files located at:
    C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG
  • Search for duplicate ALTER SERVER CONFIGURATION SET BUFFER POOL EXTENSION commands in your deployment or Powershell provisioning scripts.
  • Remove or comment out redundant initialization scripts that attempt to enable the extension on every service restart.

Step 3: Clear Pending Recovery States (If Applicable)

  • If the error persists alongside connectivity issues, restart the SQL Server service to clear any “pending” initialization locks.
  • Open Services.msc on Windows Server 2025, locate SQL Server (MSSQLSERVER), and select Restart.
  • Ensure the .BPE file path defined in your configuration (usually on a high-speed SSD drive) is accessible and not locked by another process.

Step 4: Review Always On Availability Group Sync (If Clustered)

  • If running in a High Availability setup, check the Failover Cluster Manager to ensure the resource is not stuck in a “pending” state.
  • Confirm that the Buffer Pool Extension configuration is synchronized across all secondary replicas to prevent a conflict message during failover events.

Alternative or Verification Steps

  • Verification: Re-run the sys.dm_os_buffer_pool_extension_configuration query. If state equals 2 (Running), the feature is stable and the Error 886 message can be safely ignored as a benign notification.
  • Alternative: If instability continues, manually disable and re-enable the feature via a single ALTER SERVER CONFIGURATION SET BUFFER POOL EXTENSION OFF; command, followed by a service restart, before re-enabling it with a fresh file path.