Updated on 2023-10-09 GMT+08:00

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 Code

Error Codes

Error Message

Description

Solution

100

BCS.4006012

Invalid channel name.

Invalid channel name.

Enter a valid channel name.

400

BCS.2001001

BCS service modified.

BCS service modified.

The BCS service can work properly.

400

BCS.4001001

Operation failed. The BCS service is being created.

Operation failed. The BCS service is being created.

Wait until the service is created.

400

BCS.4001002

Operation failed. The BCS service is being upgraded.

Operation failed. The BCS service is being upgraded.

Wait until the upgrade is complete.

400

BCS.4001003

Operation failed. The BCS service is being deleted.

Operation failed. The BCS service is being deleted.

Wait until the deletion is complete.

400

BCS.4001006

Failed to delete the SFS file system because the CCE API or the cluster status is abnormal.

Failed to delete the SFS file system because the CCE API or the cluster status is abnormal.

Manually delete the SFS file system. Procedure: Log in to the CCE console, choose Resource Management > Storage, and locate the file system in the cluster corresponding to the BCS service. For an SFS file system, click Delete in the Operation column. For an SFS Turbo file system, click Unbind and then go to the SFS console to delete the file system.

400

BCS.4001007

Services billed in the yearly/monthly mode cannot be deleted.

Services billed in the yearly/monthly mode cannot be deleted.

Services billed in the yearly/monthly mode cannot be deleted. They can only be unsubscribed from on the console.

400

BCS.4001008

Operation failed. Bind an EIP to at least one node in the cluster and try again.

Operation failed. Bind an EIP to at least one node in the cluster and try again.

Bind an EIP to at least one node in the cluster and try again. Procedure: Log in to the CCE console. Choose Resource Management > Nodes. Locate the nodes in the cluster corresponding to the service, and perform the following steps on any node: On the node details page, click the node name. On the displayed ECS console, click the ECS name. On the ECS details page, click the EIPs tab. Click Bind EIP.

400

BCS.4001009

Operation failed. Bind an EIP to each node in the cluster and try again.

Operation failed. Bind an EIP to each node in the cluster and try again.

Bind an EIP to each node in the cluster and try again. Procedure: Log in to the CCE console. Choose Resource Management > Nodes. In the cluster corresponding to the service, locate the nodes that have not been bound with EIPs, and perform the following steps on each node: On the node details page, click the node name. On the displayed ECS console, click the ECS name. On the ECS details page, click the EIPs tab. Click Bind EIP.

400

BCS.4001010

Failed to download the BCS certificate because the etcd connection is abnormal.

Failed to download the BCS certificate because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001011

Operation failed. The service does not exist or has been deleted. Refresh the page.

Operation failed. The service does not exist or has been deleted. Refresh the page.

Wait for a few moments and refresh the page.

400

BCS.4001015

Failed to obtain the peer information because the etcd connection is abnormal.

Failed to obtain the peer information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001018

Operation failed. A service with the same name already exists. Enter another name and try again.

Operation failed. A service with the same name already exists. Enter another name and try again.

Change the service name and try again.

400

BCS.4001019

Failed to obtain the image version for upgrade because the required image is not in the image repository or the version configuration is incorrect.

Failed to obtain the image version for upgrade because the required image is not in the image repository or the version configuration is incorrect.

Check the service version configuration and ensure that the image required for the upgrade is in the image repository.

400

BCS.4001020

Operation failed. The service status is abnormal or the service is being processed. Try again later.

Operation failed. The service status is abnormal or the service is being processed. Try again later.

Try again later.

400

BCS.4001021

Failed to add the peer to the channel because the CCE API, cluster status, or etcd connection is abnormal.

Failed to add the peer to the channel because the CCE API, cluster status, or etcd connection is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001025

Invalid EIP. The EIP may have been unbound from the cluster. Check the EIP binding of the cluster.

Invalid EIP. The EIP may have been unbound from the cluster. Check the EIP binding of the cluster.

