Windows error 14064 (ERROR_SXS_XML_E

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Manifest Parse Error : A declaration was not closed.

Previous	Next
ERROR_SXS_XML_E_UNCLOSEDCOMMENT	ERROR_SXS_XML_E_UNCLOSEDCDATA

ERROR_SXS_XML_E_UNCLOSEDDECL

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

The parser entered declaration markup and never reached the delimiter required to finish that declaration. XML declarations in DTD/internal-subset syntax are distinct from the initial <?xml ...?> declaration, so the trace location and surrounding opener matter.

Parser boundary

Element, attribute-list, entity, and notation declarations each have productions ending with a closing >. A truncated declaration or malformed nested content can keep the parser in declaration state until end of input.

What to inspect

Inspect the declaration opener before the trace location and identify its expected XML production rather than assuming it is the document XML declaration.
Look for a missing closing >, unterminated quoted value, or incomplete parenthesized content model inside that declaration.
If the SxS manifest was not intended to carry a DTD subset, find the generator that inserted declaration markup and remove it at the source.

The parsed SxS trace names the file and usually narrows the declaration region; repair the earliest unterminated construct before interpreting later EOF errors.

References

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