Error

Returned in the response message when there's an error with your request.

We have modified the messaging for some error codes to make them more meaningful to you. If you have hard coded any error codes in your API implementation, make sure that you update them as per the new codes and messages. For a list of all updated error messages, see: Secure App Service - New error codes and messages: Release 2017-8

Properties

errorCode, errorField, errorMessage

Table: Properties

Name

Type

Description

errorCode

int

The error code. See the tables below for errors.

errorField

string

The field in your request that caused the error.

errorMessage

string

The error's description.

Table: General error codes

Error code

Description

Notes

-62

Workgroup (publisher) is inactive, expired, or otherwise disallowed from performing operations such as signing.

-63

Specified workgroup (publisher) is non-existent or inactive.

-66

An invalid signing set ID was specified.

-67

One or more of the file names specified in commaDelimitedFileNames was not found in the submitted ZIP file.

Incorrect file name. File names are case-sensitive. Additional file name, which is not actually present in the upload.

-68

Specified signing service is invalid or unavailable.

-69

You are trying to create a signing set with a duplicate name. An existing signing set has the same applicationName and applicationVersion

-70

Specified action is disallowed in the current runtime environment.

-71

Renewal request cannot be honored because it is outside the permitted renewal date range.

signupPublisher command

-90

Order is not in the correct state to be approved.

-91

An individual workgroup member (publisher) is not permitted to update the organization name.

-94

Order is not in the correct state to be pushed.

-96

A feature is requested but is not enabled for the account.

-100

Internal system error or exception has occurred.

-102

Request rejected because it appears to be a re-submission of an existing order.

-128

Duplicate signing attribute name found.

-135

Could not find a required attribute element.

-136

The command is not supported for this account.

-139

The specified value exceeds the maximum.

-146

Authentication failure

-147

The entity, (for example, a field), exceeds the maximum.

-149

Time stamping is not supported for the platform.

-151

Time stamping is supported, but not enabled for the platform.

-155

Invalid signing service name.

Incorrect signing service name or the mentioned signing service does not exist. Also possible that the signing service has not been enabled for your workgroup.

-156

Your signing request does not mention any signing service name.

-161

Authentication failure.

You have entered a wrong username or password. If you are sure that you are using the correct username and password, contact support.

This error can also occur due to rare system issues, which require you to reset your password. Your administrator can send you a reset password link.

-159

Authentication failure due to a system issue. Try again later. Contact support if the issue persists.

-162

You have entered a wrong partner code in your request.

-163

Incorrect account information. Your API username does not exist in the account you are trying to use.

Check with your administrator for correct account and workgroup information. Contact support, if you have already tried with the correct information.

-5000

Required field is missing.

-5001

Submitted field value is invalid.

-5002

Submitted field value contains illegal characters.

-5003

Submitted field value contains too many or too few characters.

-5004

Field is not allowed to be submitted, either in general, or because of submitted values for other fields.

-5005

You have not specified a partner code in your request.

-5006

API username not provided.

-5007

Password not provided.

-11001

Second factor authentication failure. Cannot read your client authentication certificate. Ensure that you have configured your client authentication certificate correctly in your API integration and try again.

-11002

Second factor authentication failure. Your client authentication certificate contains wrong data. Ask your administrator to check your account information and resend the client authentication certificate pickup link to you.

-11003

Second factor authentication failure. Username and client authentication certificate mismatch. Ensure that you are using the correct username and client authentication certificate and try again.

-11004

Second factor authentication failure. Your client authentication certificate is inactive. Contact support to activate it.

-11011

You are not authorized to access the API web service.

Possible reasons:

  • Your API account is deactivated.

  • You have not picked up your client authentication certificate.

  • Something is wrong with your account configuration on our systems.

Table: General signing error codes

code or ID

Description

Notes

-8

There were extra or unexpected files in the submitted CAB file.

-9

CAB has already been signed for production.

-12

The signing set contains no files to sign.

This typically does not occur for workgroups, since the accounts are not pre-paid or fixed-quantity.

-19

Workgroup has exhausted the signing events limit assigned to it. Your administrator can help modify this limit.

-27

Signing failed.

Signing failed with unspecified cause.

-30

Signing request timed out.

-45

Specified filename for signing is the wrong type for the specified signing service.

-63

Specified workgroup (publisher) is non-existent or inactive.

-65

The signing certificate creation failed.

-67

One or more of the file names specified in commaDelimitedFileNames was not found in the submitted ZIP file.

Incorrect file name. File names are case-sensitive. Additional file name, which is not actually present in the upload.

-79

Specified signing service does not support large file uploads.

-99

A signing certificate could not be located.

-127

Only one assertion file may be submitted with each request.

-152

The signing service that you are using requires an input for signingCertificateOptionsType, but this object is missing from your request or contains an invalid value.

-154

Code signing certificate generation fails due to contract limitations. Contact your account representative, sales manager, or account manager to resolve this issue.

-158

Code signing certificate generation fails due to a technical issue on our side. Try again after some time. If the issue persists, contact support.

-160

Your workgroup does not have a valid contract to use this service. To resolve this issue, ask your administrator to contact support.

Possible reasons:

  • You don't have a contract.

  • Your contract has expired.

  • Your contract data could not be read due to a system issue.

-164

Test-signed file(s) have been purged. Your signing set is still valid and available for further test and production signing

Test signed files get purged 30 days after the date of signing.

-9000

Too many application files specified. Delete all files except one : <file type>

This occurs if multiple application files of the same type are uploaded. For example, more than one JAR file.

-9001

One or more required files are missing. Specify all files that the signing service requires for signing.

