| Previous | Next |
| ERROR_SXS_XML_E_COMMENTSYNTAX | ERROR_SXS_XML_E_BADNAMECHAR |
ERROR_SXS_XML_E_BADSTARTNAMECHAR
ERROR_SXS_XML_E_BADSTARTNAMECHAR (0x000036D0) is a Windows Side-by-Side XML parser status for application, assembly, policy, or configuration manifest processing.
The invalid character appears at the start of an XML name. This can affect an element, attribute, entity, or processing-instruction name and is distinct from a bad character later in an otherwise validly started name.
Parser boundary
XML defines NameStartChar separately from NameChar. A digit, many punctuation characters, or stray markup at the beginning of a token can therefore fail here even if similar characters may be legal later in another kind of token.
What to inspect
- Look immediately after the opening markup delimiter at the parser position for a digit, quote, equals sign, or other token that cannot start a name.
- Check whether a template expanded an empty element or attribute name and left the following value where a name should have been.
- Validate the raw generated manifest, not only the project file from which the manifest was produced.
The converted sxstrace output should be used to locate the failing file and line; repair the malformed name before testing activation-context dependencies.
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.