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

by

Troubleshooting Guide: SQL Server Error 9425 – XML Parsing Failure

Why This Error Happens

Error 9425 occurs when SQL Server’s internal XML parser encounters malformed, incomplete, or improperly encoded XML data at a specific line number during parsing operations. This typically stems from corrupted XML input (such as invalid characters, unclosed tags, or encoding mismatches like UTF-8 vs UTF-16), data truncation during transmission, or improperly escaped special characters within XML columns or variables. It can also surface when applications pass malformed XML to stored procedures using OPENXML, FOR XML, or native XML data type columns.

Step-by-Step Resolution Guide

Step 1: Identify the Exact Source and Line Number

  • Review the full error message to note the specific line number referenced (e.g., “XML parsing: line 12, unexpected end of input”).
  • Locate the source query, stored procedure, or application call generating the XML using SQL Server Profiler or Extended Events in SQL Server Management Studio (SSMS).
  • Run the query manually: SELECT TRY_CAST(YourXmlColumn AS XML) FROM YourTable WHERE ID = <ProblemRowID>; to isolate the exact malformed record.

Step 2: Validate and Repair the XML Structure

  • Check for unclosed or mismatched tags, missing root elements, or invalid special characters (&, <, >) that aren’t properly escaped as &amp;, &lt;, &gt;.
  • Verify the encoding declaration matches the actual file/stream encoding (e.g., <?xml version="1.0" encoding="UTF-8"?> must match the source).
  • Use a validation tool or run: SELECT xmlcolumn.exist('/root') FROM YourTable; to test well-formedness before full parsing.
  • If the XML originates from an external application, check the application logs on Windows Server 2025 (Event Viewer > Applications and Services Logs) for truncation or encoding errors during data transmission.

Step 3: Correct the Application or Import Process

  • If data is ingested via SSIS or BULK INSERT, confirm the file encoding matches the CODEPAGE parameter specified in the import statement.
  • Update application code to properly encode XML output using libraries like System.Xml (for .NET apps) instead of manual string concatenation, which often introduces malformed tags.
  • Re-run the import or transaction after correcting the source XML payload.

Step 4: Check for SQL Server Patch-Level Issues

  • Confirm SQL Server 2025 is updated to the latest Cumulative Update (CU) via SELECT @@VERSION; and cross-reference with Microsoft’s release notes, as XML parser bugs are occasionally patched.
  • Apply the latest CU using SQL Server Setup or Windows Update if running integrated services.

Alternative or Verification Steps

  • After applying fixes, re-execute the original query or application transaction and confirm no Error 9425 appears in the SQL Server Error Log (EXEC xp_readerrorlog;).
  • As an alternative, if the XML source cannot be immediately fixed, implement a TRY...CATCH block around the XML parsing logic to gracefully log and quarantine malformed records instead of failing the entire transaction.