Log in to the CCE console, choose Resource Management > Clusters, and click the cluster corresponding to the service. Check whether the cluster nodes have been bound with EIPs. If not, bind EIPs to the cluster nodes.

400

BCS.4001026

Failed to save the EIP to etcd because the etcd connection is abnormal.

Failed to save the EIP to etcd because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001027

Failed to update the EIP information in the consortium member configuration because the CCE API, cluster status, or etcd connection is abnormal.

Failed to update the EIP information in the consortium member configuration because the CCE API, cluster status, or etcd connection is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001030

Operation failed because the etcd connection check failed.

Operation failed because the etcd connection check failed.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001031

Failed to query the member details because the etcd connection is abnormal.

Failed to query the member details because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001032

You do not have the required permission.

You do not have the required permission.

Configure the permissions by following the instructions provided in BCS User Guide > Service Deployment > Prerequisites.

400

BCS.4001033

Failed to delete the member information because the etcd connection is abnormal.

Failed to delete the member information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001036

Operation failed. The notification does not exist. Refresh the page.

Operation failed. The notification does not exist. Refresh the page.

Refresh the page later.

400

BCS.4001040

Failed to decline the invitation for joining a channel. Refresh the page and check the invitation status later.

Failed to decline the invitation for joining a channel. Refresh the page and check the invitation status later.

Refresh the page and check the invitation status later.

400

BCS.4001042

Failed to query the member information because the etcd connection is abnormal.

Failed to query the member information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001043

Failed to modify the member information because the etcd connection is abnormal.

Failed to modify the member information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001044

Failed to accept the invitation. The acceptance is being processed. Refresh the page and check the invitation status later.

Failed to accept the invitation. The acceptance is being processed. Refresh the page and check the invitation status later.

Refresh the page later to view the processing result.

400

BCS.4001045

Weak password.

Weak password.

Enter a strong password.

400

BCS.4001047

Failed to modify the etcd data because the etcd connection is abnormal.

Failed to modify the etcd data because the etcd connection is abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001048

Failed to change the password because the CCE cluster is abnormal.

Failed to change the password because the CCE cluster is abnormal.

Log in to the CCE console and choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster nodes are normal. If they are abnormal, rectify the fault by referring to the CCE troubleshooting guide. After the cluster restores, try again. If the cluster nodes have been deleted, buy nodes and create a BCS service again.

400

BCS.4001049

Operation failed. The cluster status is abnormal. Check the cluster status and try again.

Operation failed. The cluster status is abnormal. Check the cluster status and try again.

Log in to the CCE console and choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster nodes are normal. If they are abnormal, rectify the fault by referring to the CCE troubleshooting guide. After the cluster restores, try again. If the cluster nodes have been deleted, buy nodes and create a BCS service again.

400

BCS.4001050

Scaling failed because the CCE API or the cluster status is abnormal.

Scaling failed because the CCE API or the cluster status is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service.

400

BCS.4001051

Scaling failed due to incorrect request parameters. Check whether the number of peers in the organization has reached the limit (5).

Scaling failed due to incorrect request parameters. Check whether the number of peers in the organization has reached the limit (5).

Ensure that the number of peers in each organization does not exceed the upper limit (5) and try again.

400

BCS.4001052

Operation failed because it timed out.

Operation failed because it timed out.

View the result later.

400

BCS.4001053

Failed to query the network storage because the CCE API or the cluster status is abnormal.

Failed to query the network storage because the CCE API or the cluster status is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service.

400

BCS.4001054

Failed to add the peer to the channel because the CCE cluster status or etcd connection is abnormal.

Failed to add the peer to the channel because the CCE cluster status or etcd connection is abnormal.

Log in to the CCE console and check whether CCE is normal. Choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001058

Failed to delete the member information because the etcd connection may be abnormal.

Failed to delete the member information because the etcd connection may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001062

