ServiceComb Error Codes

Common error codes

400

400001

Bad Request

Invalid parameter.

Change parameters as prompted.

404

404001

Not Found

The resource does not exist.

Enter valid search criteria.

409

409001

Conflict

The resource already exists.

Do not create the same record.

500

500003

Internal Server Error

Internal server error.

Contact technical support engineers.

Microservices

400

400002

Bad Request

The service is unhealthy.

Try again later or contact technical support engineers.

400010

Bad Request

The service already exists.

Modify the service ID or microservice description in the body of the request for creating a microservice.

400011

Bad Request

No available backend instance.

Try again later or contact technical support engineers.

400012

Bad Request

The service does not exist.

Enter a valid service ID.

400013

Bad Request

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

Bad Request

The schema ID does not exist.

Enter a valid schema ID.

400015

Bad Request

The schema cannot be modified.

The schema has been registered and cannot be modified.

400016

Bad Request

The schema does not exist.

Register the schema first.

400017

Bad Request

The instance does not exist.

Enter a valid instance ID.

400018

Bad Request

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

Bad Request

The rule already exists.

The rule is repeatedly created. Generally, this error can be ignored.

400020

Bad Request

Blacklist and whitelist error.

Modify the parameter value based on the error message.

400021

Bad Request

The rule cannot be modified.

You can modify the microservice information only after changing the version number.

400022

Bad Request

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

Bad Request

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

Bad Request

Insufficient permissions.

Use a proper account to perform operations.

400025

Bad Request

The port already exists.

Check whether the port is occupied by another instance.

400026

Bad Request

The microservice instance does not exist.

Enter a correct version number or range.

400100

Bad Request

Insufficient quota.

The quotas of resources such as microservices, instances, or schemas are insufficient. Delete some resources and create again.

401

401204

Unauthorized

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 Microservice Engine.

401201

Unauthorized

Unauthorized.

Enter a valid authorization.

403

403001

Forbidden

Insufficient permissions.

Use a proper account to perform operations.

500

500011

Internal Server Error

The registry service is unavailable.

Contact technical support engineers.

500101

Internal Server Error

No quota.

Try again later or contact technical support engineers.

500605

N/A

Failed to connect to etcd of the configuration center.

Try again later or contact technical support engineers.

Authentication

401

401202

Unauthorized

Incorrect account name or password.

Enter the correct account name and password.