| Previous | Next |
| VSS_E_UNEXPECTED_PROVIDER_ERROR | VSS_E_INVALID_XML_DOCUMENT |
VSS_E_CORRUPT_XML_DOCUMENT
VSS_E_CORRUPT_XML_DOCUMENT indicates that a VSS XML document is malformed or does not satisfy the required schema. This status is deprecated; newer code should use VSS_E_INVALID_XML_DOCUMENT for the same class of failure.
How to investigate for VSS_E_CORRUPT_XML_DOCUMENT
- Validate the XML syntax, namespaces, versioned schema, and required elements.
- Identify whether the document is requester backup metadata, writer metadata, or provider data before changing it.
- Regenerate metadata through the VSS API when possible instead of hand-editing persisted VSS documents.
Microsoft: VSS requester metadata
Diagnostic interpretation of VSS_E_CORRUPT_XML_DOCUMENT
VSS_E_CORRUPT_XML_DOCUMENT has the HRESULT value 0x80042310. AllStat records the condition as “The given XML document is invalid. For VSS_E_CORRUPT_XML_DOCUMENT, it is either incorrectly-formed XML or it does not match the schema. This error code is deprecated.”. For VSS_E_CORRUPT_XML_DOCUMENT, in practice, interpret that wording at the boundary owned by storage, volume management, or structured-storage state, rather than treating the value as a generic Windows message.
Evidence to capture for VSS_E_CORRUPT_XML_DOCUMENT
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80042310 value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions VSS_E_CORRUPT_XML_DOCUMENT or the vss / corrupt / xml / document operation.
- For VSS_E_CORRUPT_XML_DOCUMENT, compare the failing machine with a working one at the same configuration boundary: component version, policy, registration, identity, and target resource.
Retry and recovery for VSS_E_CORRUPT_XML_DOCUMENT
Retry VSS_E_CORRUPT_XML_DOCUMENT only when the owning API documents a transient state or after the condition described as “The given XML document is invalid. For VSS_E_CORRUPT_XML_DOCUMENT, it is either incorrectly-formed XML or it does not match the schema. This error code is deprecated.” has changed. For VSS_E_CORRUPT_XML_DOCUMENT, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.