| Did this page help you? Yes No Tell us about it... |
The following table lists the errors returned by all the License Service API actions. Errors specific to a particular action are listed in the topic for that action.
![]() | Important |
|---|---|
We might throttle requests to the License Service as necessary. When we throttle, we return a 503 (service unavailable) HTTP status code. Your system should be prepared to retry any request that receives a 503 code. |
| Name | Description |
|---|---|
|
|
Access to the resource is denied. |
|
|
The provided security credentials are not valid. |
|
|
The query parameter |
|
|
The element |
|
|
We encountered an internal error. Please try again. |
|
|
AWS was not able to validate the provided access credentials. |
|
|
The action |
|
|
The address |
|
|
Invalid batch request. Reason: |
|
|
The HTTP authorization header is bad, use format: |
|
|
Invalid HTTP request. Reason: |
|
|
The parameter |
|
|
Value |
|
|
The query parameter |
|
|
The service cannot handle the request. Request is invalid. |
|
|
The following response groups are invalid: |
|
|
The provided security credentials are not valid. Reason: |
|
|
The security token used in the request is invalid. Reason: |
|
|
The Web Service |
|
|
Could not parse the specified URI: |
|
|
WS-Addressing parameter |
|
|
Invalid SOAP Signature. Reason: |
|
|
Version not well formed: |
|
|
No action was supplied with this request. |
|
|
Request must contain AWSAccessKeyId or X.509 certificate. |
|
|
AWS was not able to authenticate the request: access credentials are missing. |
|
|
Authorized request must have a "date" or "x-amz-date" header. |
|
|
The request must contain the parameter |
|
|
Unexpected: missing SOAPRequestInfo from the request. |
|
|
WS-Addressing is missing a required parameter: |
|
|
Attachment content is not available. |
|
|
No MIME boundary found for attachment part. |
|
|
The requested version ( |
|
|
Request has expired. |
|
|
Request is throttled. |
|
|
SSL connection required for backward compatible SOAP authentication. |
|
|
Timestamp must be in XSD date format. |
|
|
The <Action> request element is missing in SOAP 1.1 request. |
|
|
Could not find the SOAP body in the request. |
|
|
Could not find the SOAP envelope in the request. |
|
|
Could not parse the SOAP envelope. |
|
|
The SOAP envelope exceeded the maximum allowed depth. |
|
|
The SOAP envelope exceeded the maximum allowed length. |
|
|
Envelope Namespace must be for either SOAP 1.1: http://schemas.xmlsoap.org/soap/envelope, or SOAP 1.2: http://www.w3.org/2003/05/soap-envelope. |
|
|
Encoding (most likely US-ASCII) not supported - internal service error. |
|
|
The requested HTTP verb is not supported: |
|
|
The URI exceeded the maximum limit of |
|
|
Signed info is corrupt. |
|
|
Timestamp for created date must be in ISO8601 format. |
|
|
BinarySecurityToken must have EncodingType of |
|
|
Timestamp for expires date must be in ISO8601 format. |
|
|
BinarySecurityToken has bad ValueType. |
|
|
BinarySecurityToken must have attribute ValueType. |
|
|
Request must not contain more than one BinarySecurityToken with valueType |
|
|
Request cannot contain more than one UsernameToken. |
|
|
Error while processing signature element. |
|
|
SignatureValue is missing or empty. |
|
|
Error while processing signed info. |
|
|
Request has no SignedInfo. |
|
|
Request has expired. |
|
|
Timestamp must have Expires element. |
|
|
Security Header Element is missing the timestamp element. |
|
|
UsernameToken must not contain Password. |
|
|
Request must contain Username element in UsernameToken. |
|
|
Request cannot contain both Credential and an X.509 certificate. |
|
|
Request must not contain more than one BinarySecurityToken with valueType |
|
|
Failed to check signature with X.509 certificate. |
|
|
Could not parse X.509 certificate. |