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

by

Troubleshooting Guide: SQL Server Error 10025 — “Provider Caused a Server Fault in an External Process”

Why This Error Happens

This error typically occurs when SQL Server 2025 communicates with an external OLE DB provider or linked server component that crashes or becomes unresponsive, often due to a corrupted or outdated provider DLL. It can also stem from insufficient permissions on the external process account (especially under the new Windows Server 2025 process isolation model) or from the external provider attempting to access memory/resources blocked by enhanced security sandboxing. In many cases, a mismatch between the 64-bit SQL Server engine and a 32-bit (or incompatible) external provider triggers this fault.

Step-by-Step Resolution Guide

Step 1: Verify and Reinstall the External Provider

  • Open SQL Server Management Studio (SSMS) and check linked server properties under Server Objects > Linked Servers.
  • Confirm the OLE DB provider (e.g., MSOLEDBSQL, Microsoft.ACE.OLEDB.16.0) is installed and matches SQL Server’s architecture (64-bit).
  • Reinstall the provider from the official Microsoft Download Center if corruption is suspected.
  • Run sc query MSSQLSERVER to confirm the SQL Server service is running normally post-reinstall.

Step 2: Adjust Provider and Process Isolation Settings

  • Navigate to Server Objects > Linked Servers > Providers in SSMS, right-click the provider, and enable “Allow inprocess” only if the provider is stable; otherwise, leave it disabled to force out-of-process isolation.
  • Under Windows Server 2025’s enhanced App Container sandboxing, verify the SQL Server service account has explicit permissions via Component Services > DCOM Config for the provider in question.
  • Restart the SQL Server service: Restart-Service -Name MSSQLSERVER -Force (PowerShell, run as Administrator).

Step 3: Check Windows Event Viewer and Dump Files

  • Open Event Viewer > Windows Logs > Application and filter for Event ID 10025.
  • Correlate the timestamp with any .mdmp (mini-dump) files located in C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\LOG\.
  • Review the dump using WinDbg or send it to Microsoft Support if the stack trace points to a third-party DLL.

Step 4: Update SQL Server and OS Patches

  • Confirm you are running the latest Cumulative Update (CU) for SQL Server 2025 via SELECT @@VERSION;.
  • Apply any pending Windows Updates via Settings > Windows Update, specifically security patches affecting COM/DCOM and process isolation.
  • Reboot the server and re-test the failing query or linked server connection.

Alternative or Verification Steps

  • Run the original query or linked server call again and confirm no Error 10025 appears in sys.dm_os_ring_buffers or the SQL Server error log (EXEC sp_readerrorlog;).
  • If the issue persists, bypass the external provider temporarily by using OPENROWSET with a different, verified driver to isolate whether the fault is provider-specific or SQL Server configuration-specific.