The maximum number of tenants that can be invited has been reached.

The maximum number of tenants that can be invited has been reached.

Do not invite more tenants after the invitation limit has been reached.

400

BCS.4001063

The maximum number of invitation notifications that can be received has been reached.

The maximum number of invitation notifications that can be received has been reached.

Log in to the BCS console, go to the Notification Management page, and check whether the number of received invitations reaches the upper limit (100). Process the received notifications.

400

BCS.4001067

Failed to delete the notification. The etcd connection may be abnormal.

Failed to delete the notification. The etcd connection may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001069

The chaincode is being instantiated. Try again later.

The chaincode is being instantiated. Try again later.

Log in to the Chaincode Management page of the corresponding service to check the chaincode instantiation status. After the instantiation is complete, perform the operation again.

400

BCS.4001078

Failed to query the channel information because the etcd connection may be abnormal.

Failed to query the channel information because the etcd connection may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001080

Operation failed because the CCE cluster information failed to be obtained.

Operation failed because the CCE cluster information failed to be obtained.

Check if CCE is normal by trying to log in to the CCE console. If the login is successful, choose Resource Management > Clusters to check whether the cluster used by the service is normal. If the cluster is abnormal, try again after it restores.

400

BCS.4001081

Failed to obtain the invitee's organization because the etcd is abnormal.

Failed to obtain the invitee's organization because the etcd is abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001086

Permission verification failed.

Permission verification failed.

Configure the permissions by following the instructions provided in BCS User Guide > Service Deployment > Prerequisites.

400

BCS.4001088

Operation failed due to insufficient quota. Increase the quota and try again.

Operation failed due to insufficient quota. Increase the quota and try again.

Contact the administrator to increase the quota on ManageOne.

400

BCS.4001089

Deletion failed. Failed to delete the BCS information.

Deletion failed. Failed to delete the BCS information.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001090

Operation failed. No node is available in the cluster. Try again later.

Operation failed. No node is available in the cluster. Try again later.

Check whether the node is abnormal or has been deleted. Log in to the CCE console. Choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster has nodes. If not, the nodes may have been deleted. In this case, buy nodes and create a BCS service again. If the nodes are abnormal, restore the nodes as instructed by the CCE troubleshooting document and try again later.

400

BCS.4001095

Failed to delete block configurations due to etcd exceptions.

Failed to delete block configurations due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001096

Failed to delete the AgentConfig information due to etcd exceptions.

Failed to delete the AgentConfig information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001097

Failed to delete the CCE cluster occupation information due to etcd exceptions.

Failed to delete the CCE cluster occupation information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001098

Failed to delete the SDK information due to etcd exceptions.

Failed to delete the SDK information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001099

Failed to delete the channel information due to etcd exceptions.

Failed to delete the channel information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001100

Failed to delete the EIP information due to etcd exceptions.

Failed to delete the EIP information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001101

Failed to delete the port information due to etcd exceptions.

Failed to delete the port information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001102

Failed to delete the ipmapping information due to etcd exceptions.

Failed to delete the ipmapping information due to etcd exceptions.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001104

Failed to delete the deployment template because the CCE cluster status may be abnormal.

Failed to delete the deployment template because the CCE cluster status may be abnormal.

Check the CCE cluster status. Log in to the CCE console and choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, restore the cluster as instructed by the CCE User Guide and then try again.

400

BCS.4001105

Deleting the deployment template timed out because the CCE cluster status may be abnormal.

Deleting the deployment template timed out because the CCE cluster status may be abnormal.

Check the CCE cluster status. Log in to the CCE console and choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, restore the cluster as instructed by the CCE User Guide and then try again.

400

BCS.4001106

Operation failed. The cluster does not exist. Try again later.

Operation failed. The cluster does not exist. Try again later.

Log in to the CCE console and choose Resource Management > Clusters. Check if the cluster used by the BCS service exists. If the cluster does not exist, create a cluster and buy a BCS service again.

