- 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.
ServiceComb 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.
Category |
Status Code |
Error Code |
Error Message |
Description |
Solution |
---|---|---|---|---|---|
Common error codes |
400 |
400001 |
Invalid parameter(s) |
Invalid parameter. |
Change parameters as prompted. |
404 |
404001 |
ErrRecoudNotExists |
The resource does not exist. |
Enter valid search criteria. |
|
409 |
409001 |
ErrRecordAlreadyExists |
The resource already exists. |
Do not create the same record. |
|
500 |
500003 |
Internal server error |
Internal server error. |
Contact technical support. |
|
Microservice |
400 |
400002 |
ErrUnhealthy |
The service is unhealthy. |
Try again later or contact technical support. |
400010 |
Micro-service already exists |
The service already exists. |
Modify the service ID or microservice description in the body of the request for creating a microservice. |
||
400011 |
ErrUnavailableBackend |
No available backend instance. |
Try again later or contact technical support. |
||
400012 |
Micro-service does not exist |
The service does not exist. |
Enter a valid service ID. |
||
400013 |
Micro-service has deployed instance(s) |
The microservice cannot be deleted because instances have been deployed. |
Take the instance offline and then delete the microservice. Alternatively, forcibly delete the microservice by setting the query parameter force to true in the URL. |
||
400014 |
Undefined schema id |
The schema ID does not exist. |
Enter a valid schema ID. |
||
400015 |
Not allowed to modify schema |
The schema cannot be modified. |
The schema has been registered and cannot be modified. |
||
400016 |
Schema does not exist |
The schema does not exist. |
Register the schema first. |
||
400017 |
Instance does not exist |
Instance does not exist. |
Enter a valid instance ID. |
||
400018 |
ErrTagNotExists |
The tag does not exist. |
This error code is usually generated for a query API, indicating that the tag does not exist. The service performs subsequent processing based on the returned value. |
||
400019 |
ErrRuleAlreadyExists |
The rule already exists. |
The rule is repeatedly created. Generally, this error can be ignored. |
||
400020 |
ErrBlackAndWhiteRule |
Blacklist and whitelist error. |
Modify the parameter value based on the error message. |
||
400021 |
ErrModifyRuleNotAllow |
The rule cannot be modified. |
You can modify the microservice information only after changing the version number. |
||
400022 |
ErrRuleNotExists |
The rule does not exist. |
This error code is usually generated for a query API, indicating that the rule does not exist. The service performs subsequent processing based on the returned value. |
||
400023 |
Cosumer(s) depends on this micro-service |
The microservice cannot be deleted because it is the dependent service of other microservices. |
You can forcibly delete microservices by setting the query parameter force to true in the URL. |
||
400024 |
ErrPermissionDeny |
Insufficient permissions. |
Use a proper account to perform operations. |
||
400025 |
ErrEndpointAlreadyExists |
The port already exists. |
Check whether the port is occupied by another instance. |
||
400026 |
Micro-service version does not exist |
The microservice instance does not exist. |
Enter a correct version number or range. |
||
400100 |
Not enough quota |
Insufficient quota. |
The quotas of resources such as microservices, instances, or schemas are insufficient. Delete some resources and create again. |
||
401 |
401204 |
No authorization header |
Unauthorized. |
This parameter is mandatory if security authentication is enabled for the microservice engine. Otherwise, this parameter is not required. The token of the microservice engine with security authentication enabled is in the following format: Authorization:Bearer {Token} For details about how to obtain the token, see Obtaining the User Token of an Exclusive ServiceComb Engine. |
|
401201 |
Request unauthorized |
Unauthorized. |
Enter a valid authorization. |
||
403 |
403001 |
ErrForbidden |
Insufficient permissions |
Use a proper account to perform operations. |
|
500 |
500011 |
Registry service is unavailable |
The registry service is unavailable. |
Contact technical support. |
|
500101 |
ErrUnavailableQuota |
No quota. |
Try again later or contact technical support. |
||
500605 |
NA |
Failed to connect to etcd of the configuration center. |
Try again later or contact technical support. |
||
Authentication |
401 |
401202 |
User name or password is wrong |
Incorrect account name or password. |
Enter the correct account name and password. |
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