Error Sample

Here you see a faulty uploadTemporarySspFile file/upload response, where the no file name was empty in the requestattached. The system returns you the baseResult as failedErrorId, the error code (ERR0002) and a textual description (errorMsg) why it failedmessage and the TraceId.

<baseResult>failed</baseResult>{
  <errorInfo>
    <error>ERR0002</error>"ErrorId": "ERR0097",
    <errorMsg>ERR0002: Parameter FileName is empty</errorMsg>"Message": "ERR0097 - File must not be empty.",
    <supportId>756094</supportId>
  </errorInfo> "TraceId": "f35aad06-1234-1234-1234-daedd619ed29"
}

Messages starting with “ERR00xx” are returned errors of eSAW itself. If an error occoured in the SIGNificant Server Platform (Workstep Controller) it has an additional error code with “ERROR-xxxxx”, which identifies the SSP error. Below you find the error codes for eSAW and WSC (known by eSAW).Here you find an response of an faulty SendEnvelope request, where the workstep configuration was invalid. The error is first a eSAW error (invalid workstep) and then a SSP/WSC error with details, why the workstep configuration was invalid:

<baseResult>failed</baseResult>
<errorInfo>
	<error>ERR0012</error>
	<errorMsg>ERR0012: Invalid workstep configuration: 
		<error>ERROR-12484</error>: 
		<errorMsg>Some configuration is missing for signature field with id '93cce567-ae5c-4e98-ac99-9f56ac034250', either provide a complete set for sig object or reference an existing field</errorMsg>
	</errorMsg>
	<supportId>441400</supportId>
</errorInfo>

eSignAnyWhere API Errors

Error codes starting with “ERR0xxx” are messages, which are coming from eSAW directly. Errors with “ERROR-” are errors from the SIGNificant Server Platform, which is responsible for the workstep and the workstep configuration (see below).