| Previous | Next |
| ERROR_SXS_XML_E_XMLDECLSYNTAX | ERROR_SXS_XML_E_MISSINGWHITESPACE |
ERROR_SXS_XML_E_BADCHARDATA
ERROR_SXS_XML_E_BADCHARDATA (0x000036D4) is a Windows Side-by-Side XML parser status for application, assembly, policy, or configuration manifest processing.
The failure is in parsed character data, not in an assembly identity or dependency lookup. XML 1.0 limits the characters that can appear in a document, and ordinary character data also cannot contain raw markup delimiters such as an unescaped ampersand or less-than sign.
Parser boundary
The XML Char and CharData productions are the useful boundary here. A byte-decoding problem can surface as bad character data too, so the visible glyph in an editor is not enough evidence that the underlying file is valid.
What to inspect
- Inspect the exact line reported by the SxS trace for control characters, embedded binary bytes, or text copied from a non-XML source.
- Replace literal
&and<characters in text with the appropriate XML entity references when they are data rather than markup. - Verify that the declared encoding matches the bytes on disk before editing assembly names or version attributes.
Trace the failing activation with sxstrace and start with the first parser diagnostic for the named manifest; later binding messages are consequences if XML parsing never completed.
References
- Microsoft: System Error Codes 12000-15999
- Microsoft: Side-by-Side manifest files reference
- Microsoft: sxstrace
- W3C: XML 1.0
Looking for a different code? Search another status or error code.