No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FusionCloud Troubleshooting Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Error Codes

Error Codes

A returned API Gateway error message contains the message and request_id fields in the body. The message field describes the problem occurred, and the request_id field tracks the request for further problem analysis.

Table 24-2 Error codes


Error Code

Symptom Shown on the Client

Possible Cause



{"message":"Message error","request_id":xxx}

The received message is invalid when the management interface of API Gateway is invoked.

{"message":"Unknown service error in api","request_id":xxx}

An unknown service error occurs during the AK/SK authentication.



{"message":"The account must be a tenant token(ak/sk).","request_id":xxx}

The invoker uses the account that manages the tenants to invoke the API.

{"message":"Authorization information is empty","request_id":xxx}

The authorization information is empty during the AK/SK authentication.

{"message":"Authorization information is wrong.","request_id":xxx}

The authorization information is wrong during the AK/SK authentication.

{"message":"Wrong Token.","request_id":xxx}

The tenant's Token cannot be parsed.


The tenant's Token is unauthorized.

{"message":"Token expires.","request_id":xxx}

The tenant's Token expires and a new Token is needed.

{"message":"Get user token error","request_id":xxx}

API Gateway fails to obtain the user's Token from IAM during the AK/SK authentication.

{"message":"Authorization information is wrong","request_id":xxx}

API Gateway fails to authenticate the user identity during the AK/SK authentication.



{"message":"Api does not exist","request_id":xxx}

The API invoked does not exist.




The transparent transmission goes wrong and therefore the request cannot be transmitted.

{"message":"There is no X-Sdk-Date header in request","request_id":xxx}

There is no X-Sdk-Date header in the request during the AK/SK authentication.

{"message":"Request time is wrong","request_id":xxx}

The format of the X-Sdk-Date header in the request is wrong during the AK/SK authentication.

{"message":"Request time is invalid","request_id":xxx}

When the AK/SK authentication is triggered, the time in the X-Sdk-Date header is incorrect. This may happen when the time of the client is not synchronized with that of the Shubao node in API Gateway.

{"message":"Failure parse of signature information","request_id":xxx}

A signature parsing failure occurs during the AK/SK authentication.



{"message":"Access Forbidden","request_id":xxx}

The access is forbidden during the AK/SK authentication. This may be because the AK is temporarily blacklisted because it may be cracked with brute force after failing the authentication for multiple times.

{"message":"Please refresh your token.","request_id":xxx}

The tenant's Token is invalid and needs to be updated.

Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22986

Downloads: 37

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next