- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Before You Start
- Permissions Management
-
Exclusive ServiceComb Engine
- Creating a ServiceComb Engine
-
Managing ServiceComb Engines
- Viewing ServiceComb Engine Information
- Obtaining the Service Center Address of a ServiceComb Engine
- Obtaining the Configuration Center Address of a ServiceComb Engine
- Viewing the Instance Quota of a ServiceComb Engine
- Viewing the Configuration Item Quota of a ServiceComb Engine
- Configuring Backup and Restoration of a ServiceComb Engine
- Managing Public Network Access for a ServiceComb Engine
- Viewing ServiceComb Engine Operation Logs
- Upgrading a ServiceComb Engine Version
- Deleting a ServiceComb Engine
- Changing ServiceComb Engine Specifications
- Managing Security Authentication for a ServiceComb Engine
- Managing Tags
- Using ServiceComb Engines
- Registry/Configuration Center
- Key Operations Recorded by CTS
-
Best Practices
- CSE Best Practices
-
ServiceComb Engines
-
ServiceComb Engine Application Hosting
- Hosting Spring Cloud Applications Using Spring Cloud Huawei SDK
- Hosting a Java Chassis Application
-
ServiceComb Engine Application Hosting
- Registry/Configuration Centers
-
Developer Guide
- Overview
- Developing Microservice Applications
- Preparing the Environment
- Connecting Microservice Applications
- Deploying Microservice Applications
- Using ServiceComb Engine Functions
- Appendix
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Examples
-
CSE API
- API Calling
- Dynamic Configuration
-
Engine Management
- Querying the Flavor List of a Microservice Engine
- Querying the Microservice Engine List
- Creating a Microservice Engine
- Querying Microservice Engine Details
- Querying Details About a Microservice Engine Job
- Querying Details About the Microservice Engine Quota
- Deleting a Microservice Engine
- Upgrading a Microservice Engine
- Updating Microservice Engine Configurations
- Changing Microservice Engine Specifications
- Retrying an Exclusive ServiceComb Engine Job
- Updating Microservice Engine Details
- Querying the Engine Job List
- Querying an RBAC Token
-
Microservice Governance
- Querying the Governance Policy List
- Creating a Dark Launch Policy
- Querying a Dark Launch Policy
- Deleting a Dark Launch Policy
- Changing a Governance Policy
- Deleting a Governance Policy
- Querying Governance Policy Details
- Creating a Governance Policy
- Querying the Governance Policy List of a Specified Kind
- Querying Microservice Thresholds in Batches
- Querying Microservice Reporting Information
- Querying the Reported Information List
- Nacos API
-
ServiceComb API
- API Calling
- Authentication
-
Microservice
- Querying Information About a Microservice
- Deleting Definition Information About a Microservice
- Querying Information About All Microservices
- Creating Static Information for a Microservice
- Deleting Static Information About Microservices in Batches
- Modifying Extended Attributes of a Microservice
- Querying the Unique Service or Schema ID of a Microservice
- Schema
-
Microservice Instance
- Registering a Microservice Instance
- Querying a Microservice Instance Based on service_id
- Deregistering a Microservice Instance
- Querying Details About a Microservice Instance
- Modifying the Extended Information About a Microservice Instance
- Modifying Status of a Microservice Instance
- Sending Heartbeat Information
- Querying a Microservice Instance by Filter Criteria
- Querying Microservice Instances in Batches
- Dependency
- Configuration Management
- Appendixes
- Change History
- SDK Reference
-
FAQs
- Precautions When Using Huawei Cloud CSE
- Nacos Engines
-
ServiceComb Engines
- How Do I Perform Local Development and Testing?
- How Can I Handle a Certificate Loading Error?
- What If the Header Name Is Invalid?
- What Is the Performance Loss of Mesher?
- Why Is "Version validate failed" Displayed When I Attempt to Connect to the Service Center?
- Why Is "Not enough quota" Displayed When I Attempt to Connect to the Service Center?
- What Should I Do If the Service Registration Fails After IPv6 Is Enabled for the Exclusive ServiceComb Engine with Security Authentication Enabled?
- What Is Service Name Duplication Check?
- Why Do I Have to Define Service Contracts?
- Why Are Microservice Development Framework and Netty Versions Unmatched?
- What Do I Need to Know Before Upgrading an Exclusive ServiceComb Engine?
- What Must I Check Before Migrating Services from the Professional to the Exclusive Microservice Engine?
- Why Is "Duplicate cluster name" Displayed?
- Error Message "the subnet could not be found" Is Displayed When the Access Address Fails to Be Processed During Engine Creation
- Why Is Error "does not match rule: {Max: 100, Regexp: ^[a-zA-Z0-9]{1,160}$|^[a-zA-Z0-9][a-zA-Z0-9_\-.]{0,158}[a-zA-Z0-9]$}"}" Reported?
- What Should I Do If SpringCloud Applications Fail to Connect to the Configuration Center of ServiceComb Engine 2.x?
- Why Could My the Global Configuration Not Be Modified?
- Obtain Configurations Failed
- Videos
- General Reference
Show all
Copied.
Error Codes
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 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. |
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. |
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