Error Code
Description
This section explains the meanings of error code returned by CTS APIs.
Example of Returned Error Information
The obs_details field is only contained in the error message returned by the OBS bucket.
Error Code Description
| Response Code | Error Code | Description | Error Message | Details |
|---|---|---|---|---|
| 400 | cts.0001 | The API version number is empty. | Empty API version. Check whether you need to specify an API version. | The API version in the URL is empty. Check whether the API version information is specified. |
| 400 | cts.0002 | The API version number is incorrect. | Invalid API version. Check whether the API version is correct. | The API version information in the URL is invalid. Check whether the API version information is correct. |
| 400 | cts.0003 | The tenant ID does not exist. | Empty project ID. Check whether you need to specify a project ID. | The project ID in the URL is empty. Check whether the project ID is specified. |
| 400 | cts.0004 | The tenant ID is incorrect. | Invalid project ID. Check whether the project ID is correct. | The project ID in the URL is invalid. Check whether the project ID is correct. |
| 400 | cts.0005 | The query parameters are incorrect. | Invalid query criteria. Check whether query criteria parameters are correct. | Invalid query criteria. Check whether query criteria parameters are correct. **** does not exist. |
| 400 | cts.0006 | The request URL does not exist. | The URL does not exist. Check whether the URL meets requirements. | The URL does not exist. Check whether the URL is correct. |
| 400 | cts.0007 | Request parameters are incorrect. | Invalid message body. Different errors are returned according to different parameters. | Invalid message body. Check whether the message body format and content are correct. Invalid message body. The message body is not needed or not JSON. |
| 500 | cts.0008 | Data reading error. | Data read exception. Contact O&M personnel. | Data reading is abnormal. Contact O&M personnel. |
| 500 | cts.0009 | Data writing error. | Data write exception. Contact O&M personnel. | Data writing is abnormal. Contact O&M personnel. |
| 403 | cts.0010 | Repeated creation. | Tracker is existed already. | The tracker already exists. Modify the tracker name and create it again. |
| 403 | cts.0011 | The user does not have the permission to perform the operation. | The user fails the authentication or does not have permission to this operation. | The authentication failed or you have no rights to perform the operation. |
| 404 | cts.0012 | The tracker does not exist. | The tracker does not exist. Check whether the tracker name is correct or CTS has been enabled. | The tracker does not exist. Check whether the tracker name is correct. |
| 404 | cts.0013 | The trace does not exist. | The event does not exist. Check whether the trace ID is correct. | The trace does not exist. Check whether the trace ID is correct. |
| 400 | cts.0014 | The token is not found. | No valid token found. | The token is not found. Contact O&M personnel. |
| 500 | cts.0015 | Internal service error. | Internal server error. Contact the O&M personnel. | An internal service error occurs. Contact O&M personnel. |
| 500 | cts.0016 | Failed to write data into the cache. | Failed to write data into the cache. Contact O&M personnel. | Cache writing failed. Contact O&M personnel. |
| 401 | cts.0017 | Token authentication failed. | The token does not exist or is invalid. Check whether the token information is correct. | The token does not exist or is invalid. Check whether the token information is correct. |
| 202 | cts.0018 | O&M query is not supported. | The current environment does not support the calling of O&M interfaces. Check whether the URL is correct. | The system does not support invocation of O&M APIs. Check whether the URL information is correct. |
| 400 | cts.0019 | Failed to obtain the AK/SK. | Failed to obtain the user AK and SK. | Failed to obtain the AK/SK of the current user. Contact O&M personnel. |
| 400 | cts.0020 | Invalid AK/SK. | The user AK and SK are invalid. | The AK/SK of the current user is invalid. |
| 400 | cts.0021 | OBS authentication failed. | Failed to authenticate the OBS bucket. Contact O&M personnel. | The OBS bucket does not exist. Check whether the OBS bucket has been deleted. |
| 400 | cts.0022 | Enabled. | CTS cannot be repeatedly enabled. Check whether CTS has been enabled. | The OBS bucket authentication failed. Contact O&M personnel. |
| 404 | cts.0023 | The OBS bucket has been deleted. | The OBS bucket of the current user does not exist. Check whether the OBS bucket has been deleted. | The requested OBS bucket does not exist. Check whether the OBS bucket has been deleted. |
| 403 | cts.0024 | OBS authentication failed. | CTS is not authorized by the current user's OBS bucket. Check whether CTS is successfully authorized. | CTS failed to obtain the permission to access the OBS bucket. Check whether CTS has been authorized. |
| 400 | cts.0025 | Connecting to the database failed. | The api service disconnect with db. | The API service failed to connect to the database. |
| 400 | cts.0026 | Connecting to the cache failed. | The api service disconnect with cache. | The API service failed to connect to the Cache node. |
| 400 | cts.0027 | Failed to obtain the bucket list. | Failed to obtain the OBS bucket list. Contact O&M personnel. | Failed to obtain the list of OBS buckets. Contact O&M personnel. |
| 400 | cts.0028 | Failed to obtain the bucket location. | Failed to obtain the OBS bucket location. Contact O&M personnel. | Failed to obtain the region of the OBS bucket. Contact O&M personnel. |
| 400 | cts.0029 | Failed to create a bucket policy. | Failed to create the OBS bucket policy. Contact O&M personnel. | Failed to create an OBS bucket policy. Contact O&M personnel. |
| 400 | cts.0030 | Failed to delete a bucket policy. | Failed to delete the OBS bucket policy. Contact O&M personnel. | Failed to delete an OBS bucket policy. Contact O&M personnel. |
| 400 | cts.0032 | Failed to authenticate the account information. | Failed to check the OBS bucket existence. Contact O&M personnel. | The OBS account information is not updated, and you can try 15 minutes later. |
| 400 | cts.0033 | The OBS bucket does not belong to the current user. | Account information is not refresh in OBS. Please retry after 15 minutes. | The OBS bucket does not belong to the current user. Check whether the OBS bucket is correct. |
| 400 | cts.0034 | Failed to obtain the central region from IAM. | The OBS bucket does not belong to the current user. Check whether the OBS bucket is correct. | Failed to obtain the central area information from IAM. |
| 400 | cts.0036 | Failed to create a bucket. | Create bucket failed. | Failed to create a bucket. |
| 400 | cts.0037 | Failed to check the bucket. | Check bucket failed.The bucket is already exist. | Failed to check the bucket, and a bucket exists. |
| 400 | cts.0038 | Failed to obtain the project ID. | Failed to obtain the project ID from IAM when the system is trying to obtain keys from KMS. | Failed to obtain the project ID. Contact O&M personnel. |
| 400 | cts.0039 | The key does not exist. | The KMS key id of the current user does not exist. Check whether the KMS key id has been deleted. | The key does not exist. Contact O&M personnel. |
| 400 | cts.0040 | Failed to obtain the key. | Failed to obtain key list from KMS. | Failed to obtain the key. Contact O&M personnel. |
| 400 | cts.0041 | Failed to create a log topic or group. | Create log group or log topic failed, create tracker failed, please try again. | Failed to create a log topic or group. Contact O&M personnel. |
| 400 | cts.0043 | Failed to query the bucket. | Check bucket failed. Contact O&M personnel. | Failed to query the bucket. Contact O&M personnel. |
| 400 | cts.0044 | Failed to set the bucket lifecycle. | Set bucket life cycle failed. Contact O&M personnel. | Failed to set the bucket lifecycle. Contact O&M personnel. |
| 400 | cts.0045 | Failed to obtain the bucket lifecycle. | Get bucket life cycle failed. Contact O&M personnel. | Failed to get the bucket lifecycle. Contact O&M personnel. |
| 400 | cts.0046 | The number of created trackers reaches the upper limit. | The maximum number of trackers is: %s. | Failed to create the tracker. Contact O&M personnel. |
| 400 | cts.0048 | Failed to delete the data tracker. | Failed to delete the tracker, Please try again. | Failed to delete the tracker. Contact O&M personnel. |
| 400 | cts.0049 | A bucket cannot be used to create multiple trackers that record operations of the same type. | You cannot create different trackers to record the same type of operations on the same OBS bucket. | Failed to create the tracker. Contact O&M personnel. |
| 400 | cts.0050 | The tracked bucket cannot be modified. | The tracked OBS bucket can not be modify. | You are not allowed to modify the tracked OBS bucket. |
| 400 | cts.0051 | A bucket cannot be tracked by multiple trackers. | Failed to configure the tracker because the new settings could not be applied to the log group or log topic. Try again later. | An OBS bucket can be tracked by only one tracker. |
| 400 | cts.0052 | Failed to delete the log topic. | The topic in LTS deleted failed, tracker deleted failed. Please try again or delete the topic manually. | Failed to delete the log topic. Contact O&M personnel. |
| 400 | cts.0054 | The key operation notification already exists. | Notification name is existed already. | The key operation notification already exists and cannot be created repeatedly. |
| 404 | cts.0055 | The key operation notification does not exist. | The notification does not exist. | The key operation notification does not exist. Contact O&M personnel. |
| 400 | cts.0056 | The number of key operation notifications reaches the upper limit. | The quantity has exceeded the maximum quantity limit. | Failed to create the key operation notification. Contact O&M personnel. |
| 400 | cts.0057 | Failed to start or stop the key operation notification. | State setting failed, check if topicId exists. | Failed to start or stop the key operation notification. Contact O&M personnel. |
| 400 | cts.0058 | Failed to obtain group users from IAM. | Get group users failed from IAM. | Failed to obtain group users from IAM. Contact O&M personnel. |
| 400 | cts.0059 | An error occurred when querying the page_type parameter in the CDR. | Get meter data failed, the page_type parameter must be 2. | The page_type parameter must be set to 2. |
| 400 | cts.0060 | An error occurred when querying the limit parameter in the CDR. | Get meter data failed, the limit parameter should be greater than 0 or equal to 1000. | The limit parameter must be set to 0-1000. |
| 401 | cts.0061 | The project ID in the request does not match that in the token. | CSB update CTS status error, projectId in token is not equal projectId in body. | The project ID in the token is different from that in the request. Contact O&M personnel. |
| 404 | cts.0062 | The tracked bucket has been deleted. | The OBS bucket of the current user does not exist. Check whether the tracked bucket has been deleted. | Check whether the tracked bucket has been deleted. |
| 404 | cts.0063 | The current version number cannot be queried. | CTS does not support API interface version query. | The current version number cannot be queried. |
| 400 | cts.0065 | Failed to get time zone and language from CBC. | Failed to get time zone and language from CBC. | Failed to get time zone and language from CBC. Contact O&M personnel. |
| 500 | cts.0066 | Failed to obtain the AK/SK from IAM. | Failed to get AK/SK from IAM. | Failed to obtain the AK/SK from IAM. Contact O&M personnel. |
Last Article: Appendix
Next Article: Obtaining the Account ID and Project ID
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.