-10025

Your workgroup or service management account is deactivated.

Contact our customer success manager or customer support to reactivate the account.

Table: Error codes for the application upload and download servlet

code or ID

Description

Notes

-9002

<fileName> exceeds the size limit. Reduce the file size and upload again

Returns the name of any file that exceed the size limit

-9003

No files are available for download. Specify Application or Supporting files for download

-9004

No files are available for download. Upload the files required for the signing set

-9005

You can only upload one zip file. Choose a single zip file and try again

-9006

Application files cannot be downloaded at this time. Wait a few moments and try again

Table: Android signing error codes

Code

Description

-89

No .apk was found for an Android signing request.

-90

More than one .APK file was found. Only one file is permitted.

-99

A signing certificate could not be located.

-117

Wrong input for signingAction parameter. Your request does not specify whether you want to use an existing certificate friendly name or generate a new certificate. This issue generally arises while using on-demand or fixed-pool certificate model.

-118

Incorrect certificate friendly name in the request. Either the name is incorrect or there are no certificates by that name.

-120

You have not provided a certificate friendly name in your request. Issue arises when you use the fixed-pool or on-demand certificate model with a valid signingAction value, but the certificate friendly name field is blank.

-122

You are trying to request a new certificate with a duplicate friendly name.

-123

You are trying to generate a new certificate with a very long friendly name. Certificate friendly name should not exceed 128 characters.

-125

Extra files were found in addition to the .APK.

Table: JAVA, JAVA Mobile signing error codes

Code

Description

Signing service

-1

Your upload does not contain one or more of the files that you mentioned in the commaDelimitedFileNames parameter.

JAVA_MOBILE, JAVA

-2

The JAD file is missing

JAVA_MOBILE

-3

Found files that were not of type JAR or JAD

JAVA_MOBILE

-6

Found more than one JAR

JAVA_MOBILE, JAVA

-7

Found more than one JAD

JAVA_MOBILE

-97

Found files that were not of type JAR

JAVA

Table: Microsoft Mobile CAB, Microsoft Mobile XAP, Windows Mobile, Windows Autodesk signing error codes

Code

Description

Signing service

-10

There was more than one CAB file in the signing set.

MICROSOFT_MOBILE

-21

Invalid CAB file or no signature found on CAB file

MICROSOFT_MOBILE

-52

Found more than one EXE

WINDOWS AUTODESK

-73

Illegal additional files have been submitted for signing with the XAP file

MICROSOFT_MOBILE_XAP

-74

Found more than one XAP

MICROSOFT_MOBILE_XAP

-83

Extra files were found in addition to the EXE

WINDOWS AUTODESK

Table: XMLDSIG signing error codes

Code

Description

Signing service

-117

Wrong input for signingAction parameter. Your request does not specify whether you want to use an existing certificate friendly name or generate a new certificate. This issue generally arises while using on-demand or fixed-pool certificate model.

XMLDSIG

-118

Incorrect certificate friendly name in the request. Either the name is incorrect or there are no certificates by that name.

XMLDSIG

-120

You have not provided a certificate friendly name in your request. Issue arises when you use the fixed-pool or on-demand certificate model with a valid signingAction value, but the certificate friendly name field is blank.

XMLDSIG

-132

One or more XML files are missing

XMLDSIG

-152

Certificate options are missing from the signing request

XMLDSIG

Table: Input parameter error codes for the upload and download services

Error code

Error field

Error message

-100

Internal system error or exception has occurred

-5000

fieldname

Required field is missing

-5001

fieldname

Submitted field value is invalid

-5002

fieldname

Submitted field value contains illegal characters

-2600

Runtime error in upload service

-2601

Runtime error in download service

-2602

Invalid credentials (username + password + signingSetID

-2603

signingSetID

No matching signing set

-2604

signingSetID

No matching signing request

-2605

signingSetID

No matching application file

-2606

signingSetID

Invalid signing set state for file upload

-2607

Invalid request - wrong content type

-2608

Invalid request - no content length

-2609

Invalid request - malformed data stream

-2610

Invalid request - no application file

-2611

Maximum file size exceeded

-2612

Invalid request - No multipart boundary

-2613

An application file has already been uploaded to the signing set

-2614

Upload filename does not match filename in signing set

-2615

Only one large application file can be uploaded at a time

-2616

signingSetID

Application file is not ready - testing in progress

-2617

signingSetID

Application file is not ready - waiting for signing

-2618

signingSetID

Application file signing failed

-2619

signingSetID

Testing failed for this signing set - no signed file is available

-2620

Content-Disposition specification missing

-2621

Content-Disposition specification is malformed

-2622

Content-Disposition - name part is missing

-2623

Content-Disposition - name part is invalid

-2624

Content-Disposition - name part's key is invalid

-2625

Content-Disposition - name part's value is missing or invalid

-2626

Content-Disposition - filename part is missing

-2627

Content-Disposition - filename part is invalid

-2628

Content-Disposition - filename part's key is invalid

-2629

Content-Disposition - filename part's value is missing or invalid

-9000

Too many application files specified. Delete all files except one : <file type>

-9001

One or more required files are missing. Specify all files that the signing service requires for signing.

-9002

<fileName> exceeds the size limit. Reduce the file size and upload again

-9003

No files are available for download. Specify application or supporting files for download.

-9004

No files are available for download. Upload the files required for the signing set.

-9005

You can only upload one zip file. Choose a single zip file and try again

-9006

Application files cannot be downloaded at this time. Wait a few moments and try again

We use cookies to ensure that we give you the best experience on our website. By using this site, you agree to the Terms of Service.