Error Codes
Format of an Error Response Body
If an error occurs during API calling, the system returns an error code and message to you. The following shows the format of an error response body:
{ "error_code": "IEF.011002", "error_msg": "xxxxxxxxx" }
In the preceding information, error_code is an error code, and error_msg describes the error.
Error Code Description
If an error code starting with APIGW is returned after you call an IEF API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|
IEF.011002 |
The API is not registered. |
The API is not registered. |
Check whether the requested URL is correct. If it is correct but the error persists, contact technical support for assistance. |
IEF.011005 |
Authentication failed. |
Authentication failed. |
Use the project ID of the tenant to obtain the token and try again. If the token is correct but the error persists, contact technical support for assistance. |
IEF.100004 |
The request offset does not comply with specifications. |
The requested offset does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100005 |
The request limit does not comply with specifications. |
The requested limit does not meet the specifications. |
Locate the error cause based on the returned error information, modify the parameter value, and try again. |
IEF.100009 |
The attached volume does not meet specifications. |
The attached volume does not meet the specifications. |
Enter a correct volume type. |
IEF.100010 |
The application version does not meet specifications. |
The application version does not meet the specifications. |
Enter a correct application version. |
IEF.100011 |
The application template name does not comply with the specifications. |
The application template name does not meet the specifications. |
Enter a correct application template name and try again. |
IEF.100012 |
The resource name does not comply with the specifications. |
The resource name does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100013 |
The environment variable of the application version does not comply with the specifications. |
The environment variable of the application version does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100020 |
The application icon storage URL does not meet specifications. |
The application icon storage URL does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100021 |
The description or remarks of the device binding node do not comply with the specifications. |
The description or remarks of the binding relationship between the device and node do not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100040 |
Invalid image path |
The image path is invalid. |
Enter a correct image path and try again. |
IEF.100047 |
The application template visualization parameter type is not supported. |
The type of the application template visualization parameter is not supported. |
Correctly set the parameter. The template visualization property value can only be public, private, shared, or left empty. |
IEF.100058 |
The device has been bound to a node. |
The device has been bound to a node. |
Unbind the device from the node and then delete the device. |
IEF.100065 |
The system subscription ID does not meet requirements. |
The system subscription ID does not meet the specifications. |
Correctly set the message subject according to the API Reference and try again. |
IEF.100067 |
The node cannot be deleted because it has bound devices. |
The node cannot be deleted because it has bound devices. |
Log in to the IEF console, go to the Edge Nodes page, click the target node to open its node details page, and check whether the node has any bound devices. If yes, unbind the devices from the node and try again. |
IEF.100100 |
The request parameter is incorrect. |
The request parameter is incorrect. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100112 |
The configmap/secret of the mounted volume is incorrect. |
The ConfigMap or secret of the attached volume is incorrect. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100113 |
The resource configuration of the application version does not comply with the specifications. |
The resource configuration of the application version does not meet the specifications. |
Enter correct resource configuration for the application version. |
IEF.100119 |
The name of the application configuration item does not comply with the specifications. |
The ConfigMap name does not meet the specifications. |
Enter a correct ConfigMap name. |
IEF.100120 |
The key of the application configuration item does not comply with the specifications. |
The key of the ConfigMap does not meet the specifications. |
Enter a correct key for the ConfigMap. |
IEF.100121 |
The value of the application configuration item does not meet the specifications. |
The value of the ConfigMap does not meet the specifications. |
Enter a correct value for the ConfigMap. |
IEF.100122 |
The configuration data of the application configuration item does not comply with the specifications. |
The configuration data of the ConfigMap does not meet the specifications. |
Enter correct ConfigMap data. |
IEF.100126 |
Insufficient resource quota |
The resource quota is insufficient. |
Change the parameter value based on the error cause described in the response body to ensure that the quota is sufficient and try again. |
IEF.100133 |
The probe configuration of the application version does not meet specifications. |
The probe configuration of the application version does not meet the specifications. |
Correctly set the probe properties. Only exec, http_get, and tcp_socket_port are supported. |
IEF.100148 |
The name of the application key does not comply with the specifications. |
The application secret name does not meet the specifications. |
Enter a correct secret name. |
IEF.100149 |
The application key data is invalid. |
Invalid application secret data. |
Enter correct secret data. |
IEF.100150 |
The application key data type does not meet specifications. |
The application secret type does not meet the specifications. |
Enter a correct secret type. |
IEF.100151 |
The application key does not comply with the specifications. |
The application secret key does not meet the specifications. |
Enter a correct secret key. |
IEF.100152 |
The application key value does not meet specifications. |
The application secret value does not meet the specifications. |
Enter a correct secret value. |
IEF.100155 |
The key is in use and cannot be deleted. |
The secret is in use and cannot be deleted. |
Stop using the secret and then delete it. |
IEF.100159 |
The application configuration item is in use and cannot be deleted. |
The ConfigMap is in use and cannot be deleted. |
Stop using the ConfigMap and then delete it. |
IEF.100161 |
The node is being updated. The application cannot be deleted. |
The application cannot be deleted because the node is being updated. |
Stop updating the node and then delete the application. |
IEF.100162 |
The advanced configuration parameters of the application version do not comply with the specifications. |
The advanced configuration parameters of the application version do not meet the specifications. |
Enter correct advanced configuration parameters for the application version. |
IEF.100163 |
The node operation type is not supported. |
The node operation type is not supported. |
Specify a correct node operation type. |
IEF.100165 |
The application key data includes at least one key-value pair. |
The application secret data must include at least one key-value pair. |
Check whether at least one secret data record exists. |
IEF.100166 |
The node version is earlier than 2.1.5. The node cannot be updated. |
The node cannot be updated because its version is earlier than 2.1.5. |
Upgrade the node to the latest version. You can view the node version and upgrade records on the node details page. |
IEF.100167 |
Invalid application version schema |
Invalid application version architecture. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.100404 |
The resource does not exist. |
The resource does not exist. |
Ensure that the parameters of the requested resource are correct. If they are correct but the error persists, contact technical support for assistance. |
IEF.100412 |
Failed to query K8S cluster resources. |
Failed to query the Kubernetes cluster resources. |
An internal error occurred. Contact technical support for assistance. |
IEF.101001 |
[Service Grid] Failed to convert the structure. |
[Service mesh] Failed to convert the structure. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.101002 |
[Service Grid] The service already exists. |
[Service mesh] The service already exists. |
Modify service parameters or delete unnecessary services and try again. |
IEF.101003 |
[Service Grid] The associated application does not exist. |
[Service mesh] The associated application does not exist. |
Check whether the associated application exists. Enter the correct associated application and try again. |
IEF.101004 |
[Service Grid] Failed to Create K8S Cluster Resources |
[Service mesh] Failed to create Kubernetes cluster resources. |
An internal error occurred. Contact technical support for assistance. |
IEF.101005 |
[Service Grid] Failed to Delete K8S Cluster Resources |
[Service mesh] Failed to delete Kubernetes cluster resources. |
An internal error occurred. Contact technical support for assistance. |
IEF.101006 |
[Service Grid] Failed to Query K8S Cluster Resources |
[Service mesh] Failed to query Kubernetes cluster resources. |
An internal error occurred. Contact technical support for assistance. |
IEF.101007 |
[Service Grid] Failed to Update K8S Cluster Resources |
[Service mesh] Failed to update Kubernetes cluster resources. |
An internal error occurred. Contact technical support for assistance. |
IEF.104004 |
The resource to be created already exists. |
The resource to be created already exists. |
Modify resource parameters or delete unnecessary resources and try again. |
IEF.110074 |
The specified application template cannot be found. |
The specified application template cannot be found. |
Check whether the specified application template exists. Enter the correct application template and try again. |
IEF.110076 |
The specified app version cannot be found. |
The specified application version cannot be found. |
Check whether the specified application version exists. Enter the correct application version and try again. |
IEF.110080 |
Specified device not found |
The specified device is not found. |
Check whether the specified device exists. Enter the correct device and try again. |
IEF.110081 |
The specified device template is not found. |
The specified device template is not found. |
Check whether the specified device template exists. Enter the correct device template and try again. |
IEF.120001 |
Internal error |
An internal error occurred. |
An internal error occurred. Contact technical support for assistance. |
IEF.130089 |
Insufficient resource quota |
The resource quota is insufficient. |
Ensure that the quota is sufficient and try again. |
IEF.300000 |
Failed to obtain request parameters. |
Failed to obtain request parameters. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300001 |
The request parameter message endpoint does not meet the requirements. |
The message endpoint in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300002 |
The name of the request parameter message endpoint does not comply with the specifications. |
The message endpoint name in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300003 |
The description of the request parameter message endpoint does not comply with the specifications. |
The message endpoint description in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300004 |
The request parameter message endpoint type is not supported. |
The message endpoint type in the request is not supported. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300005 |
The endpoint attribute of the request parameter does not comply with the specifications. |
The message endpoint property in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300006 |
The request parameter message endpoint already exists. |
The message endpoint in the request already exists. |
Change a message endpoint name, or delete the existing message endpoint without affecting services, then try again. |
IEF.300007 |
The specified message endpoint does not exist. |
The specified message endpoint does not exist. |
Check whether the specified message endpoint is deleted. Enter the correct message endpoint and try again. |
IEF.300008 |
The message endpoint is in use and cannot be deleted. |
The message endpoint is in use and cannot be deleted. |
Stop using the message endpoint or wait until the message endpoint is no longer used, and then delete the message endpoint. |
IEF.300009 |
Message Endpoint Quota Insufficient |
The message endpoint quota is insufficient. |
Reduce the resource usage or contact technical support to increase the quota. |
IEF.300101 |
The request parameter message route does not comply with the specifications. |
The message route in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300102 |
The routing name of the request parameter does not comply with the specifications. |
The message route name in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300103 |
The message route description of the request parameter does not comply with the specifications. |
The message route description in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300104 |
The source endpoint ID of the message route does not comply with the specifications. |
The source endpoint ID of the message route does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300105 |
The source endpoint resource of the message route does not meet the specifications. |
The source endpoint resource of the message route does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300106 |
The destination endpoint ID of the message route does not comply with the specifications. |
The destination endpoint ID of the message route does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300107 |
The destination endpoint resource of the message route does not meet the specifications. |
The destination endpoint resource of the message route does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300108 |
The specified message route already exists. |
The specified message route already exists. |
Change a message route name, or delete the existing message route without affecting services, then try again. |
IEF.300109 |
The specified message route does not exist. |
The specified message route does not exist. |
Check whether the specified message route is deleted. Enter the correct message route and try again. |
IEF.300110 |
Failed to obtain the message routing request action. |
Failed to obtain the message routing request action. |
Set the message routing action correctly and try again. |
IEF.300111 |
The message routing request action is not supported. |
The message routing request action is not supported. |
Set the message routing action correctly and try again. |
IEF.300112 |
The message route is being enabled and cannot be enabled. The message route is being disabled and cannot be disabled. |
The message route is already enabled, or the message route is already disabled. |
Log in to the IEF console, locate the specified route on the Routes page, and check its status. If the route has been enabled, do not enable it again. |
IEF.300113 |
Message routing quota is insufficient. |
The message route quota is insufficient. |
Reduce the resource usage or contact technical support to increase the quota. |
IEF.300114 |
The specified DIS channel does not exist. |
The specified DIS stream does not exist. |
Check whether the specified DIS stream is deleted. Enter the correct DIS stream and try again. |
IEF.300115 |
Invalid DIS channel requested |
The requested DIS stream is invalid. |
Check whether the specified DIS stream is deleted. Enter the correct DIS stream and try again. |
IEF.300116 |
The requested servicebus path does not meet specifications. |
The requested Service Bus path does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300117 |
The requested eventbus topic does not meet specifications. |
The requested EventBus topic does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300118 |
The requested eventbus topic already exists. |
The requested EventBus topic already exists. |
Change an EventBus topic, or delete the existing EventBus topic without affecting services, then try again. |
IEF.300119 |
The requested APIGW resource does not meet specifications. |
The requested API Gateway resource does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300120 |
The requested MQTT topic does not meet specifications. |
The requested MQTT topic does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300121 |
Duplicate MQTT topic data. |
The requested MQTT topic already exists. |
Change an MQTT topic, or delete the existing MQTT topic without affecting services, then try again. |
IEF.300122 |
The REST path of the request parameter does not meet the specifications. |
The REST path in the request does not meet the specifications. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300123 |
Duplicate REST path data in the request parameter. |
The REST path in the request already exists. |
Change a REST path, or delete the existing REST path without affecting services, then try again. |
IEF.300124 |
The request parameter device is faulty. |
The device in the request is faulty. |
Locate the error cause based on the returned error information or the API Reference, modify the parameter value, and try again. |
IEF.300125 |
The requested device does not exist. |
The requested device does not exist. |
Check whether the requested device is deleted. Enter the correct device and try again. |
IEF.300126 |
The requested edge node does not exist. |
The requested edge node does not exist. |
Check whether the requested edge node is deleted. Enter the correct edge node and try again. |
IEF.300127 |
The requested edge node conflicts. |
The requested edge node already exists. |
Change an edge node, or delete the existing edge node without affecting services, then try again. |
IEF.300128 |
When the request destination port type is tsdb, the projectID is empty. |
The project ID is empty when the type of the requested destination port is tsdb. |
Enter a correct project ID and try again. |
IEF.300129 |
When the request destination port type is tsdb, projectID is invalid. |
The project ID is invalid when the type of the requested destination port is tsdb. |
Enter a correct project ID and try again. |
IEF.300130 |
When the request destination port type is tsdb, domain_id is invalid. |
The domain ID is invalid when the type of the requested destination port is tsdb. |
Enter a correct domain ID and try again. |
IEF.300131 |
The URL is invalid when the request destination port type is tsdb. |
The URL is invalid when the type of the requested destination port is tsdb. |
Enter a correct URL and try again. |
IEF.300132 |
When the request destination port type is tsdb, the label is invalid. |
The tag is invalid when the type of the requested destination port is tsdb. |
Enter a correct tag and try again. |
IEF.300133 |
The requested edge node does not exist. |
The requested edge node does not exist. |
Check whether the requested edge node is deleted. Enter the correct edge node and try again. |
IEF.300134 |
When the request destination port type is tsdb, the resource does not meet the specifications. |
The resource does not meet the specifications when the type of the requested destination port is tsdb. |
Enter a correct resource and try again. |
IEF.300135 |
The nodeId is empty or does not comply with the specifications. |
The node ID is empty or does not meet the specifications. |
Enter a correct node ID and try again. |
IEF.300201 |
The quota type is incorrect. |
Incorrect quota type. |
Change the quota type based on the returned error information or the API Reference and try again. |
IEF.310000 |
The request does not contain a token. |
The request does not carry a token. |
Ensure that the request header contains the correct token. |
IEF.310001 |
Failed to obtain the token in the request. |
Failed to obtain the token in the request. |
Ensure that the entered token is correct or obtain a new token. If the token is correct but the error persists, contact technical support for assistance. |
IEF.310002 |
The token has expired. |
The token has expired. |
Obtain a new token. |
IEF.310003 |
Failed to connect to the database. |
Failed to connect to the database. |
An internal error occurred. Contact technical support for assistance. |
IEF.330000 |
Failed to connect to the DIS service. |
Failed to connect to the DIS service. |
An internal error occurred. Contact technical support for assistance. |
IEF.330001 |
Failed to connect to the edgebroker. |
Failed to connect to the edgebroker. |
An internal error occurred. Contact technical support for assistance. |
IEF.340000 |
Failed to convert the token. |
Failed to convert the token. |
Ensure that the token is correct or contact technical support for assistance. |
IEF.340001 |
Internal error |
An internal error occurred. |
An internal error occurred. Contact technical support for assistance. |
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