The ValidateArchive operation returns errors as inline result codes or SOAP faults depending on the nature of the error.

Result codes

The following result codes are returned inline in the Result element of a ValidateArchive response. All other errors are returned as SOAP faults.

Code	Description (Desc)	Details
OK	The signature is valid	The signature is valid. This also includes that the signer certificate is valid.
SignatureInvalid	<Descriptive message>	A signature or a timestamp is invalid.
SignerInvalid	<Descriptive message>	A signing certificate or a timestamp certificate is invalid; it is either revoked or expired.

SOAP faults

The following SOAP faults can be returned by the ValidateArchive operation. Each fault includes a FaultCode and a Reason (FaultString) with a human-readable message.

FaultCode	Reason	Description
Client	Wrong input type	The InputType parameter in the ValidateArchive SOAP request is not supported.
Client	Wrong output type	The OutputType parameter in the ValidateArchive SOAP request is not supported.
Client	No document present in request	No SignedDocument to be validated is present in the request.
Client	No valid ValidationResult found	No ValidationResult element is present in the ValidateArchive SOAP request.
Client	Invalid archive (missing TimeStamp in ValidationData)	The ValidationData is not timestamped.
Client	Document is not PDF	PDF signature document format is needed as input to validate a PDF signature. This error occurs if the requested InputType is a PDF signature and the requested OutputType is PDF.
Client	Invalid signed content	The signed content is invalid.
Client	Signed content not present	No signed content can be parsed from the signature.
Client	Signature corrupt	The signature format is corrupt.
Client	Document corrupt	The format of the document parsed from the signature is corrupt.
Client	Illegal InputType/OutputType combination	Not all combinations of InputType and OutputType are allowed. See the supported formats reference for details.
Client	Request containing both Archive and ValidationData not supported	It is not allowed to specify both ValidationData and a CAdES-A or XAdES-A signature in SignedDocument.
Client	Archive input parameter not allowed	The Archive input parameter is not allowed for the signature type of the long-term verifiable signature.
Client	Missing data in Archive input parameter for input type PKCS7D	A long-term verifiable signature with signature type PKCS7D must specify the Archive element.
Client	Missing data in Archive input parameter for input type EANCOM	A long-term verifiable signature with signature type IDEAL, GS1AT, or AECOC must specify the Archive element.
Client	Detached archive is not related to signature	The document in the Document element is not related to the long-term verifiable signature in the Archive element.
Client	InputType <inputType value> does not match input document type	The InputType is set to a supported value, but the document to be validated is completely malformed and cannot be parsed. Note that "Document is not PDF," "Signature corrupt," and "Document corrupt" errors have separate codes.
Client	Document size (<actualSize> bytes) exceeded the maximum allowed size (<maxSize> bytes)	The size of the uploaded document exceeds the maximum allowed size for the InputType/OutputType combination in use.
Client	ISO9796-2 unknown trailer '<X>'	The ISO9796-2 trailer was not recognized.
Client	ISO9796-2 implicit trailer not allowed	Implicit trailer is not allowed for ISO9796-2.
Client	ISO9796 trailer mismatch, expected '<X>' but was '<Y>'	The hash algorithm specified in the ISO9796-2 trailer (<Y>) is not the expected one (<X>).
Client	Signing certificate has unsupported asymmetric algorithm <oid>	An asymmetric algorithm other than RSA was used to create the signature.
Client.NotAuthorized	Authentication certificate not found, revoked or not valid	The client certificate used has not been configured to access this operation.
Server	Internal server error	General server exception.