| Previous | Next |
| STATUS_LOST_WRITEBEHIND_DATA_LOCAL_DISK_ERROR | STATUS_XMLDSIG_ERROR |
STATUS_XML_PARSE_ERROR
The input failed XML parsing before higher-level processing
XML parsing first requires a well-formed document: markup must be correctly nested, a document must have a single root element, character references must be legal, and the byte stream must agree with its encoding declaration. This status usually identifies a syntax or decoding failure before schema validation or application-specific interpretation can begin.
The most useful evidence is the original byte sequence plus the parser location and error. Text displayed in a log may already have replaced invalid bytes or normalized line endings. Truncated network responses, an unexpected byte-order mark, unescaped characters, duplicate declarations, and HTML returned where XML was expected are common concrete causes.
What to inspect
- Capture the original bytes, content length, content type, declared encoding, BOM, and parser line and column.
- Validate well-formedness independently without automatically rewriting the document.
- Check transport and decompression layers for truncation before changing XML parser settings.
- Distinguish a syntax failure from a well-formed document that later fails schema or business validation.
References
- Microsoft Open Specifications: NTSTATUS values
- W3C: XML 1.0
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.