400

BCS.4001109

Operation failed. Failed to obtain the peer organization status. Try again later.

Operation failed. Failed to obtain the peer organization status. Try again later.

Try again later.

400

BCS.4001110

Failed to create CertBitConf because the network may be faulty.

Failed to create CertBitConf because the network may be faulty.

Try again later.

400

BCS.4001120

Failed to delete the service. The member failed to exit the consortium. The cluster or etcd connection is abnormal.

Failed to delete the service. The member failed to exit the consortium. The cluster or etcd connection is abnormal.

Log in to the CCE console and check whether CCE is normal. Choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001123

Failed to delete the service because the cluster has been hibernated.

Failed to delete the service because the cluster has been hibernated.

Wake up the cluster and try again. Log in to the CCE console and choose Resource Management > Clusters. Locate the cluster used by the service, choose More > Wake. After the cluster status is restored, delete the BCS service again.

400

BCS.4001130

Failed to save the node and port information because the etcd, CCE API, or cluster is abnormal.

Failed to save the node and port information because the etcd, CCE API, or cluster is abnormal.

Log in to the CCE console and check whether CCE is normal. Choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001133

Failed to save the channel information because etcd may be abnormal.

Failed to save the channel information because etcd may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001134

Failed to save the BCS information because etcd may be abnormal.

Failed to save the BCS information because etcd may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001135

Failed to save the certificate because etcd may be abnormal.

Failed to save the certificate because etcd may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001136

Failed to save bitconf because etcd may be abnormal.

Failed to save bitconf because etcd may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001137

Failed to save the deployment template because etcd may be abnormal.

Failed to save the deployment template because etcd may be abnormal.

Check the etcd status. If etcd is abnormal, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001149

Failed to query the cluster details because the CCE service or API is abnormal.

Failed to query the cluster details because the CCE service or API is abnormal.

Check the CCE service and API status. Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service.

400

BCS.4001161

Failed to add the organization because the etcd connection or CCE API may be abnormal.

Failed to add the organization because the etcd connection or CCE API may be abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001171

Weak password.

Weak password.

Enter a strong password.

400

BCS.4001196

Operation failed because the current service or services in the consortium are being updated. Try again later.

Operation failed because the current service or services in the consortium are being updated. Try again later.

Try again later.

400

BCS.4001202

Deletion failed. The service does not exist or has already been deleted. Refresh the page.

Deletion failed. The service does not exist or has already been deleted. Refresh the page.

Refresh the Service Management page.

400

BCS.4001203

Operation failed. Failed to obtain the deployment task.

Operation failed. Failed to obtain the deployment task.

Try again.

400

BCS.4001212

Operation failed. The ECS specified by node_flavor in the request cannot be purchased.

Operation failed. The ECS specified by node_flavor in the request cannot be purchased.

Specify an ECS with other flavors in the node_flavor.

400

BCS.4001234

Operation failed because the BCS service is in the Hibernating or Frozen state.

Operation failed because the BCS service is in the Hibernating or Frozen state.

Click More > Wake in the Operation column of the row containing the specified service and try again after the service is normal.

400

BCS.4001242

Failed to remove the organization from a channel.

Failed to remove the organization from a channel.

Remove the organization again until the channel and service statuses are normal.

400

BCS.4001301

Failed to query the ROMA instance information because the ROMA instance may have been deleted or its status is abnormal.

Failed to query the ROMA instance information because the ROMA instance may have been deleted or its status is abnormal.

Log in to the ROMA console and check whether the instance status is normal. Wait until the instance status is normal or use an unused, normal instance.

400

BCS.4001302

Failed to query the cluster information because the cluster has been deleted or is abnormal.

Failed to query the cluster information because the cluster has been deleted or is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. If the cluster corresponding to the BCS service does not exist, the cluster has been deleted. In this case, use an existing, normal cluster to buy a BCS service again. If the cluster exists, check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored or use a normal cluster to create another BCS service.

