Error Codes

Status Code	Error Codes	Error Message	Description	Solution
400	CTS.0001	The IAM or OBS service is abnormal.	The IAM or OBS service is abnormal.	Contact technical support.
400	CTS.0003	The message body is empty or invalid.	The message body is empty or invalid.	Check the content and format of the message body.
400	CTS.0200	The number of trackers has reached the upper limit.	The number of trackers has reached the upper limit.	Delete or modify trackers no longer needed.
400	CTS.0201	A management tracker has been created.	A management tracker has been created.	Check whether a management tracker is already available.
400	CTS.0202	The value of the tracker_type parameter is incorrect.	The value of the tracker_type parameter is incorrect.	Change its value to system or data.
400	CTS.0203	The value of tracker_name parameter is in an incorrect format.	The value of tracker_name parameter is in an incorrect format.	Modify its value. Ensure that the tracker name is a string of 1 to 32 characters and does not start with an underscore (_) or hyphen (-)
400	CTS.0204	The tracker_name parameter of a management tracker can only be set to system.	The tracker_name parameter of a management tracker can only be set to system.	Change the value of tracker_name to system.
400	CTS.0205	The status parameter can only be set to enabled or disabled.	The status parameter can only be set to enabled or disabled.	Change its value to enabled or disabled.
400	CTS.0206	The data_bucket parameter cannot be included in the message body for a management tracker.	The data_bucket parameter cannot be included in the message body for a management tracker.	Delete the data_bucket parameter.
400	CTS.0207	The tracker_name parameter in the message body cannot be set to system for a data tracker.	The tracker_name parameter in the message body cannot be set to system for a data tracker.	Change the value of tracker_name to a value other than system.
400	CTS.0209	A type of operations on an OBS bucket can be tracked by only one tracker.	A type of operations on an OBS bucket can be tracked by only one tracker.	Change the tracker configurations.
400	CTS.0210	The OBS bucket to track cannot be empty.	The OBS bucket to track cannot be empty.	Select another bucket or ensure that the bucket is not empty.
400	CTS.0211	The tracked OBS bucket does not exist.	The tracked OBS bucket does not exist.	Check whether the bucket name is correctly set.
400	CTS.0212	The tracked OBS bucket cannot be modified.	The tracked OBS bucket cannot be modified.	Withdraw the changes on the OBS bucket.
400	CTS.0213	The OBS bucket used for trace transfer cannot be a tracked OBS bucket.	The OBS bucket used for trace transfer cannot be a tracked OBS bucket.	Select another OBS bucket for trace transfer.
400	CTS.0215	The OBS bucket already exists.	The OBS bucket already exists.	Change the value of bucket_name.
400	CTS.0216	Failed to create a bucket.	Failed to create a bucket.	Contact technical support.
400	CTS.0217	Failed to set a lifecycle rule for the OBS bucket.	Failed to set a lifecycle rule for the OBS bucket.	Contact technical support.
400	CTS.0218	The value of file_prefix_name is in an incorrect format.	The value of file_prefix_name is in an incorrect format.	Modify its value. Ensure that the file prefix name is a string of 0 to 64 characters and contains only letters, digits, underscores (_), hyphens (-), or periods (.)
400	CTS.0219	The operation type cannot be empty.	The operation type cannot be empty.	Select at least one operation type to track.
400	CTS.0220	KMS is not supported.	KMS is not supported.	Contact technical support.
400	CTS.0221	The KMS ID is empty.	The KMS ID is empty.	Check whether the KMS ID is correct.
400	CTS.0222	KMS verification failed.	KMS verification failed.	Check whether the KMS ID is correct.
400	CTS.0225	Only WRITE and/or READ operations on the OBS bucket can be tracked.	Only WRITE and/or READ operations on the OBS bucket can be tracked.	Check whether the input parameters are correctly set.
400	CTS.0231	Invalid bucket name. A bucket name must be a string of 3 to 63 characters, including only lowercase letters, digits, hyphens (-), or periods (.). It must start with a digit or a lowercase letter.	Invalid bucket name. A bucket name must be a string of 3 to 63 characters, including only lowercase letters, digits, hyphens (-), or periods (.). It must start with a digit or a lowercase letter.	Check whether the bucket name is correct.
400	CTS.0300	Query failed.	Query failed.	Try again later or contact technical support.
403	CTS.0002	Authentication failed or you do not have the permissions required.	Authentication failed or you do not have the permissions required.	Check your permissions.
403	CTS.0208	The tracker already exists.	The tracker already exists.	Check whether the tracker exists.
404	CTS.0100	API version query is not supported in CTS.	API version query is not supported in CTS.	Contact technical support.
404	CTS.0214	The tracker does not exist.	The tracker does not exist.	Check whether the tracker has been deleted.
500	CTS.0004	Failed to write data.	Failed to write data.	Contact technical support.
500	CTS.0005	Failed to read data.	Failed to read data.	Contact technical support.
400	CTS.0001	IAM or OBS exception , please check.	IAM or OBS service exception	Please contact technical support
400	CTS.0003	Invalid message body. The message body is empty or invalid.	Body is empty or illegal	Please verify the body content and format
400	CTS.0200	tracker number is Maximum	The number of trackers is full	Delete or modify unwanted trackers
400	CTS.0201	CTS cannot be repeatedly enabled. Check whether CTS has been enabled.	Existing management tracker	Check whether CTS has been enabled
400	CTS.0202	Invalid message body. Tracker tracker_type must be either system or data.	Tracker_type field does not match the format	Please change the corresponding value to system or data
400	CTS.0203	Invalid message body. The tracker_name is a string of 1 to 32 characters and cannot start with underscores or hyphens.	Tracker_name field does not match the format	Please refer to the parameter description for modification.
400	CTS.0204	Invalid message body. The tracker_name value must be system.	The value of the tracker_name field of the management tracker should be system	Please refer to the parameter description for modification.
400	CTS.0205	Invalid message body. Tracker status is required and value must be either enabled or disabled.	The value of status field can only be enabled or disabled	Please change the corresponding value to enabled or disabled
400	CTS.0206	Invalid message body. The data_bucket is not need.	For management tracker, the body cannot have the data_bucket parameter.	Please remove the data_buket parameter
400	CTS.0207	Invalid message body. The tracker_name value cannot be system.	For data tracker, the value of the tracker_name field in the body cannot be system	Please change tracker_name to a value other than system
400	CTS.0209	You cannot create different trackers to record the same type of operations on the same OBS bucket.	Tracking the same type of operation for one bucket	Please change the tracking item
400	CTS.0210	Invalid message body. The OBS bucket for which data operations are to be recorded can not be empty.	The tracked bucket cannot be empty	Please change a bucket or make the bucket not empty
400	CTS.0211	Check bucket failed.The bucket is not exist.	The bucket being tracked does not exist	Please check if the bucket_name is filled in correctly.
400	CTS.0212	The tracked OBS bucket can not be modify.	The tracked obs bucket cannot be modified	Please withdraw the change of the bucket
400	CTS.0213	Invalid message body. The OBS bucket for which data operations are to be recorded and the OBS bucket configured for storing transferred traces cannot be the same.	The tracked bucket is the same as the bucket used for dumping	Please replace the bucket for dumping
400	CTS.0215	Check bucket failed.The bucket is already exist.	The bucket already exists	Please modify bucket_name
400	CTS.0216	Create bucket failed.	Failed to create bucket	Please contact technical support
400	CTS.0217	Set bucket life cycle failed. Contact O&M personnel.	Setting bucket lifecycle rules failed	Please contact technical support
400	CTS.0218	Invalid message body. The file_prefix_name is a string of 0 to 64 characters and can only contain uppercase letters, lowercase letters, digits, hyphens, underscores and periods.	The file_prefix_name field in the body does not match the format	Please refer to the parameter description for modification.
400	CTS.0219	The bucket Bucket operation cannot be empty	Operation type cannot be empty	Please select at least one tracking operation
400	CTS.0220	this region unsupport kms.	This region does not support KMS	Please contact technical support
400	CTS.0221	KMS_ID is null	The kms_id field in the body is empty	Please check if kms_id is correct
400	CTS.0222	Failed to obtain key list from KMS.	KMS verification failed	Please check if kms_id is correct
400	CTS.0300	get query service failed, please check query-Service	Query failed	Please try again later or contact technical support.
403	CTS.0002	The user fails the authentication or does not have permission to this operation.	Role error	Please verify that the role of token is correct
403	CTS.0208	Tracker is existed already.	The tracker already exists	Please check if the tracker already exists
404	CTS.0100	CTS does not support API interface version query.	The current environment does not support API interface version query.	Please contact technical support
404	CTS.0214	The tracker does not exist.	The tracker does not exist	Please check if the tracker has been deleted
500	CTS.0004	Data write exception. Contact O&M personnel.	Failed to write data	Please contact technical support
500	CTS.0005	Data read exception. Contact O&M personnel.	Failed to read data	Please contact technical support