Windows error 14033 (ERROR_SXS_XML_E

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Manifest Parse Error : A name contained an invalid character.

Previous	Next
ERROR_SXS_XML_E_BADSTARTNAMECHAR	ERROR_SXS_XML_E_BADCHARINSTRING

ERROR_SXS_XML_E_BADNAMECHAR

ERROR_SXS_XML_E_BADNAMECHAR (0x000036D1) is a Windows Side-by-Side XML parser status for application, assembly, policy, or configuration manifest processing.

The parser had already recognized the beginning of an XML name and then encountered a character that is not permitted in the remaining NameChar sequence. The affected token can be an element name, attribute name, entity name, processing-instruction target, or another XML name.

Parser boundary

XML distinguishes the first character of a name from later characters: NameStartChar starts the token and NameChar governs the rest. This code is therefore different from ERROR_SXS_XML_E_BADSTARTNAMECHAR.

What to inspect

Inspect punctuation or whitespace embedded in the name reported near the parser position; such characters often terminate a token unexpectedly.
Check generated namespace-qualified names for malformed prefixes rather than blindly removing every colon.
If a tool synthesized the manifest, compare its raw output with the XML source that was intended to be emitted.

The first SxS parser error is the useful one: locate the exact name token in the traced manifest and validate it against XML name syntax before investigating assembly binding.

References

Looking for a different code? Search another status or error code.