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

by

Troubleshooting Guide: SQL Server Error 2294 – Invalid XML Processing Instruction Target

Why This Error Happens

This error occurs when SQL Server’s XML parser encounters a processing instruction (PI) that uses the reserved target name “xml” (in any case variation), which violates the W3C XML specification. The XML 1.0 standard explicitly reserves names matching the pattern [Xx][Mm][Ll] for the XML declaration itself, so using it as a custom processing instruction target—such as <?xml-stylesheet?> being malformed into <?xml ...?>—triggers a parse failure. This typically happens due to malformed XML data being inserted into an xml typed column, corrupted import files, or improperly generated XML from third-party ETL tools or legacy applications feeding data into SQL Server 2025.

Step-by-Step Resolution Guide

Step 1: Identify the Source of the Malformed XML

  • Locate the specific INSERT, UPDATE, or BULK IMPORT statement that triggered Error 2294 by checking SQL Server Error Logs via C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG.
  • Run SELECT * FROM sys.dm_exec_requests WHERE session_id = <SPID> to correlate the failing session with the query text.
  • Export the raw XML payload to a .xml file for manual inspection using Notepad++ or VS Code on Windows 11/Windows Server 2025.

Step 2: Correct the XML Processing Instruction

  • Open the offending XML file and search for any instance of <?xml that is NOT the first line of the document (valid XML declarations must only appear once, at position 0).
  • Rename any erroneous processing instructions—for example, change <?xml-data version="1.0"?> back to a properly namespaced PI like <?xmldata version="1.0"?> or <?custom-xml version="1.0"?>.
  • Validate the corrected file using PowerShell: [xml](Get-Content "C:\temp\yourfile.xml") — if no error is thrown, the XML is well-formed.

Step 3: Patch or Update the Source Application

  • If the XML is being generated programmatically (e.g., via SSIS packages or a .NET application), check the XmlWriterSettings configuration and ensure WriteProcessingInstruction() calls never pass “xml” as the target parameter.
  • Update SSIS packages stored in C:\Program Files\Microsoft SQL Server\170\DTS\Packages\ to sanitize XML output before it reaches the xml data type column.
  • Apply the latest Cumulative Update for SQL Server 2025 via Setup.exe, as parser edge-case handling may be refined in later builds.

Step 4: Re-Run the Import or Transaction

  • Re-execute the original INSERT/UPDATE statement or BULK INSERT job using the corrected XML file.
  • Monitor sys.messages for Error 2294 recurrence: SELECT * FROM sys.messages WHERE message_id = 2294 AND language_id = 1033.

Alternative or Verification Steps

  • Verify the fix: Run SELECT CAST('<root><?validpi data="test"?></root>' AS XML) in SSMS—if it returns successfully without Error 2294, your XML parsing pipeline is now compliant.
  • Alternative workaround: If you cannot modify the source XML generator immediately, pre-process incoming XML strings using REPLACE() or a regex-based cleansing step in SSIS to strip any <?xml occurrences beyond the first line before casting the data to the xml type in SQL Server.