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

by

Troubleshooting Guide: Error 6357 – Cannot Locate CreateInfoSetReaderEx in xmlrw.dll

Why This Error Happens

This error occurs when SQL Server’s XML parsing engine attempts to call a function exported by xmlrw.dll (or its 64-bit counterpart xmlrw64.dll) but finds either a missing, outdated, or mismatched version of the file. This is typically caused by a corrupted SQL Server installation, an incomplete patch/update cycle, or a conflicting third-party application that has overwritten the DLL with an incompatible version. It can also occur if the DLL exists but is not properly registered or sits in a directory not included in the system’s binary search path.

Step-by-Step Resolution Guide

Step 1: Verify the Existence and Version of xmlrw.dll

  • Navigate to the SQL Server binaries directory, typically C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Binn\ (adjust the version folder as needed for SQL Server 2025).
  • Right-click xmlrw.dll and xmlrw64.dll, select Properties > Details, and confirm the file version matches your installed SQL Server build number.
  • If the file is missing entirely, this confirms a corrupted or incomplete installation.

Step 2: Run a SQL Server Repair Operation

  • Open Control Panel > Programs and Features, locate Microsoft SQL Server 2025.
  • Right-click and select Change, then choose the Repair option from the SQL Server Installation Center.
  • Allow the repair wizard to complete; this will restore missing or corrupted system DLLs, including xmlrw.dll.
  • Restart the SQL Server service afterward via services.msc or by running net stop MSSQLSERVER && net start MSSQLSERVER in an elevated Command Prompt.

Step 3: Apply the Latest Cumulative Update (CU)

  • Download the latest Cumulative Update for SQL Server 2025 from the official Microsoft Download Center.
  • Ensure Windows Server 2025 / Windows 11 has all pending OS updates installed first via Settings > Windows Update.
  • Install the CU package, as this will replace xmlrw.dll with the correct, patched version tied to the current build.

Step 4: Check for DLL Conflicts from Third-Party Software

  • Use Process Explorer (Sysinternals) to check if another application has loaded a conflicting version of xmlrw.dll into memory.
  • Uninstall any third-party XML processing tools or legacy SQL Server client components that might place an older xmlrw.dll into a system path directory (e.g., C:\Windows\System32).
  • Reboot the server to clear any locked file handles before re-testing the query.

Alternative or Verification Steps

  • To verify the fix, re-run the specific query or SSIS package that triggered the XML parsing error; the operation should now complete without throwing Error 6357.
  • If the error persists after a repair and CU update, perform a full Uninstall and clean Reinstall of the SQL Server instance to ensure no orphaned or corrupted binary files remain in the Binn directory.