Error Codes

Updated on 2025-04-25 GMT+08:00

View PDF

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.

**Table 1** Engine management error codes
Status Codes	Error Code	Error Message	Description	Solution
400	SVCSTG.00501134	The engine type is left blank.	Invalid engine type.	The engine type field is the specType field in the request query. Set it to a valid value (for example, CSE2) and try again. For example, to query the specifications supported by CSE, set specType to CSE2.
400	SVCSTG.00501111	Duplicate engine instance name.	Duplicate engine instance name.	Change the engine name.
400	SVCSTG.00501112	Insufficient engine instance quota.	Insufficient engine instance quota	Contact technical support to increase the engine instance quota or delete unnecessary engine instances.
400	SVCSTG.00501133	The number of engines has reached the upper limit of the site.	The number of engines reaches the upper limit of the site.	Contact technical support.
400	SVCSTG.00501103	Engine payment is empty or is invalid.	Empty or invalid billing mode.	Input the billing mode parameter of the engine and check whether the user can create such an engine.
400	SVCSTG.00501104	Incorrect format of the engine instance specifications.	Incorrect engine instance flavor format.	Invalid flavor. Enter a valid flavor.
400	SVCSTG.00501105	Incorrect AZ format.	Incorrect AZ format	Specify a valid AZ in the request parameter. The AZ field is a string array and cannot be empty. The number of AZ name levels ranges from 1 to 3.
400	SVCSTG.00501117	The engine in the current state cannot be deleted.	The engine in this state cannot be deleted.	Wait until the engine state changes to Available, Unavailable, or Creation failed, and then try again.
400	SVCSTG.00501152	Incorrect task ID format.	Incorrect task ID format.	Use the job ID returned by the APIs for creating and deleting an engine.
400	SVCSTG.00501153	No task found.	Failed to find the task.	Use the job ID returned by the APIs for creating and deleting an engine.
400	SVCSTG.00501149	Abnormal node status.	Abnormal engine node.	Try again later or contact technical support.
400	SVCSTG.00501116	Failed to find the engine instance.	Failed to find the engine instance.	Check whether the input engine ID is correct. Use the username and password of the tenant to log in to CSE and check whether the current tenant has an engine with the corresponding ID.
400	SVCSTG.00501201	The name must contain 3 to 24 characters, including letters, digits, and hyphens (-). It must start with a letter but not end with a hyphen (-). The name cannot be default or the current engine name.	Incorrect format of the peer engine instance name.	The peer engine instance name must contain 3 to 24 characters, including letters, digits, and hyphens (-), and must start with a letter but cannot end with a hyphen (-). The name cannot be default and must be different from the current engine instance name.
400	SVCSTG.00501202	An HA engine can be the peer engine.	The peer engine must be an HA engine.	The engine must be an HA engine. Enter the engine flavor again.
400	SVCSTG.00501203	The peer engine must be in a single AZ.	The peer engine must be in a single AZ.	The AZs must be single AZs. Enter the AZ list again.
500	SVCSTG.00500400	Internal service request parameter error.	Incorrect internal request parameter of the service.	Check the error message. If the parameter is invalid, check whether the input argument is correct. For other errors, contact technical support.

**Table 2** Dynamic configuration error codes
Status Codes	Error Code	Error Message	Description	Solution
400	SVCSTG.00400649	Key/value length exceeds the upper limit.	Too long key or value.	The configuration item contains 1 to 2048 characters, including digits, letters, and special characters (.-_:[]). The value can contain 1 to 131072 characters, including digits, letters, and special characters ('~!@#$%^&*()_\{}\|:"<>?`-[],./=).
400	SVCSTG.00400650	Invalid configuration file.	Invalid configuration file.	The uploaded file is invalid.
400	SVCSTG.00400651	The file is empty or in an incorrect format.	The file is empty or in an incorrect format.	The uploaded file is empty or not in JSON format.
400	SVCSTG.00400652	Configuration item key/value is null or not a string.	The key or value is empty or is not a string.	The uploaded key or value is null or is not a string.
400	SVCSTG.00400653	Invalid label or body.	Invalid label or body.	Enter a valid body or label in the query parameter.
400	SVCSTG.00400100	Invalid parameter(s)	Invalid parameter.	Change parameters as prompted.
404	SVCSTG.00400106	Record does not exist	The resource does not exist.	Enter valid search criteria.
409	SVCSTG.00400107	ecord already exist	The resource already exists.	Do not create the same record.
500	SVCSTG.00300605	Failed to connect the configuration center to ETCD.	Internal Server Error	Contact technical support engineers.
400	SVCSTG.00300401	Invalid token	Unauthorized	Enter a correct token.

Parent topic: Appendixes

Previous topic: Status Codes

Next topic: ServiceComb Error Codes

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot