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

by

Troubleshooting Guide: SQL Server Error 13175 – Version Mismatch

Why This Error Happens

Error 13175 in SQL Server 2025 typically occurs when there is a version incompatibility between the SQL Server Polybase/external data components and the underlying Hadoop or external data source connector being referenced. This can result from mismatched DLL versions after an incomplete update, corrupted PolyBase configuration files, or a failed cumulative update installation that left legacy binaries in place. Additionally, this error may surface when Windows Server 2025 security policies block access to version metadata required by SQL Server’s external services layer.

Step-by-Step Resolution Guide

Step 1: Verify SQL Server Build and Patch Level

  • Open SQL Server Management Studio (SSMS) and run: SELECT @@VERSION;
  • Compare the returned build number against the official Microsoft SQL Server 2025 release notes to confirm you are on a supported, fully patched build.
  • If outdated, download the latest Cumulative Update (CU) from the Microsoft Update Catalog and apply it.

Step 2: Repair or Reinstall PolyBase/External Data Components

  • Navigate to Control Panel > Programs > Programs and Features.
  • Locate Microsoft SQL Server 2025, right-click, and select Change.
  • Choose the Repair option for the PolyBase Query Service and External Data components.
  • Restart the service via PowerShell: Restart-Service MSSQLSERVER -Force

Step 3: Clear Corrupted Configuration Cache

  • Stop the SQL Server service from SQL Server Configuration Manager.
  • Navigate to C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Binn\Polybase\Settings\ (adjust instance folder name as needed).
  • Rename the polybase.settings file to polybase.settings.bak to force regeneration on restart.
  • Restart the SQL Server and PolyBase Data Movement services.

Step 4: Validate Windows Server Permissions

  • Open Local Security Policy (secpol.msc) on Windows Server 2025.
  • Ensure the SQL Server service account has “Log on as a service” rights under Local Policies > User Rights Assignment.
  • Confirm the account also has read/write access to the SQL Server installation directory to prevent version-check failures.

Alternative or Verification Steps

  • To verify the fix, re-run the failing query or data import job and check the SQL Server Error Log (ERRORLOG file in the Log subfolder) for the absence of Error 13175.
  • If the error persists, consider performing a full uninstall of the PolyBase feature followed by a clean reinstall via the SQL Server Installation Center, ensuring no orphaned registry keys remain under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\PolyBase.