| Previous | Next |
| ERROR_SXS_XML_E_INVALID_UNICODE | ERROR_SXS_XML_E_UNEXPECTEDENDTAG |
ERROR_SXS_XML_E_WHITESPACEORQUESTIONMARK
ERROR_SXS_XML_E_WHITESPACEORQUESTIONMARK (0x000036E2) is a Windows Side-by-Side XML parser status for application, assembly, policy, or configuration manifest processing.
This code exposes the parser’s expected-token set: after the syntax already consumed, the next legal token must begin with XML whitespace or ?. Another character means the current declaration or processing-instruction form cannot continue under that production.
Parser boundary
XML uses ? in processing-instruction and declaration terminators such as ?>, while whitespace separates declaration fields and processing-instruction data. The exact preceding token determines which branch the parser expected.
What to inspect
- Inspect several characters before the reported position to identify the declaration or processing-instruction context already parsed.
- Add whitespace only when a separator is required; if the construct should end, verify the complete
?>terminator instead. - Check manifest serializers that concatenate XML declaration fields or processing-instruction data without preserving token boundaries.
Use sxstrace to capture the precise manifest and location because the status name alone does not identify which XML production reached the whitespace-or-question-mark branch.
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.