400

BCS.4001304

Failed to query the ROMA instance list because the ROMA MQS API is abnormal.

Failed to query the ROMA instance list because the ROMA MQS API is abnormal.

Log in to the ROMA console and check whether ROMA MQS and the ROMA instance is normal. If they are abnormal, try again after they are normal or rectify the fault as instructed by the ROMA troubleshooting document.

400

BCS.4001305

Failed to obtain the topic information of the ROMA instance because the ROMA instance is abnormal or has been deleted.

Failed to obtain the topic information of the ROMA instance because the ROMA instance is abnormal or has been deleted.

Log in to the ROMA console to check whether the ROMA instance used by the BCS service is normal. If it is abnormal, try again after it is normal. If the instance is deleted, purchase a new ROMA instance and create a BCS service again.

400

BCS.4001306

Operation failed because the ROMA instance is currently in use.

Operation failed because the ROMA instance is currently in use.

Select an unused, normal ROMA instance.

400

BCS.4001307

Operation failed because you do not have the permissions to view DMS data. Check your permissions in IAM.

Operation failed because you do not have the permissions to view DMS data. Check your permissions in IAM.

Check the account permissions in IAM. For details about the required permissions, see the user guide. Add the DMS permissions and try again.

400

BCS.4001356

Operation failed. No network storage space has been configured for the cluster.

Operation failed. No network storage space has been configured for the cluster.

Buy a BCS service again. When configuring Network Storage, choose Create SFS File System.

400

BCS.4001401

Failed to update the IPMapping information of the current tenant because etcd, the CCE API, or the cluster is abnormal.

Failed to update the IPMapping information of the current tenant because etcd, the CCE API, or the cluster is abnormal.

Log in to the CCE console and choose Resource Management > Clusters. Locate the cluster used by the BCS service, and check whether the cluster is normal. If the cluster is abnormal, rectify the fault by referring to the CCE troubleshooting document or use an available cluster to buy another BCS service. If the cluster status is normal, choose Configuration Center > ConfigMaps. Filter the configuration items by cluster, find the IPMapping of the cluster corresponding to the BCS service, and check whether the configuration is correct and whether the format is complete. If no fault if found in the preceding steps, rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001402

Failed to update the access address because the EIP information in the SDK configuration fails to be updated due to an etcd exception.

Failed to update the access address because the EIP information in the SDK configuration fails to be updated due to an etcd exception.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001404

Failed to update the EIP information of other consortium members because etcd may be abnormal.

Failed to update the EIP information of other consortium members because etcd may be abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001407

Try again or check whether ETCD is normal.

Obtain EIP data failed.

Try again or check whether ETCD is normal.

400

BCS.4001408

Do not use the domain name repeatedly. Apply for a new domain name or add a new domain name resolution set.

The domain name has been used in other BCS instances.

Do not use the domain name repeatedly. Apply for a new domain name or add a new domain name resolution set.

400

BCS.4001520

Failed to obtain the topology information of the invitee because etcd may be abnormal.

Failed to obtain the topology information of the invitee because etcd may be abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001521

Failed to obtain the topology information of the inviting party because etcd may be abnormal.

Failed to obtain the topology information of the inviting party because etcd may be abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001708

Operation failed. The IP address of the IEF node cluster is incorrect.

Operation failed. The IP address of the IEF node cluster is incorrect.

  1. Log in to the CCE console.

  2. Choose Resource Management > Clusters, and click the cluster of a target BCS service.

  3. Click Nodes, view the EIP bound to the cluster node. 4. Set the public IP addresses of these IEF nodes to the EIPs bound to the nodes.

400

BCS.4001717

Operation failed. The number of IEF nodes is less than that required by the consensus policy.

Operation failed. The number of IEF nodes is less than that required by the consensus policy.

Buy IEF nodes required by the consensus policy or buy more such nodes.

400

