Error Codes
Background
- An error code returned by an API does not correspond to one error message. The following table lists only common error messages.
- Most DeH APIs are asynchronous. Some error codes are displayed in the returned messages for task viewing requests. HTTP status codes may not be accurate.
- The DeH service is strongly dependent on other services, such as network and storage. If the reported error messages contain information about ECS-depended services, contact technical support for troubleshooting.
Description
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|
400 |
DEH.0001 |
Request body parsing failed, please check if the request data is correct. |
Failed to parse the request. |
Check whether the request data is correct. |
400 |
DEH.0006 |
An error has occurred in job submission. Try again later or contact customer service. |
Submit job failed. |
For details, see the returned error message or contact technical support. |
400 |
DEH.0018 |
Illegal parameter. Try again later or contact customer service. |
Invalid parameter. |
For details, see the returned error message or contact technical support. |
400 |
DEH.0019 |
Failed to query enterprise project id. Try again later or contact customer service. |
Failed to obtain the enterprise project ID. |
For details, see the returned error message or contact technical support. |
403 |
DEH.0033 |
Operations are prohibited on the client due to permissions. Check token permissions. For details, see the error message returned by the API. |
Operations are prohibited on the client due to insufficient permissions. |
You do not have the permissions to perform such an operation. Check token permissions. For details, see the error message returned by the API. |
400 |
DEH.0051 |
Failed to query the dedicated host quota of the tenant. Try again later or contact customer service. |
Failed to query the tenant DeH quota. |
For details, see the returned error message or contact technical support. |
400 |
DEH.0052 |
PDP authentication failed. |
PDP authentication failed. |
Configure the required permissions. |
403 |
DEH.0054 |
Your account lacks the necessary permissions. Try again later or contact customer service. |
You do not have permission or your balance is insufficient. |
For details, see the returned error message or contact technical support. |
400 |
DEH.0055 |
Failed to update server status scene. |
Failed to update the DeH status. |
When updating the DeH status, the scene can be empty. If the scene is not empty, check whether the scene is POLICE, ILLEGAL, VERIFY, PARTNER, or DELETE_ACCOUNT. |
400 |
DEH.1007 |
Failed to access the OpenStack. Try again later or contact customer service. |
Failed to access the OpenStack. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3004 |
Failed to allocate dedicated hosts. Try again later or contact customer service. |
Failed to create a DeH. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3009 |
OpenStack access timed out. For details, contact technical support. |
OpenStack access timed out. |
For details, contact technical support. |
500 |
DEH.3011 |
System error. Try again later or contact customer service. |
System error. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3016 |
Failed to call the IAM API. Try again later or contact customer service. |
Failed to access IAM. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3028 |
Failed to allocate dedicated host. Try again later or contact customer service. |
Failed to allocate DeHs. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3039 |
Failed to release dedicated host. Try again later or contact customer service. |
Failed to release a DeH. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3040 |
Failed to list dedicated hosts. Try again later or contact customer service. |
Failed to list DeHs. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3041 |
Failed to get dedicated host. Try again later or contact customer service. |
Failed to obtain the DeH. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3042 |
Failed to list dedicated host resource types. Try again later or contact customer service. |
Failed to list DeH resource types. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3043 |
Failed to list dedicated host types. Try again later or contact customer service. |
Failed to list DeH types. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3044 |
Failed to update dedicated host. Try again later or contact customer service. |
Failed to update the DeH. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3045 |
Failed to list dedicated host servers. Try again later or contact customer service. |
Failed to list DeH servers. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3046 |
Failed to list dedicated host resource type flavors. Try again later or contact customer service. |
Failed to list the flavors of DeH resource types. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3047 |
Failed to get domain name. Please check if the domain name is correct. |
Obtain domain name failed. |
Check whether the domain name is correct. |
500 |
DEH.3048 |
Failed to get dedicated hosts version information. Try again later or contact customer service. |
Obtain version info failed. |
For details, see the returned error message or contact technical support. |
404 |
DEH.3049 |
The requested version is not supported. Try again later or contact customer service. |
The version is not supported. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3050 |
Request api version is incorrect. Please check if the api version in the request is correct. |
Requested version information is incorrect. |
Check whether the version information in the request is correct. |
400 |
DEH.3051 |
Failed to list dedicated host resources. Try again later or contact customer service. |
Failed to list DeH resources. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3052 |
Authentication failed. Try again later or contact customer service. |
Failed to escalate permissions. |
For details, see the returned error message or contact technical support. |
400 |
DEH.3054 |
Failed to terminate the dedicated host server. Try again later or contact customer service. |
Failed to terminate the DeH. |
For details, see the returned error message or contact technical support. |
400 |
DEH.4001 |
Failed to delete the dedicated host because it has associated instances. Please delete all associated instances in the current dedicated host and try again. |
Failed to delete the DeH associated with an instance. |
Delete all associated instances from the DeH and try again. |
400 |
DEH.4002 |
Releasing dedicated hosts in prepaid charging mode is not supported, please check the charging model. |
Prepaid DeHs cannot be released. |
Yearly/Monthly DeHs cannot be released. Check the billing mode. |
400 |
DEH.4003 |
Failed to create the dedicated host due to no flavor matching. Try again later or contact customer service. |
Failed to create a DeH because no available flavor is matched. |
For details, see the returned error message or contact technical support. |
400 |
DEH.4004 |
Please check whether the current region supports the current charging mode. |
The billing mode is not supported. |
Check whether the current region supports the current billing mode. |
400 |
DEH.4005 |
An error has occurred in order submission. Try again later or contact customer service. |
Failed to submit the order. |
For details, see the returned error message or contact technical support. |
400 |
DEH.4006 |
An error has occurred when querying dedicated hosts by tags. Try again later or contact customer service. |
Failed to query DeHs by tag. |
For details, see the returned error message or contact technical support. |
400 |
DEH.4007 |
An error has occurred when adding or removing dedicated host tags. Try again later or contact customer service. |
Failed to add or delete a DeH tag. |
For details, see the returned error message or contact technical support. |
400 |
DEH.4008 |
An error has occurred while querying the dedicated host metadata. Try again later or contact customer service. |
Failed to query DeH metadata. |
For details, see the returned error message or contact technical support. |
400 |
DEH.4009 |
Tag policy compliance verification failed. Please check the tag policy or contact technical support. |
Failed to pass the compliance verification of the tag policy. |
Change the tag policy or contact technical support. |
400 |
DEH.4010 |
Failed to list dedicated host types. Try again later or contact customer service. |
Failed to list DeH types. |
For details, see the returned error message or contact technical support. |
403 |
Pdp.0001 |
API authentication failed. Try again later or contact customer service. |
Fine-grained authentication failed. |
For details, see the returned error message or contact technical support. |
400 |
CMM.0101 |
Please check if the parameters in the request are correct. |
Invalid parameters. |
Check whether the parameters in the request are correct. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot