The Sign 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 Sign response. All other errors are returned as SOAP faults.

Code	Description (Desc)	Details
OK	The operation completed successfully	The document was successfully signed and returned in the response.
SignerInvalid	<Descriptive message>	The signing certificate is invalid: it is revoked, expired, or not trusted. This result code is returned only when an archive for long-term validation is created (JobType is CADESA, XADESA, PADESLTV, or EVIDENCE), because this is the only case where the signer certificate is checked for validity.

SOAP faults

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

FaultCode	Reason	Description
Client	SenderTag is required	No SenderTag is present in the Sign SOAP request, or the SenderTag cannot be parsed from the business document.
Client	ReceiverTag is required	No ReceiverTag is present in the Sign SOAP request, or the ReceiverTag cannot be parsed from the business document.
Client	Could not find compliance map for <key reference>	The authentication certificate does not have any assigned compliance map.
Client	Could not find associated certificate(s) for sender=<SenderTag> and receiver=<ReceiverTag>	It was not possible to find a signing certificate for the SenderTag/ReceiverTag pair.
Client	Could not find any sign policies for sender=<SenderTag> and receiver=<ReceiverTag>	It was not possible to derive a signing policy from the SenderTag/ReceiverTag pair.
Client	Sender=<SenderTag> and receiver=<ReceiverTag> require double signature, a feature which is not supported by the chosen output format	The signature format does not support double signatures, which is required by the compliance map in use.
Client	No document present in request	No Document element is present in the request.
Client	Document is not PDF	PDF document format is needed as input to create a PDF signature. This error occurs if the requested InputType is PDF and the requested OutputType is a PDF signature.
Client	The PDF is encrypted/password protected and cannot be opened	To create a signed PDF, the document must be opened. A password-protected PDF cannot be signed.
Client	AgreementIdentifier format violation	The AgreementIdentifier is too long or contains illegal characters.
Client	SignerIdentifier not supported	The SignerIdentifier is not permitted for the chosen signature format.
Client	SignerIdentifier format violation	The SignerIdentifier is too long or contains illegal characters.
Client	ClientData format violation	The ClientData is too long or contains illegal characters.
Client	Illegal combination: <jobType>/<outputType>	There are restrictions on how to combine JobType with OutputType. See the JobType reference for details.
Client	Illegal InputType/OutputType combination	Not all combinations of InputType and OutputType are allowed. See the supported formats reference for details.
Client	Authentication certificate not configured	The client certificate used has not been configured to access this operation.
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	Sender=<X> and receiver=<Y> require a hash algorithm, <Z>, which is not supported by the chosen output format	The selected flow requires a hash algorithm that the output format does not support.
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 error. See the event log for more details.