BCS.4001750

Failed to query the quota from ManageOne because the ManageOne API may be abnormal.

Failed to query the quota from ManageOne because the ManageOne API may be abnormal.

Check the ManageOne API status. Log in to ManageOne and go to the quota management page. If the displayed page shows the service quotas in the specified region, the ManageOne API is normal. If the ManageOne API is abnormal, try again after it restores.

400

BCS.4001751

The BCS service quota is not found because the quota is not registered or the quota configuration is incorrect.

The BCS service quota is not found because the quota is not registered or the quota configuration is incorrect.

Log in to ManageOne and go to the quota management page. If the displayed page shows the BCS quota in the specified region, the BCS quota has been registered correctly. Otherwise, the BCS quota has not been registered or the quota configuration is incorrect. In this case, contact the administrator to register the BCS quota again.

400

BCS.4001752

Failed to modify the quota on ManageOne because the ManageOne API may be abnormal.

Failed to modify the quota on ManageOne because the ManageOne API may be abnormal.

Check the ManageOne API status. Log in to ManageOne and go to the quota management page. If the displayed page shows the service quotas in the specified region, the ManageOne API is normal. If the ManageOne API is abnormal, try again after it restores.

400

BCS.4001753

Failed to query the product from ManageOne because the product does not exist, the product information is abnormal, or the ManageOne API is abnormal.

Failed to query the product from ManageOne because the product does not exist, the product information is abnormal, or the ManageOne API is abnormal.

Check the ManageOne API status and the product information. Log in to ManageOne and go to the quota management page. If the displayed page shows the service quotas in the specified region, the ManageOne API is normal. Then, check the BCS information. If the BCS information is missing, contact the administrator to register BCS. If the page is not displayed properly, the ManageOne API is abnormal. In this case, try again after it restores.

400

BCS.4001754

This operation cannot be performed on the order because the order parameters do not exist.

This operation cannot be performed on the order because the order parameters do not exist.

Buy a BCS service again.

400

BCS.4001755

Failed to save the order parameters because etcd may be abnormal.

Failed to save the order parameters because etcd may be abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4001756

The order processing cannot proceed because the order parameters have changed.

The order processing cannot proceed because the order parameters have changed.

Buy a BCS service again.

400

BCS.4001757

Operation verification failed. Only create and delete operations are supported.

Operation verification failed. Only create and delete operations are supported.

Check whether the operation is creation or deletion.

400

BCS.4001999

Failed to accept the invitation. Refresh the page and check the invitation status later.

Failed to accept the invitation. Refresh the page and check the invitation status later.

Refresh the page and check the invitation status later.

400

BCS.4003007

No authorization from CCE.

No authorization from CCE.

Obtain authorization on the CCE console.

400

BCS.4004001

You cannot select EVS storage because the CCE cluster version is earlier than 1.15.

You cannot select EVS storage because the CCE cluster version is earlier than 1.15.

Log in to the CCE console, choose Resource Management > Clusters, click the cluster where the BCS service is deployed, and check whether the cluster version is later than 1.15. If the cluster version is earlier than 1.15, create another cluster whose version is later than 1.15. If CCE does not support clusters whose version is later than 1.15, contact CCE support personnel.

400

BCS.4004002

EVS storage is not supported.

EVS storage is not supported.

Log in to CloudAutoDeploy-CDK, select a region, and choose Cloud Service Management > Upgrade. Select the cluster where the BCS service is deployed and select the baas-service pod for upgrade. Change the value of evs_service_enable to true, and perform the upgrade. Wait until the upgrade is complete.

400

BCS.4004003

You cannot select EVS storage because the EVS disk and the CCE node are located in different AZs.

You cannot select EVS storage because the EVS disk and the CCE node are located in different AZs.

Log in to the CCE console, choose Resource Management > Clusters, and click the cluster where the BCS service is deployed. Then, choose Nodes in the navigation pane, and view the AZs configured for the nodes. Choose Storage in the navigation pane, click the EVS tab, and click Buy EVS Disk. Check whether the AZ of the EVS disk is the same as that of the cluster nodes. If they are different, purchase another CCE cluster in the same AZ as the EVS disk.

400

BCS.4004004

You cannot select EVS storage when the Fabric version of the BCS service is earlier than 3.0.

You cannot select EVS storage when the Fabric version of the BCS service is earlier than 3.0.

Set the Fabric version of the BCS service to 3.0 or later.

400

BCS.4004005

You cannot change the billing mode of the BCS service to yearly/monthly because the BCS service uses EVS storage.

You cannot change the billing mode of the BCS service to yearly/monthly because the BCS service uses EVS storage.

BCS services billed in the yearly/monthly mode do not support EVS storage. You can use SFS file systems instead.

400

BCS.4004006

Failed to query the EVS type.

Failed to query the EVS type.

Check whether the network is normal. Manually run the curl command with the EVS domain name. If the domain name cannot be accessed, contact the DNS service personnel. Log in to the EVS console, click Buy Disk, and check whether an error message is displayed. If an error message is displayed, contact the EVS O&M personnel. Check whether the back-end service of BCS is normal. If the back-end service is abnormal, view the corresponding logs.

400

BCS.400402

Query failed.

Query failed.

Check the entity type in the input parameter.

400

BCS.4004022

Failed to query the monitoring data because the AOM API may be abnormal. Check whether the AOM service is normal and whether the AOM monitoring API can be accessed.

Failed to query the monitoring data because the AOM API may be abnormal. Check whether the AOM service is normal and whether the AOM monitoring API can be accessed.

Check whether the AOM service is normal and whether the AOM monitoring API can be accessed.

400

BCS.4004025

Invalid request information.

Invalid request information.

Check the request information and ensure that it is correct.

400

BCS.4004029

Query failed.

Query failed.

Check the input parameters and try again.

400

BCS.4006005

Failed to query the BCS service because the etcd connection may be abnormal.

Failed to query the BCS service because the etcd connection may be abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006007

Failed to submit the request because no EIP is bound to the CCE cluster or the EIP fails to be queried.

Failed to submit the request because no EIP is bound to the CCE cluster or the EIP fails to be queried.

Log in to the CCE console. Choose Resource Management > Nodes. Locate the node corresponding to the BCS service and check whether the EIP is bound. For a private blockchain, at least one node must be bound with an EIP. For a consortium blockchain, all nodes must be bound with EIPs. Perform the following steps to bind an EIP: On the node details page, click the node name. On the displayed ECS console, click the ECS name. On the ECS details page, click the EIPs tab. Click Bind EIP. The Bind EIP dialog box is displayed.

400

BCS.4006009

Failed to download the SDK configuration because the etcd connection or the CCE cluster status is abnormal.

Failed to download the SDK configuration because the etcd connection or the CCE cluster status is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service, and check whether the cluster status is normal and whether the cluster has available nodes. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006012

Failed to create the channel because the etcd connection or the CCE cluster status is abnormal.

Failed to create the channel because the etcd connection or the CCE cluster status is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service, and check whether the cluster status is normal and whether the cluster has available nodes. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006013

Failed to update the BCS service instance information because the etcd connection is abnormal.

Failed to update the BCS service instance information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006017

Failed to upgrade the BCS service because the etcd connection or the CCE cluster status is abnormal.

Failed to upgrade the BCS service because the etcd connection or the CCE cluster status is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service, and check whether the cluster status is normal and whether the cluster has available nodes. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006018

Failed to query data because the etcd connection is abnormal.

Failed to query data because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006019

Failed to change the password because the etcd connection, the CCE configuration update API, or the cluster status is abnormal.

Failed to change the password because the etcd connection, the CCE configuration update API, or the cluster status is abnormal.

Log in to the CCE console and check whether CCE is normal. If CCE is normal, choose Resource Management > Clusters. Locate the cluster corresponding to the BCS service and check whether the cluster status is normal. If the cluster is abnormal, try again after the cluster is restored. Alternatively, use a normal cluster to create another BCS service. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006025

Invitation failed because the tenant has already been invited or the etcd connection is abnormal.

Invitation failed because the tenant has already been invited or the etcd connection is abnormal.

Go to the Member Management page on the BCS console to check whether the tenant invitation information exists. If the invitation exists, the tenant has been invited and cannot be invited again. Wait for the invited tenant to reply. If the invitation does not exist, the etcd connection may be abnormal. In this case, proceed to the next step. Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006026

Some invitations failed because the etcd connection is abnormal.

Some invitations failed because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006027

Failed to list the members because the etcd connection is abnormal.

Failed to list the members because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006032

Failed to download the SDK configuration. The OrderEIP is empty because the etcd connection may be abnormal.

Failed to download the SDK configuration. The OrderEIP is empty because the etcd connection may be abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006034

Failed to obtain the notification information because the etcd connection is abnormal.

Failed to obtain the notification information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006036

Failed to generate the organization certificate because the etcd connection is abnormal.

Failed to generate the organization certificate because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006037

Failed to send the event information because the AOM API or the network connection is abnormal.

Failed to send the event information because the AOM API or the network connection is abnormal.

Log in to the AOM console to check whether AOM is normal and whether related information is reported. If AOM is abnormal, events can be reported only after AOM is restored. If AOM APIs are normal, the network connection may not be stable. Try again later.

400

BCS.4006038

Failed to update the notification information because the etcd connection is abnormal.

Failed to update the notification information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006039

Failed to submit the request because the cluster is in use.

Failed to submit the request because the cluster is in use.

Select an unused cluster and try again.

400

BCS.4006040

Failed to save the member information because the etcd connection is abnormal.

Failed to save the member information because the etcd connection is abnormal.

Rectify the etcd fault by referring to the BCS Troubleshooting document and try again after etcd is normal.

400

BCS.4006041

Failed to delete the notification because finished notifications cannot be deleted.

Failed to delete the notification because finished notifications cannot be deleted.

Do not delete finished notifications.

400

BCS.4009100

System error. Check the system or network status.

System error. Check the system or network status.

Switch from the BCS console to other service consoles, such as the CCE console. If multiple services are abnormal, the fault is caused by a common component fault in the environment. After the fault is rectified, try again. If only BCS is abnormal, the BCS backend node may be faulty. In this case, rectify the fault by following the instructions provided in "BCS Node Fault" in the BCS Emergency Plan.

400

BCS.4009101

The request URL does not exist. Check whether the URL has been registered.

The request URL does not exist. Check whether the URL has been registered.

Log in to the API registration page on DMK. Find BCS APIs, and check whether the API for performing the specified operation exists in the list. If it does not exist, register the API as instructed by the API Gateway document contained in the BCS installation package.

400

BCS.4009102

Internal system error. Check the system status or network status.

Internal system error. Check the system status or network status.

Switch from the BCS console to other service consoles, such as the CCE console. If multiple services are abnormal, the fault is caused by a common component fault in the environment. After the fault is rectified, try again. If only BCS is abnormal, the BCS backend node may be faulty. In this case, rectify the fault by following the instructions provided in "BCS Node Fault" in the BCS Emergency Plan.

400

BCS.4009103

The maximum number (5) of invited members in the channel has been reached.

The maximum number (5) of invited members in the channel has been reached.

Do not exceed the maximum number of members that can be invited to each channel.

401

BCS.4010401

Permission verification failed.

Permission verification failed.

Configure the permissions by following the instructions provided in BCS User Guide > Service Deployment > Prerequisites.

403

BCS.4030403

Insufficient permissions.

Insufficient permissions.

Configure the permissions by following the instructions provided in BCS User Guide > Service Deployment > Prerequisites.