Error Code
If an error occurs during API calling, no results will be returned. You can locate the error cause based on error codes of each API. If an error occurs, an HTTP status code is returned. The returned message body contains a specific error code and error message.
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to Error Codes.
Status Code |
Error Codes |
Error Message |
Description |
Troubleshooting |
---|---|---|---|---|
422 |
DRS.M00002 |
The returned result is empty. |
The returned result is empty. |
Check the request parameters or task status. |
422 |
DRS.M00004 |
Service is abnormal. Check logs. |
Service is abnormal. Check logs. |
If the service is abnormal, contact technical support. |
400 |
DRS.M00007 |
Invalid request parameter. |
Invalid request parameter. |
Check the request parameters. |
403 |
DRS.M00100 |
Invalid token. |
Failed to pass IAM authentication. |
Check the user token information. |
404 |
DRS.M00101 |
The user role is empty. |
The user role is empty. |
Check the role information of the user. |
403 |
DRS.M00102 |
You do not have sufficient permissions. |
Insufficient permissions. |
Check the DRS permissions of the current user. |
401 |
DRS.M00103 |
You do not have operation permissions. Check account permissions on IAM. |
Operation denied. Check your account permissions on IAM. |
Check the DRS permissions of the current user. |
400 |
DRS.M00105 |
User restricted. |
User restricted. |
Check the DRS permissions of the current user. |
400 |
DRS.M00200 |
Parameter error. |
Invalid parameters. |
Check the request parameters. |
400 |
DRS.M00201 |
The parameter %s is empty. |
The parameter %s is empty. |
Check the request parameters. |
400 |
DRS.M00202 |
The value of parameter %s is invalid. |
The value of parameter %s is invalid. |
Check the request parameters. |
400 |
DRS.M00210 |
The value of Page is invalid, %s |
Invalid page value, %s. |
Check the request page parameters. |
400 |
DRS.M00211 |
The value of Page exceeds the upper limit. |
The number of pages exceeds the upper limit. |
Check the request page parameters. |
403 |
DRS.M00261 |
Invalid project ID. |
Invalid project ID. |
Check the value of project ID in the request. |
400 |
DRS.M00269 |
The tag key must be unique. |
The tag key cannot be duplicated. |
Check whether the tag key is unique. |
400 |
DRS.M00270 |
The tag key or value is too long. |
The tag key or value exceeds the maximum length allowed. |
Check the length of the tag key or value in the request. |
400 |
DRS.M00271 |
The number of tags exceeds the limit. |
The maximum number of tags has been reached. |
Check the number of tags in the request. |
400 |
DRS.M00273 |
Invalid parameter. The parameter contains %s. |
Invalid parameter. %s exists in the parameter. |
Check the request parameters. |
422 |
DRS.M00277 |
The task name already exists. |
The task name already exists. |
Change the task name. |
400 |
DRS.M00289 |
Missing query result: %s |
No query result is found. |
Check the request parameters. |
400 |
DRS.M00298 |
Job does not exist, please check job id. |
The job does not exist. Check the job ID. |
Check the request parameters. |
400 |
DRS.M00299 |
Only one jobId is allowed. |
Only one job ID can be transferred. |
Check the request parameters. |
400 |
DRS.M00300 |
Invalid request, %s |
Invalid request. %s. |
Check the request parameters. |
400 |
DRS.M00301 |
There are duplicate %s in request. |
The request contains duplicate task IDs. |
Check the request parameters. |
400 |
DRS.M00302 |
The transfer schema is invalid, please refer to supported transfer schema. |
Invalid migration scheme. |
Check the request parameters. |
400 |
DRS.M00303 |
The corresponding parameter is not obtained from the cache. |
Failed to obtain corresponding parameters from the cache. |
Check the request parameters. |
400 |
DRS.M00304 |
This API cannot be called in the current task status. |
API cannot be invoked in current state of the task. |
Check the current task status. |
400 |
DRS.M00305 |
Parameter error:%s |
Parameter error: %s. |
Check the request parameters. |
400 |
DRS.M00306 |
Start time cannot be the same as end time. |
The start time cannot be the same as the end time. |
Check the request parameters. |
400 |
DRS.M00307 |
Only subtasks can invoke this interface. |
Only subtasks can use this API. |
Change the task ID. |
400 |
DRS.M00308 |
Only parent tasks can invoke this interface. |
Only parent tasks can use this API. |
Change the task ID. |
400 |
DRS.M00401 |
%s is not support re-editing of synchronization tasks. |
%s does not support re-editing synchronization tasks. |
Change the task ID. |
400 |
DRS.M00402 |
The subtask already exists. |
The subtask already exists. |
Change the task ID. |
400 |
DRS.M00403 |
This task does not support flow control. |
This task does not support flow control. |
Change the task ID. |
422 |
DRS.M00414 |
The value for Logical Copy Slot Advance Interval must be between 1 and 999. |
The interval for advancing the logical replication slot must range from 1 to 999. |
Change the interval for advancing the logical replication slot. |
422 |
DRS.M01501 |
Service error. |
The server is abnormal. |
If the service is abnormal, contact technical support. |
202 |
DRS.M01504 |
Another operation is being performed on the migration task or the migration task is abnormal. |
Other operations are being performed on the migration task or the migration task is faulty. Try again later. |
Check the current task status. |
400 |
DRS.M05003 |
Task information not found. |
Task information cannot be queried. |
Check the task ID in the request. |
400 |
DRS.M05004 |
The task has been deleted or the resource has been released. |
The task has been deleted or resources have been released. |
Check the current task status. |
422 |
DRS.M05006 |
Invalid RDS DB instance. |
Invalid RDS DB instance. |
Check the RDS instance ID in the request. |
200 |
DRS.M05066 |
Failed to create instance! |
Failed to create an instance. |
Contact technical support. |
400 |
DRS.M06007 |
The DB instance cannot be left blank. |
The DB instance is null or "". |
Check the RDS instance ID in the request. |
422 |
DRS.M06011 |
Failed to obtain RDS information. |
Obtain RDS DB instance information failed. |
Check the RDS instance ID in the request. |
422 |
DRS.M06020 |
The destination DB instance has been set to read/write by the migration task %s and cannot be used. |
The destination DB instance cannot be used because it has been set to read/write by the migration task %s. |
Check the RDS instance ID in the request. |
422 |
DRS.M06021 |
The destination DB instance has been set to read/write by the synchronization task %s and cannot be used. |
The destination DB instance cannot be used because it has been set to read/write by the synchronization task %s. |
Check the RDS instance ID in the request. |
400 |
DRS.M07000 |
Data processing rule already exists. |
Data processing rule already exists. |
Modify the data processing rule in the request. |
200 |
DRS.KE0001 |
Failed to connect to the database network. |
Database connection failed. |
Check the network configuration between the database and the replication instance. |
200 |
DRS.KE0002 |
The username or password is incorrect. |
The username or password is incorrect. |
Check the username and password. |
200 |
DRS.KE0003 |
The port cannot be accessed. |
The port cannot be accessed. |
Check the database port. |
200 |
DRS.KE0004 |
Connection failed.Handling suggestion: Please check the security group/firewall/SSL configuration of the database. |
Connection failed. |
Check the security group, firewall, and SSL configuration of the database. |
200 |
DRS.KE0005 |
The database user must allow remote connections.Handling suggestion: Run CREATE USER 'Account'@'%' IDENTIFIED BY 'Password' to create a user that allows remote connections. After the migration, delete this user. |
The database user must allow remote connections. |
Run CREATE USER'Account'@'%' IDENTIFIED BY 'Password' to create a user that allows remote connections. After the migration is complete, delete the user. |
200 |
DRS.KE0006 |
The remote connection permission is not configured in pg_hba.conf for the replication instance and database user.Handling suggestion: Add \"host all ***(dbuser) 0.0.0.0/0 password\" to the pg_hba.conf configuration file to grant the remote connection permission to the user and restart the database. After the migration is complete, delete this record and restart the database again. |
The remote connection permission is not configured in pg_hba.conf for the replication instance and database user. |
Add \"host all ***(dbuser) 0.0.0.0/0 password\" to the pg_hba.conf configuration file to grant the remote connection permission to the user, and restart the database. After the migration is complete, delete this record and restart the database again. |
200 |
DRS.KE0007 |
The database user does not have the login permission.Handling suggestion: Run alter role *** (dbuser) login to grant the login permission. |
The database user does not have the login permission. |
Run alter role *** (dbuser) login to grant the login permission. |
200 |
DRS.KE0008 |
The specified source database does not exist. Handling suggestion: Create a database or enter an existing database name. |
The specified source database was not found. |
Create a database or enter an existing database name. |
200 |
DRS.KE0009 |
The SSL CA certificate does not exist.Handling suggestion: Contact technical support. |
The SSL CA certificate was not found. |
Contact technical support. |
200 |
DRS.KE0010 |
SSL is not enabled or the certificate is invalid. Handling suggestion: Enable SSL or upload a valid SSL CA certificate. |
SSL is disabled or the certificate is invalid. |
Enable SSL or upload a valid SSL CA certificate. |
200 |
DRS.KE0011 |
The source database does not have the Microsoft SQL Server replication component installed. |
The source database does not have the Microsoft SQL Server replication component installed. |
Install the Microsoft SQL Server replication component. |
200 |
DRS.KE0012 |
The user does not have the permission to access the database. |
The user does not have the permission to access the database. |
Grant the permission to access the database to the user. |
200 |
DRS.KE0013 |
Insufficient permissions. |
Insufficient permissions. |
Grant the permission to access the database to the user. |
200 |
DRS.KE0014 |
Internal error. |
Internal error. |
Contact technical support. |
200 |
DRS.KE0015 |
The network connection between the replication instance and database is faulty. |
The network connection between the replication instance and the database is faulty. |
Contact technical support. |
200 |
DRS.KE0016 |
Failed to connect to the database. In the postgresql.conf file, the listen_addresses parameter value or port number is incorrect.Handling suggestion: In postgres.conf, set listen_addresses to * or change the port number to the correct value. Then, restart the database for the modification to take effect. |
Failed to connect to the database. In the postgresql.conf file, the listen_addresses parameter value or port number is incorrect. |
In postgres.conf, set listen_addresses to * or change the port number to the correct value. Then, restart the database to apply the change. |
200 |
DRS.KE0017 |
The IP address cannot be pinged.Handling suggestion: See migration preparations in the DRS Best Practices. |
The IP address cannot be pinged. |
See migration preparations in the DRS Best Practices. |
200 |
DRS.KE0018 |
Failed to resolve the domain name. |
Failed to resolve the domain name. |
See migration preparations in the DRS Best Practices. |
200 |
DRS.KE0019 |
Failure cause: The subnets of any of the source, destination, or replication (synchronization or disaster recovery) instances in different VPCs overlap. |
The subnet CIDR blocks of any of the source, destination, or replication (synchronization or disaster recovery) instances in different VPCs overlap. |
See migration preparations in the DRS Best Practices. |
200 |
DRS.KE0020 |
Incorrect replica set name. |
The replica set name is incorrect. |
Contact technical support. |
200 |
DRS.KE0021 |
The source database cannot connect to the port of the replication instance.Handling suggestion: Modify the firewall and security group configurations of the source and destination databases to enable the source database to connect to the port of the replication instance. See migration preparations in the DRS Best Practices. |
The source database cannot connect to the port of the replication instance. |
Modify the firewall and security group configurations of the source and destination databases to enable the source database to connect to the port of the replication instance. See migration preparations in the DRS Best Practices. |
200 |
DRS.KE0022 |
The SSL certificate is incorrect.Handling suggestion: Upload a correct SSL certificate. |
The SSL certificate is incorrect. |
Upload a correct SSL certificate. |
200 |
DRS.KE0023 |
The DRS EIP is not in the whitelist of the source database.Handling suggestion: Add the DRS EIP to the whitelist of the source database. |
The EIP of the DRS instance is not added to the whitelist of the source database. |
Add the EIP of the DRS instance to the whitelist of the source database. |
200 |
DRS.KE0030 |
The service name is incorrect.Handling suggestion: Check whether the service name is correct before the connection test. |
The database service name is incorrect. |
Check whether the database service name specified in the connection test is correct. |
200 |
DRS.KE0031 |
Query failed.Handling suggestion: Check whether the migration account has sufficient permissions. |
Query failed. |
Check whether the migration account has sufficient permissions. |
200 |
DRS.KE0032 |
The Oracle certificate is incorrect.Handling suggestion: Upload a correct Oracle certificate. |
The Oracle certificate is incorrect. |
Upload a correct Oracle certificate. |
200 |
DRS.KE0033 |
The username, password, or authentication database of the source database is incorrect.Handling suggestion: Check that the input username, password, and authentication database for the connection test are correct. |
The username, password, or authentication database of the source database is incorrect. |
Check whether the username, password, and authentication database entered for the connection test are correct. |
200 |
DRS.KE0034 |
The username, password, or authentication database of the destination database is incorrect.Handling suggestion: Check that the input username, password, and authentication database for the connection test are correct. |
The username, password, or authentication database of the destination database is incorrect. |
Check whether the username, password, and authentication database entered for the connection test are correct. |
200 |
DRS.KE0035 |
The database middleware is not a MySQL sharding middleware. |
The database middleware is not a MySQL sharding middleware. |
Contact technical support. |
200 |
DRS.KE0036 |
SSL must be enabled when the database password plugin caching_sha2_password is verified.Handling suggestion: Enable SSL or create a user. |
SSL must be enabled when the database password plugin cache_sha2_password is verified. |
Enable SSL or create a user. |
200 |
DRS.KE0037 |
The username or password is incorrect.Handling suggestion: Check that the input username and password for the connection test are correct. |
The username or password is incorrect. |
Check whether the username and password for the connection test are correct. |
200 |
DRS.KE0038 |
The account is locked.Handling suggestion: Contact technical support to unlock the account. |
The account is locked. |
Contact technical support to unlock the account. |
200 |
DRS.KE0039 |
The database cannot be connected because the client IP address is not in the whitelist.Handling suggestion: Use an account with the ALTER SYSTEM permission and execute the following SQL statement: alter system add hba entry (hostssl [Username] [Subnet of the RDS instance]);. |
The database cannot be connected because the client IP address is not in the whitelist. |
Use an account with the ALTER SYSTEM permission to run the following SQL statement: alter system add hba entry (hostssl [username] [subnet CIDR block where RDS is located]). |
200 |
DRS.KE0040 |
The kafka brokers is not available. |
The Kafka node is unavailable. |
Contact technical support. |
200 |
DRS.KE0041 |
The kafka is not available. |
Kafka is unavailable. |
Contact technical support. |
200 |
DRS.KE0042 |
The kafka topic is not existed. |
The Kafka topic does not exist. |
Contact technical support. |
200 |
DRS.KE0043 |
The user does not have the permission to create connections.Grant the required permission to the user and try again. |
The user does not have the permission to create connections.. |
Grant the required permissions to the user and try again. |
200 |
DRS.KE0044 |
The parameters for test connection contains non-ascii character. Handling suggestion: Please check test connection parameters, use user info without NON-ASCII characters to test connection. |
The parameters for testing the connection contain non-ASCII characters. |
Check the connection test parameters and use the user information without non-ASCII characters to test the connection. |
200 |
DRS.KE0045 |
The user account is locked. |
The user account is locked. |
Contact technical support. |
200 |
DRS.KE0046 |
The IP address that the user requested to establish a connection is not monitored by the database. |
The IP address used by the user to request to set up a connection is not monitored by the database. |
Contact technical support. |
200 |
DRS.KE0047 |
The queue name is not exist.Handling suggestion: Check that the input queue name for the connection test are correct. |
The queue name does not exist. |
Check whether the name of the queue entered for the connection test is correct. |
200 |
DRS.KE0048 |
Failed to connect to the database. |
Failed to connect to the database. |
Contact technical support. |
200 |
DRS.KE0049 |
Database user privilege is not enough. |
The database user does not have sufficient permissions. |
Contact technical support. |
200 |
DRS.KE0050 |
The PDB database is not open. |
Failed to open the PDB database. |
Open the PDB database. |
200 |
DRS.KE0051 |
The PDB database does not exist. |
The PDB database does not exist. |
Contact technical support. |
200 |
DRS.KE0052 |
Versions earlier than Oracle 12c do not support PDB. |
Versions earlier than Oracle 12c do not support PDB. |
Contact technical support. |
200 |
DRS.KE0053 |
Entered Oracle user has insufficient permissions. |
The entered Oracle user does not have sufficient permissions. |
Contact technical support. |
200 |
DRS.KE0054 |
Agent Connection Failed.Handling suggestion: Please check whether the logical replication agent is enabled or IP address and port number of the logical replication agent is correct. |
Failed to connect to the agent. |
Check whether the logical replication agent is enabled or whether the IP address and port number of the logical replication agent are correct. |
200 |
DRS.KE0055 |
Password has expired.Handling suggestion: Please reset the password. |
The password has expired. |
Reset the password. |
200 |
DRS.KE0056 |
The current instance does not support connections on multiple IP addresses during synchronization. Possible cause: The current instance is connected to a node through multiple IP addresses, which can cause a task to fail. Handling suggestion: Select a stable node, enter the single IP address of the node, and try to connect to the instance again. |
Data synchronization does not allow the instance to be connected using multiple IP addresses. |
Select a stable node, enter the single IP address of the node, and try to connect to the instance again. |
200 |
DRS.KE0057 |
The Kafka user name or password is incorrect. |
The Kafka username or password is incorrect. |
Check the username and password. |
200 |
DRS.KE0058 |
The Kafka encryption certificate or certificate password is incorrect. |
The Kafka encryption certificate or certificate password is incorrect. |
Check the username, password, or certificate. |
200 |
DRS.KE0059 |
The connected DB engine does not match the DB engine supported by the task. |
The connected DB engine does not match the DB engine supported by the task. |
Contact technical support. |
200 |
DRS.KE0060 |
Test connection is succeeded.Handling suggestion: The Oracle database is a RAC cluster. You are advised to use the SCAN IP address as the connection. For details, see here. |
The connection test is successful. |
The Oracle database is a RAC cluster. You are advised to use the SCAN IP address for the connection. |
200 |
DRS.KE0061 |
Possible reasons are:1. The node status is abnormal.2. The primary node information is not specified.3. The whitelist of pg_hba.conf is not configured.4.The network is abnormal. |
Failed to test the connection. The possible causes are as follows: 1. The node is abnormal. 2. The primary node information is not specified. 3. The pg_hba.conf whitelist is not configured. 4. The network is abnormal. |
Contact technical support. |
200 |
DRS.KE0062 |
The archived space is full, need to release. |
The archive space is full and resources need to be released. |
Clear the archive space. |
200 |
DRS.KE0063 |
The database query result is empty. The database does not have a table or does not have the SELECT permission on the table. |
The database query result is empty because the database has no tables or you do not have the SELECT permissions on the tables. |
Contact technical support. |
200 |
DRS.KE0064 |
The account password has expired.Handling suggestion: Changing the Expired Status of a User to OPEN.Refer to the modification statement: UPDATE SYS.USER$ SET ASTATUS = 0 WHERE NAME = 'user_name'. |
The account password has expired. |
Change the expiration status of the user to OPEN. For details, see the following statement: UPDATE SYS.USER$ SET ASTATUS = 0 WHERE NAME = 'user_name' |
200 |
DRS.KE0065 |
Database access denied. Handling suggestion: 1.Check whether the database name is correct before the connection test. 2.Check whether the DB2 database listening port number is correct. 3.Check whether the DB2 server is stopped. 4.Check whether the Firewall is stopped. |
Access to the database is denied. |
1. Check whether the database name is correct before the connection test. 2. Check whether the listening port number of the DB2 database is correct. 3. Check whether the DB2 server is stopped. 4. Check whether the firewall is disabled. |
200 |
DRS.KE0066 |
The number of DRS task shards must be the same as the actual number of GaussDB shard nodes. |
The number of DRS task shards must be the same as the actual number of GaussDB shard nodes. |
Contact technical support. |
200 |
DRS.KE0067 |
Cannot open user default database. |
Failed to open the default database of the account. |
Contact technical support. |
200 |
DRS.KE0068 |
The GTID format is incorrect. |
The GTID format is incorrect. |
Contact technical support. |
200 |
DRS.KE0069 |
The specified point is unavailable, the specified point must be between the task start point and the current point. |
The specified point is unavailable. The specified point must be between the task start point and the current point. |
Contact technical support. |
200 |
DRS.KE0070 |
Connection failed.Handling suggestion: Please check the security group/firewall/SSL configuration/pg_hba.conf whitelist of the database. |
Connection failed. |
Check the security group, firewall, SSL configuration, and pg_hba.conf whitelist of the database. |
Status Code |
Error Codes |
Error Message |
Description |
Troubleshooting |
---|---|---|---|---|
400 |
DRS.10000001 |
Failed |
Failed to process the request. |
Contact technical support. |
400 |
DRS.10020000 |
Parameter error:%s |
Parameter error: %s. |
Check the request parameters. |
400 |
DRS.10020001 |
Parameter %s is null |
The parameter %s is empty. |
Check the request parameters. |
400 |
DRS.10020002 |
The value of parameter %s is invalid. |
The parameter %s has an invalid value. |
Check the request parameters. |
400 |
DRS.10000010 |
The task does not exist. Check the task ID. |
The task does not exist. Check the task ID. |
Check the task ID. |
400 |
DRS.10000011 |
The database is abnormal. |
A database error occurred. |
Contact technical support. |
400 |
DRS.10000012 |
The start time cannot be the same as the end time. |
The start time cannot be the same as the end time. |
Change the time in the request. |
400 |
DRS.10010000 |
The start time cannot be the same as the end time. |
The start time cannot be the same as the end time. |
Change the time in the request. |
400 |
DRS.10010002 |
Async job param checking, Please wait param check complete and resubmit. |
The parameters of the task created asynchronously are being verified. Submit the task after the parameter verification is complete. |
Submit the task after the parameter verification is complete. |
400 |
DRS.10010004 |
Submit job failed. |
Failed to submit the task. |
Contact technical support. |
400 |
DRS.10010006 |
Create job failed. |
Failed to create the task. |
Contact technical support. |
400 |
DRS.10010007 |
Test connection failed. |
Failed to test the connection. |
Contact technical support. |
400 |
DRS.10010009 |
Set policy config failed,%s |
Failed to set the task policy, %ss. |
Check the task policy. |
400 |
DRS.10010010 |
Set progressing data failed,%s |
Failed to set data processing rules, %s. |
Check the data processing rules. |
400 |
DRS.10010011 |
Set user migration data failed,%s |
Failed to set user migration, %s. |
Check the user migration settings. |
400 |
DRS.10010012 |
Precheck failed,%s |
Pre-check failed, %s. |
Contact technical support. |
400 |
DRS.10010013 |
Database param modify success, please restart the database. |
Parameters of the DB instance are modified. Restart the database. |
Restart the database. |
400 |
DRS.10010014 |
Start job failed,%s |
Failed to start the task, %s. |
Contact technical support. |
400 |
DRS.10010016 |
%s is an EPS system tag and cannot be added manually. |
%s is an EPS system tag and cannot be manually added. |
Check the tag parameter. |
400 |
DRS.10010024 |
Param check failed,%s |
Parameter verification failed, %s. |
Check the parameter. |
400 |
DRS.10010025 |
The current API does not support this %s engine type now. |
The current APIs do not support this type of engine. |
Modify the request parameters. |
400 |
DRS.10010026 |
Reset job failed,%s. |
Failed to reset the task, %s. |
Contact technical support. |
400 |
DRS.10010027 |
Restart job failed,%s. |
Failed to retry the task, %s. |
Contact technical support. |
400 |
DRS.10010028 |
Pause job failed,%s. |
Failed to pause the task, %s. |
Contact technical support. |
400 |
DRS.10010029 |
Teminate job failed,%s. |
Failed to stop the task, %s. |
Contact technical support. |
400 |
DRS.10010030 |
Delete job failed,%s. |
Failed to delete the task, %s. |
Contact technical support. |
400 |
DRS.10010031 |
Test connection timeout. |
Connection testing timed out. |
Contact technical support. |
400 |
DRS.10010032 |
Failed to create the comparison task,%s. |
Failed to create the comparison task, %s. |
Contact technical support. |
400 |
DRS.10010033 |
Query progress failed,%s. |
Failed to query the task progress, %s. |
Contact technical support. |
400 |
DRS.10020072 |
Invalid projectId. |
Invalid project ID. |
Check the project ID. |
400 |
DRS.10020077 |
Duplicate task name. |
Duplicate task name. |
Check the task name. |
400 |
DRS.10030000 |
Excel content is empty. |
The Excel file to be uploaded is empty. |
Check the Excel file. |
400 |
DRS.10030001 |
Excel file size is too large, exceeds the threshold %s. |
The size of the Excel file to be uploaded exceeds the threshold %s. |
Check the size of the Excel file. |
400 |
DRS.10030002 |
Excel has more than one sheet. |
The Excel file to be uploaded contains more than one sheet. |
Check the number of files in the Excel. |
400 |
DRS.10030003 |
The object name is invalid. |
The object name is invalid. |
Check the object name. |
400 |
DRS.10030004 |
Support the file name extension can be ZIP, JSON, TXT, or Excel 2007 or later (with the file name extension .xlsx/.xls). |
Files in the format of ZIP, JSON, TXT, and Excel 2007 or later (with the file name extension .xlsx or .xls) can be imported. |
Check the format of the Excel file. |
400 |
DRS.10030005 |
Export excel fail. |
Failed to export the Excel file. |
Contact technical support. |
400 |
DRS.10030006 |
The file name format is %s. |
The file name can contain only %s. |
Check the file name. |
400 |
DRS.10030007 |
The supported file format is .xls or .xlsx. Please check. |
The file format must be .xls or .xlsx. |
Check the file format. |
400 |
DRS.10030008 |
Failed to download the file. |
Failed to download the file. |
Contact technical support. |
400 |
DRS.10030009 |
Failed to export data, because %s. |
Failed to export data due to %s. |
Contact technical support. |
400 |
DRS.10030010 |
The information of imported database is empty. Please check. |
The database information is empty. |
Check the imported file. |
400 |
DRS.10030011 |
The number of selection database exceeds the limit of 5000. |
More than 5000 databases are selected. |
Check the imported file. |
400 |
DRS.10030012 |
Failed to import the Excel file. |
Failed to import the Excel file. |
Contact technical support. |
400 |
DRS.10020111 |
The length exceeds %s. |
The length exceeds %s. |
Check the parameter length. |
400 |
DRS.10060015 |
Task is waiting for running. |
The task is waiting for running. |
Check the parameter length. |
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