|
400 |
SMS.0007 |
Agent error. |
Agent error. |
Contact technical support. |
|
400 |
SMS.0201 |
Network busy. Source server failed to connect to API Gateway. |
Network busy. Source server failed to connect to API Gateway. |
Check the network between the source server and the API gateway. |
|
400 |
SMS.0202 |
AK/SK authentication failed. Ensure that the AK and SK are correct. |
AK/SK authentication failed. Ensure that the AK and SK are correct. |
Check whether you enter the correct AK and SK of the target platform account and whether the account is frozen. |
|
400 |
SMS.0203 |
Connection from source server to API Gateway timed out. |
Connection from source server to API Gateway timed out. |
Check the network between the source server and the API gateway. |
|
400 |
SMS.0204 |
Insufficient permissions. Cause: {0[0]}. Obtain the required fine-grained permissions. |
Insufficient permissions. Cause: {0[0]}. Obtain the required fine-grained permissions. |
Obtain the required fine-grained permissions. |
|
400 |
SMS.0205 |
Incorrect system time or time zone on source server. |
Incorrect system time or time zone on source server. |
Change system time or time zone on source server. |
|
400 |
SMS.0206 |
Only x86 servers can be migrated. |
Only x86 servers can be migrated. |
Use another migration method. |
|
400 |
SMS.0207 |
KVM driver not available on source server. |
KVM driver not available on source server. |
Install the KVM driver. |
|
400 |
SMS.0208 |
Failed to send your service statement confirmation to SMS |
Failed to send your confirmation to SMS. |
Check the network between the source server and the API gateway. |
|
400 |
SMS.0210 |
Failed to create file %s on target server |
Failed to create file %s on target server. |
Check the network and start the migration task again. |
|
400 |
SMS.0211 |
Failed to send certificate decryption key to target server |
Failed to send the certificate decryption key to the target server. |
Check the network and start the migration task again. |
|
400 |
SMS.0212 |
Failed to obtain certificate decryption key. Delete the target configuration and configure the target server again |
Migration failed because the source server failed to obtain certificate decryption key. |
Delete the target configuration and configure the migration task again. |
|
400 |
SMS.0301 |
Incorrect proxy information. Check proxy configuration and try again. |
Incorrect proxy information. Check proxy configuration and try again. |
Modify the proxy information. |
|
400 |
SMS.0302 |
Failed to resolve domain name {0[0]}. |
Failed to resolve domain name {0[0]}. |
Check whether the domain name is reachable. |
|
400 |
SMS.0303 |
Unable to access domain name {0[0]}. |
Unable to access domain name {0[0]}. |
Check whether the domain name is reachable. |
|
400 |
SMS.0401 |
No project ID found. Cause: %s |
No project ID found. Cause: %s |
Contact technical support. |
|
400 |
SMS.0406 |
No image found. Cause: %s |
No image found. Cause: %s |
Contact technical support. |
|
400 |
SMS.0407 |
No target server information found. Cause: %s |
No target server information found. Cause: %s |
Contact technical support. |
|
400 |
SMS.0408 |
Failed to obtain details about target server %s. Cause: %s |
Failed to obtain details about target server %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.0409 |
Failed to obtain volume information of target server %s. Cause %s |
Failed to obtain volume information of target server %s. Cause %s |
Contact technical support. |
|
400 |
SMS.0410 |
Failed to obtain NIC information of target server %s. Cause: %s |
Failed to obtain NIC information of target server %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.0411 |
Disk %s does not exist. |
Disk %s does not exist. |
The disk has been deleted. Migrate the source server again. |
|
400 |
SMS.0412 |
Target server %s does not exist. |
Target server %s does not exist. |
The target server has been deleted. Migrate the source server again. |
|
400 |
SMS.0413 |
Failed to query the region where the bucket locates. Cause: %s |
Failed to query the region where the bucket locates. Cause: %s |
Contact technical support. |
|
400 |
SMS.0414 |
Failed to copy logs from the customer's OBS bucket to the destination bucket. Cause: %s |
Failed to copy logs from the customer's OBS bucket to the destination bucket. Cause: %s |
Contact technical support. |
|
400 |
SMS.0415 |
Failed to obtain the target server specifications. Cause: %s |
Failed to obtain the target server specifications. Cause: %s |
Contact technical support. |
|
400 |
SMS.0416 |
No VPC found. Cause: %s |
No VPC discovered. Cause: %s |
Contact technical support. |
|
400 |
SMS.0417 |
No security group found. Cause: %s |
No security group discovered. Cause: %s |
Contact technical support. |
|
400 |
SMS.0418 |
No subnet found. Cause: %s |
No subnet discovered. Cause: %s |
Contact technical support. |
|
400 |
SMS.0419 |
Failed to obtain the volume details of target server %s by calling the combined API. Cause: %s |
Failed to obtain the volume details of target server %s by calling the combined API. Cause: %s |
Contact technical support. |
|
400 |
SMS.0420 |
Failed to obtain the disk details of the target server. Cause: %s |
Failed to obtain the disk details of the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.0421 |
Failed to obtain the domain ID. Cause: %s |
Failed to obtain the domain ID. Cause: %s |
Contact technical support. |
|
400 |
SMS.0422 |
Failed to obtain the details about the VPC with the specified ID. |
Failed to obtain the details about the VPC with the specified ID. |
Contact technical support. |
|
400 |
SMS.0423 |
The VPC with the specified ID is abnormal. |
The VPC with the specified ID is abnormal. |
Contact technical support. |
|
400 |
SMS.0424 |
The obtained list of disks on the target server has no content. |
The obtained list of disks on the target server has no content. |
Contact technical support. |
|
400 |
SMS.0426 |
Response body too long. Maximum length: %s |
Response body too long. Maximum length: %s |
Modify the maximum length limit in the configuration file. |
|
400 |
SMS.0501 |
Failed to report the task progress to SMS. |
Failed to report the task progress to SMS. |
Contact technical support. |
|
400 |
SMS.0502 |
Source server registration failed. Cause: %s |
Source server registration failed. Cause: %s |
Contact technical support. |
|
400 |
SMS.0503 |
Log upload failed. Cause: %s |
Log upload failed. Cause: %s |
Contact technical support. |
|
400 |
SMS.0504 |
Failed to obtain task details. Cause: %s |
Failed to obtain task details. Cause: %s |
Contact technical support. |
|
400 |
SMS.0505 |
Task %s not found. Check whether the task has been deleted. |
Task %s not found. Check whether the task has been deleted. |
If the task is not deleted, contact technical support. |
|
400 |
SMS.0506 |
Failed to obtain template details. Template ID: %s |
Failed to obtain template details. Template ID: %s |
Contact technical support. |
|
400 |
SMS.0507 |
Source server details deleted. Register it with SMS again. |
Source server details deleted. Register it with SMS again. |
Register the source server with SMS again. |
|
400 |
SMS.0508 |
Failed to obtain commands from the source server. Cause %s |
Failed to obtain commands from source server %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.0510 |
Failed to update the replication status to %s. |
Failed to update the replication status to %s. |
Contact technical support. |
|
400 |
SMS.0511 |
Failed to obtain the private key. Cause: %s |
Failed to obtain the private key. Cause: %s |
Contact technical support. |
|
400 |
SMS.0512 |
Failed to update task details. |
Failed to update task details. |
Contact technical support. |
|
400 |
SMS.0513 |
Failed to add the subtask. |
Failed to add the subtask. |
Contact technical support. |
|
400 |
SMS.0514 |
Updating source server information failed. Cause: {0[0]} |
Updating source server information failed. Cause: {0[0]} |
Contact technical support. |
|
400 |
SMS.0515 |
Migration failed. Source disk information has changed. Delete target server configuration and restart the Agent. |
Migration failed. Source disk information has changed. Delete target server configuration and restart the Agent. |
Delete target server configuration and restart the Agent. |
|
400 |
SMS.0516 |
Failed to execute the synchronization task, because the I/O monitoring module failed to run. |
Failed to execute the synchronization task, because the I/O monitoring module failed to run. |
Contact technical support. |
|
400 |
SMS.0519 |
Not enough space. Delete target configuration, restart Agent, and expand target partition. |
Not enough space. Delete target configuration, restart Agent, and expand target partition. |
Delete target configuration, restart Agent, and expand target partition. |
|
400 |
SMS.0601 |
Target server creation failed. Cause: %s |
Target server creation failed. Cause: %s |
Contact ECS technical support. |
|
400 |
SMS.0602 |
VPC creation failed. Cause: %s |
VPC creation failed. Cause: %s |
Contact VPC technical support. |
|
400 |
SMS.0603 |
Security group creation failed. Cause: %s |
Security group creation failed. Cause: %s |
Contact VPC technical support. |
|
400 |
SMS.0604 |
Failed to add the security group rule. Cause: %s |
Failed to add the security group rule. Cause: %s |
Contact VPC technical support. |
|
400 |
SMS.0605 |
Subnet creation failed. Cause: %s |
Subnet creation failed. Cause: %s |
Contact VPC technical support. |
|
400 |
SMS.0606 |
No general-computing server flavors are available in this AZ. Select another flavor. |
No general-computing server flavors are available in this AZ. Select another flavor. |
Select another flavor. |
|
400 |
SMS.0607 |
cloud-region.json does not contain details about the current region. |
cloud-region.json does not contain details about the current region. |
Contact technical support. |
|
400 |
SMS.0608 |
Volume creation failed. Cause: %s |
Volume creation failed. Cause: %s |
Contact technical support. |
|
400 |
SMS.0804 |
File upload failed. |
File upload failed. |
Check whether the network is functional. |
|
400 |
SMS.0805 |
Failed to migrate partition %s to target server %s. |
Failed to migrate partition %s to target server %s. |
Handle the problem as instructed in the corresponding case. |
|
400 |
SMS.0806 |
Failed to synchronize partition %s to target server %s. |
Failed to synchronize partition %s to target server %s. |
Handle the problem as instructed in the corresponding case. |
|
400 |
SMS.0807 |
Network error between source and target servers. |
The network between the source and target servers is abnormal. |
Check whether the network is functional. |
|
400 |
SMS.1101 |
Failed to start target server %s. |
Failed to start target server %s. |
Contact technical support. |
|
400 |
SMS.1102 |
Failed to stop target server %s. |
Failed to stop target server %s. |
Contact technical support. |
|
400 |
SMS.1103 |
Failed to attach disk %s. Cause: %s |
Failed to attach disk %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1104 |
Failed to detach disk %s. Cause: %s |
Failed to detach disk %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1105 |
Disk creation failed. Cause: %s |
Disk creation failed. Cause: %s |
Contact technical support. |
|
400 |
SMS.1106 |
Failed to delete disk %s. Cause: %s |
Failed to delete disk %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1107 |
Failed to upload the private key and certificate to target server %s. Cause: %s |
Failed to upload the private key and certificate to target server %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1108 |
Failed to detach disk %s. |
Failed to detach disk %s. |
Contact technical support. |
|
400 |
SMS.1109 |
An exception occurred when the private key and certificate are uploaded to target server %s |
An exception occurred when the private key and certificate are uploaded to target server %s. |
Contact technical support. |
|
400 |
SMS.1110 |
Failed to attach disk %s. |
Failed to attach disk %s. |
Contact technical support. |
|
400 |
SMS.1111 |
Failed to start target server %s. Cause %s |
Failed to start target server %s. Cause %s |
Contact technical support. |
|
400 |
SMS.1112 |
Failed to stop target server %s. Cause: %s |
Failed to stop target server %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1113 |
Failed to reconfigure partition details on the target server. |
Failed to reconfigure partition details on the target server. |
Contact technical support. |
|
400 |
SMS.1114 |
Failed to send command to the target server. |
Failed to send command to the target server. |
Contact technical support. |
|
400 |
SMS.1116 |
Failed to set type for disk %s. Cause: %s |
Failed to set type for disk %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1117 |
Failed to generate the RSA key pair on the target server. |
Failed to generate the RSA key pair on the target server. |
Contact technical support. |
|
400 |
SMS.1118 |
Failed to query the content of file %s. |
Failed to query the content of file %s. |
Contact technical support. |
|
400 |
SMS.1119 |
Failed to restart SSHD on the target server. |
Failed to restart SSHD on the target server. |
Contact technical support. |
|
400 |
SMS.1120 |
Command execution on the Windows server failed. Cause: missing command or command parameter. |
Command execution on the Windows server failed. Cause: missing command or command parameter. |
Contact technical support. |
|
400 |
SMS.1201 |
%s not installed. |
%s not installed. |
Contact technical support. |
|
400 |
SMS.1202 |
Public agent image not registered in this region. Download the latest Agent. |
Public agent image not registered in this region. Download the latest Agent. |
Download the latest Agent. |
|
400 |
SMS.1203 |
Insufficient memory on the source server. |
Insufficient memory on the source server. |
Close programs on source server to release memory. |
|
400 |
SMS.1204 |
Failed to create a file on the source server. Cause: %s |
Failed to create a file on the source server. Cause: %s |
Contact technical support. |
|
400 |
SMS.1205 |
Failed to load WMI. Go to the official website to view the solution. |
Failed to load WMI. Go to the official website to view the solution. |
Handle the problem as instructed in the corresponding case. |
|
400 |
SMS.1301 |
Failed to write partition information to the configuration file. |
Failed to write partition information to the configuration file. |
Contact technical support. |
|
400 |
SMS.1311 |
Insufficient disks on the target server. |
Insufficient disks on the target server. |
Add disks to the target server. |
|
400 |
SMS.1312 |
Partition failed. Disk: %s. Cause: %s |
Partition failed. Disk: %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1313 |
Failed to create physical volume %s. Cause: %s |
Failed to create physical volume %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1314 |
Formatting failed. Partition: %s. Cause: %s |
Formatting failed. Partition: %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1315 |
Insufficient free space on target partition %s. |
Insufficient free space on target partition %s. |
Expand the partition capacity. |
|
400 |
SMS.1401 |
Failed to copy the I/O monitoring module. |
Failed to copy the I/O monitoring module. |
Contact technical support. |
|
400 |
SMS.1402 |
SSH client not installed. Install the openssh-clients package and check the installation with ssh -V. |
SSH client not installed. Install the openssh-clients package and check the installation with ssh -V. |
If the problem persists, contact technical support. |
|
400 |
SMS.1403 |
No grub file found. Find it under /boot. |
No grub file found. Find it under /boot. |
If there is no grub file under /boot, contact technical support. |
|
400 |
SMS.1404 |
Disk %s is abnormal. Expected status: %s |
Disk %s is abnormal. Expected status: %s |
Contact technical support. |
|
400 |
SMS.1405 |
Failed to obtain information about disk %s. Cause: %s |
Failed to obtain information about disk %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1406 |
Failed to obtain the EIP. Cause: %s |
Failed to obtain the EIP. Cause: %s |
Contact technical support. |
|
400 |
SMS.1407 |
Failed to obtain the target server specifications. Cause: %s |
Failed to obtain the target server specifications. Cause: %s |
Contact technical support. |
|
400 |
SMS.1408 |
Snapshot creation failed. Disk: %s. Cause: %s |
Snapshot creation failed. Disk: %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1409 |
Failed to delete snapshot %s. Cause: %s |
Failed to delete snapshot %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1410 |
Snapshot %s does not exist. |
Snapshot %s does not exist. |
Contact technical support. |
|
400 |
SMS.1411 |
Snapshot %s is in the %s state. |
Snapshot %s is in the %s state. |
Contact technical support. |
|
400 |
SMS.1412 |
Snapshot %s rollback failed. Cause: %s |
Snapshot %s rollback failed. Cause: %s |
Contact technical support. |
|
400 |
SMS.1413 |
Failed to obtain the status of snapshot %s. Cause: %s |
Failed to obtain the status of snapshot %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.1414 |
The migration module stopped abnormally and cannot synchronize data. |
The migration module stopped abnormally and cannot synchronize data. |
Contact technical support. |
|
400 |
SMS.1423 |
Failed to obtain details about snapshot {0[0]}. Cause: {0[1]} |
Failed to obtain details about snapshot {0[0]}. Cause: {0[1]} |
Contact technical support. |
|
400 |
SMS.1501 |
OS version not supported. |
OS version not supported. |
Contact technical support. |
|
400 |
SMS.1502 |
Target server %s is abnormal. Expected status: %s |
Target server %s is abnormal. Expected status: %s |
Contact technical support. |
|
400 |
SMS.1503 |
Disk %s is not the system boot disk. |
Disk %s is not the system boot disk. |
Contact technical support. |
|
400 |
SMS.1504 |
The sizes of disks on the target server do not match those on the source server. |
The sizes of disks on the target server do not match those on the source server. |
Contact technical support. |
|
400 |
SMS.1505 |
No boot partition found. |
No boot partition found. |
Contact technical support. |
|
400 |
SMS.1506 |
No boot disk found. |
No boot disk found. |
Contact technical support. |
|
400 |
SMS.1507 |
No system partition found. |
No system partition found. |
Contact technical support. |
|
400 |
SMS.1508 |
Mount point, partition, or disk configured in disk.cfg not found. |
Mount point, partition, or disk configured in disk.cfg not found. |
Check the disk.cfg file. |
|
400 |
SMS.1509 |
Invalid disk.cfg file. |
Invalid disk.cfg file. |
Check the disk.cfg file. |
|
400 |
SMS.1510 |
Configure advanced option %s failed. Cause: %s. |
Configure advanced option %s failed. Cause: %s |
Check the settings. |
|
400 |
SMS.1511 |
Failed to check the consistency. Cause: %s |
Failed to verify data consistency. Cause: %s |
Contact technical support. |
|
400 |
SMS.1701 |
The installed Agent cannot migrate the server to this region. Install the latest Agent. |
The installed Agent cannot migrate the server to this region. Install the latest Agent. |
If the problem persists, contact technical support. |
|
400 |
SMS.1702 |
An error occurred when converting the string into the JSON format. |
An error occurred when converting the string into the JSON format. |
Contact technical support. |
|
400 |
SMS.1801 |
Migration or synchronization task failed. |
Migration or synchronization task failed. |
Contact technical support. |
|
400 |
SMS.1802 |
Migration or synchronization task paused. |
Migration or synchronization task paused. |
Contact technical support. |
|
400 |
SMS.1805 |
Migration or synchronization task failed because memory allocation on the target server failed. |
The migration or synchronization task failed because memory allocation on the target server failed. |
Contact technical support. |
|
400 |
SMS.1807 |
Failed to connect to the target server. Check whether its IP address %s is reachable and confirm that port 8900 is enabled. |
Failed to connect to the target server. Check whether its IP address %s is reachable and confirm that port 8900 is enabled. |
If the connection still fails, contact technical support. |
|
400 |
SMS.1901 |
Agent could not read disk information. |
Agent could not read disk information. |
Contact technical support. |
|
400 |
SMS.1902 |
Failed to start the I/O monitoring module. |
Failed to start the I/O monitoring module. |
Contact technical support. |
|
400 |
SMS.1903 |
No valid block data found. |
No valid block data found. |
Contact technical support. |
|
400 |
SMS.1904 |
Failed to create a snapshot for the Windows server. |
Failed to create a snapshot for the Windows server. |
Contact technical support. |
|
400 |
SMS.1905 |
Failed to read the disk information. |
Failed to read the disk information. |
Contact technical support. |
|
400 |
SMS.1907 |
Failed to send the migration command. |
Failed to send the migration command. |
Contact technical support. |
|
400 |
SMS.1908 |
Data transmission failed. |
Data transmission failed. |
Contact technical support. |
|
400 |
SMS.1909 |
Data compression failed. |
Data compression failed. |
Contact technical support. |
|
400 |
SMS.1910 |
Failed to obtain the I/O monitoring data. |
Failed to obtain the I/O monitoring data. |
Contact technical support. |
|
400 |
SMS.1911 |
Boot sector read error. |
Boot sector read error. |
Contact technical support. |
|
400 |
SMS.2003 |
Volume reconfiguration failed. |
Volume reconfiguration failed. |
Contact technical support. |
|
400 |
SMS.2004 |
Failed to back up volume sector details on the target server. |
Failed to back up volume sector details on the target server. |
Contact technical support. |
|
400 |
SMS.2007 |
Failed to write data to disks on the target server. |
Failed to write data to disks on the target server. |
Contact technical support. |
|
400 |
SMS.2009 |
Data decompression failed. |
Data decompression failed. |
Contact technical support. |
|
400 |
SMS.2011 |
Failed to receive data. |
Failed to receive data. |
Contact technical support. |
|
400 |
SMS.2012 |
Failed to read or parse the volume information from the configuration file. |
Failed to read or parse the volume information from the configuration file. |
Contact technical support. |
|
400 |
SMS.2013 |
Failed to open the disk. |
Failed to open the disk. |
Contact technical support. |
|
400 |
SMS.2014 |
Failed to hide the partition information. |
Failed to hide the partition information. |
Contact technical support. |
|
400 |
SMS.2015 |
Failed to restore the partition information. |
Failed to restore the partition information. |
Contact technical support. |
|
400 |
SMS.2016 |
Drive letter restoration failed. |
Drive letter restoration failed. |
Contact technical support. |
|
400 |
SMS.2017 |
Failed to traverse all volumes. |
Failed to traverse all volumes. |
Contact technical support. |
|
400 |
SMS.2018 |
Error in reading the volume boot sector. |
Error in reading the volume boot sector. |
Contact technical support. |
|
400 |
SMS.2101 |
Registry modification failed. |
Registry modification failed. |
Contact technical support. |
|
400 |
SMS.2102 |
Failed to modify the device information. |
Failed to modify the device information. |
Contact technical support. |
|
400 |
SMS.2103 |
Failed to set active partitions. |
Failed to set active partitions. |
Contact technical support. |
|
400 |
SMS.2104 |
Failed to modify BCD configuration. |
Failed to modify BCD configuration. |
Contact technical support. |
|
400 |
SMS.2105 |
Failed to modify boot configuration file. |
Failed to modify boot configuration file. |
Contact technical support. |
|
400 |
SMS.2201 |
Failed to clear disk information. |
Failed to clear disk information. |
Contact technical support. |
|
400 |
SMS.2202 |
Failed to convert the format of disk %s. |
Failed to convert the format of disk %s. |
Contact technical support. |
|
400 |
SMS.2203 |
Failed to create partition %s. |
Failed to create partition %s. |
Contact technical support. |
|
400 |
SMS.2204 |
Failed to format partition %s. |
Failed to format partition %s. |
Contact technical support. |
|
400 |
SMS.2205 |
Failed to update the partition information. |
Failed to update the partition information. |
Contact technical support. |
|
400 |
SMS.2301 |
Failed to start ntcldst. |
Failed to start ntcldst. |
Contact technical support. |
|
400 |
SMS.2802 |
Failed to connect to the target server. Check whether its IP address %s is reachable and port 8899 is enabled. |
Failed to connect to the target server. Check whether its IP address %s is reachable and port 8899 is enabled. |
If the connection still fails, contact technical support. |
|
400 |
SMS.3101 |
Failed to modify the configuration file of the target server. Cause: %s |
Failed to modify the configuration file of the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3102 |
Failed to modify the initrd file on the target server. Cause: %s |
Failed to modify the initrd file on the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3103 |
Failed to execute bootloader on the target server. Cause: %s |
Failed to execute bootloader on the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3104 |
Failed to read /etc/fstab on the source server. Cause: %s |
Failed to read /etc/fstab on the source server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3202 |
Failed to create volume group %s. Cause: %s |
Failed to create volume group %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.3203 |
Failed to create logical volume %s. Cause: %s |
Failed to create logical volume %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.3204 |
Failed to create swap partition %s. Cause: %s |
Failed to create swap partition %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.3205 |
Failed to mount partition %s to directory %s. Cause: %s |
Failed to mount partition %s to directory %s. Cause: %s |
Contact technical support. |
|
400 |
SMS.3206 |
Failed to obtain the UUID of the partition on the target server. Cause: %s |
Failed to obtain the UUID of the partition on the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3207 |
Failed to create file %s on the target server. Cause: %s |
Failed to create file %s on the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3208 |
Failed to write file %s on the target server. Cause: %s |
Failed to write file %s on the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3209 |
Failed to assign execution permission to the script on the target server. Cause: %s |
Failed to assign execution permission to the script on the target server. Cause: %s |
Contact technical support. |
|
400 |
SMS.3210 |
Failed to format partition {0[0]} to {0[1]}. Cause: {0[2]} |
Failed to format partition {0[0]} to {0[1]}. Cause: {0[2]} |
Contact technical support. |
|
400 |
SMS.3300 |
Failed to read the configuration file for Linux block-level migration. |
Failed to read the configuration file for Linux block-level migration. |
Download the latest Agent. |
|
400 |
SMS.3301 |
Failed to load the SSL certificate. |
Failed to load the SSL certificate. |
Create a migration task again. |
|
400 |
SMS.3401 |
Download of RSA public and private keys failed. HTTP Status Code: %s |
Download of RSA public and private keys failed. HTTP Status Code: %s |
Contact technical support. |
|
400 |
SMS.3402 |
Download of RSA public and private keys failed. |
Download of RSA public and private keys failed. |
Contact technical support. |
|
400 |
SMS.3802 |
Failed to establish an SSH connection with the target server. |
Failed to establish an SSH connection with the target server. |
Check the network. |
|
400 |
SMS.3803 |
The connection to the target server failed, because an error occurred during the public key verification on the target server. |
The connection to the target server failed, because an error occurred during the public key verification on the target server. |
Contact technical support. |
|
400 |
SMS.3804 |
The connection to the target server failed due to invalid connection credential. |
The connection to the target server failed due to invalid connection credential. |
Contact technical support. |
|
400 |
SMS.3805 |
The connection to the target server timed out. |
The connection to the target server timed out. |
Check the network. |
|
400 |
SMS.3806 |
The connection to the target server was rejected. |
The connection to the target server was rejected. |
Contact technical support. |
|
400 |
SMS.3807 |
Failed to upload the file to the target server. |
Failed to upload the file to the target server. |
Contact technical support. |
|
400 |
SMS.3808 |
Failed to ping target server. |
Failed to ping target server. |
Check the network environment. |
|
400 |
SMS.5101 |
Agent installation failed. |
Agent installation failed. |
Contact technical support. |
|
400 |
SMS.5102 |
Agent startup failed because the noexec permission is unavailable on /tmp in Linux. |
Agent startup failed because the noexec permission is unavailable on /tmp in Linux. |
Grant the noexec permission to the /tmp directory. |
|
400 |
SMS.5103 |
Agent startup failed due to insufficient space on /tmp in Linux. |
Agent startup failed due to insufficient space on /tmp in Linux. |
Increase the size of /tmp. |
|
400 |
SMS.5104 |
Failed to paste AK or SK. |
Failed to paste AK or SK. |
Restart the Agent. |
|
400 |
SMS.5105 |
Agent startup failed because the current shell character set is wrong. |
Agent startup failed because the current shell character set is wrong. |
Set the coding mode of the character set to UTF-8. |
|
400 |
SMS.5106 |
Internal error. Failed to create a temporary directory. |
Internal error. Failed to create a temporary directory. |
Run the Agent as administrator. |
|
400 |
SMS.5107 |
Failed to open the file for writing. |
Failed to open the file for writing. |
Contact technical support. |
|
400 |
SMS.5108 |
Failed to execute df -TH. |
Failed to execute df -TH. |
Check whether a mounted device is offline or does not exist. |
|
400 |
SMS.5109 |
The application cannot be started due to incorrect parallel configuration. |
The application cannot be started due to incorrect parallel configuration. |
Run SMSAgentDeploy.exe directly. |
|
400 |
SMS.5110 |
The Windows Agent unable to launch. |
The Windows Agent unable to launch. |
Unlock the file and try again. |
|
400 |
SMS.5111 |
Agent startup failed. Multiple volume groups found with the same name. |
Agent startup failed. Multiple volume groups found with the same name. |
Contact technical support. |
|
400 |
SMS.5301 |
Booting with GRUB failed. |
Booting with GRUB failed. |
Reinstall the GRUB bootloader. |
|
400 |
SMS.5302 |
Failed to install the KVM driver. |
Failed to install the KVM driver. |
Uninstall the Xen driver and install the KVM driver. |
|
400 |
SMS.5401 |
Disks of the Windows target server are offline. |
Disks of the Windows target server are offline. |
Bring the disks online manually. |
|
400 |
SMS.5402 |
Network error on the target server running Windows 2003. |
Network error on the target server running Windows 2003. |
Use another migration method. |
|
400 |
SMS.5403 |
Progress is slow or suspended. |
Progress is slow or suspended. |
Check whether the bandwidth is too low. |
|
400 |
SMS.5404 |
The target server running CentOS 6.x cannot access the Internet. |
The target server running CentOS 6.x cannot access the Internet. |
Contact technical support. |
|
400 |
SMS.5601 |
The disk usage changes greatly after migration. |
The disk usage changes greatly after migration. |
Contact technical support. |
|
400 |
SMS.5602 |
Time error occurred in the target server running Linux. |
Time error occurred in the target server running Linux. |
Use NTP for time synchronization. |
|
400 |
SMS.5603 |
The target server running Windows cannot access the Internet. |
The target server running Windows cannot access the Internet. |
Reinstall the NIC driver. |
|
400 |
SMS.5604 |
The MySQL service on the target server cannot be started. |
The MySQL service on the target server cannot be started. |
Stop services and synchronize data again. |
|
400 |
SMS.5605 |
After the migration is complete, the target server starts and the System Recovery Options window is displayed. |
After the migration is complete, the target server starts and the System Recovery Options window is displayed. |
Contact technical support. |
|
400 |
SMS.5606 |
Windows fails to start because the Xen driver is abnormal. |
Windows fails to start because the Xen driver is abnormal. |
Contact technical support. |
|
400 |
SMS.6000 |
Service error. |
Service error. |
Contact technical support. |
|
400 |
SMS.6001 |
The source server name is a required field. |
The source server name is a required field. |
Specify the source server name. |
|
400 |
SMS.6002 |
Source server names must consist of 4 to 20 characters. |
Source server names must consist of 4 to 20 characters. |
Specify a source server name containing 4 to 20 characters. |
|
400 |
SMS.6003 |
Uppercase letters, lowercase letters, and digits are allowed. |
Uppercase letters, lowercase letters, and digits are allowed. |
Specify a source server name with uppercase letters, lowercase characters, or digits. |
|
400 |
SMS.6004 |
Invalid subtask name. |
Invalid subtask name. |
Enter a valid subtask name. |
|
400 |
SMS.6005 |
The status of the sourceServer does not meet the requirements. |
The source server status does not meet requirements. |
Contact technical support. |
|
400 |
SMS.6010 |
The request body is not in the JSON format. |
The request body is not in the JSON format. |
Set the request body as required. |
|
400 |
SMS.6011 |
The JSON request body does not meet the specifications. |
The JSON request body does not meet the specifications. |
Set the request body as required. |
|
400 |
SMS.6012 |
Empty request body. |
Empty request body. |
Set the request body as required. |
|
400 |
SMS.6013 |
Incomplete request parameters. |
Incomplete request parameters. |
Check whether all required parameters are included. |
|
400 |
SMS.6014 |
The parameter part in the request body is too long. |
The parameter part in the request body is too long. |
Modify the request parameters. |
|
400 |
SMS.6015 |
The request header is missing. |
The request header is missing. |
Add a request header. |
|
400 |
SMS.6016 |
The header type must be application/json. |
The header type must be application/json. |
Ensure that the request header type is application/json. |
|
400 |
SMS.6020 |
The command name is missing. |
The command name is missing. |
Contact technical support. |
|
400 |
SMS.6021 |
The command from the Agent is inconsistent with that from SMS. |
The command from the Agent is inconsistent with that from SMS. |
Enter the command from SMS correctly. |
|
400 |
SMS.6022 |
Incorrect result format. |
Incorrect result format. |
Set the result in the correct format. |
|
400 |
SMS.6023 |
Incorrect result_detail format. |
Incorrect result_detail format. |
Set result_detail in the correct format. |
|
400 |
SMS.6030 |
Invalid source server ID. |
Invalid source server ID. |
Enter a correct source server ID. |
|
400 |
SMS.6031 |
The target server information is missing. |
The target server information is missing. |
Enter the required target server information. |
|
400 |
SMS.6032 |
The target server ID is missing. |
The target server ID is missing. |
Enter the target server ID. |
|
400 |
SMS.6033 |
The disk information is missing. |
The disk information is missing. |
Enter the disk information of the target server. |
|
400 |
SMS.6034 |
Invalid region name. |
Invalid region name. |
Enter a valid region name. |
|
400 |
SMS.6035 |
Domain ID is missing. |
Domain ID is missing. |
Enter the domain ID. |
|
400 |
SMS.6101 |
Invalid migration progress. |
Invalid migration progress. |
Enter an integer ranging from 0 to 100. |
|
400 |
SMS.6102 |
Parameters do not meet the JSON format requirements. |
Parameters do not meet the JSON format requirements. |
Check whether the JSON format is correct. |
|
400 |
SMS.6103 |
Disk ID is missing. |
Disk ID is missing. |
Enter a disk ID. |
|
400 |
SMS.6104 |
Physical volume name is missing. |
Physical volume name is missing. |
Enter a volume name. |
|
400 |
SMS.6105 |
Physical volume size is missing or invalid. |
Physical volume size is missing or invalid. |
Enter a valid volume size. |
|
400 |
SMS.6301 |
Database read or write error. |
Database read or write error. |
Contact technical support. |
|
400 |
SMS.6302 |
No migration speed limit found. |
No migration speed limit found. |
Reset the migration speed limit |
|
400 |
SMS.6303 |
The installed Agent is of an earlier version. Download the latest version. |
The installed Agent is of an earlier version. Download the latest version. |
Download the latest version. |
|
400 |
SMS.6304 |
Fail to get config information. |
Fail to get configuration information. |
Contact technical support. |
|
400 |
SMS.6401 |
Unsupported encoding mode. |
Unsupported encoding mode. |
Use a correct encoding mode. |
|
400 |
SMS.6402 |
The algorithm does not exist. |
The algorithm does not exist. |
Contact technical support. |
|
400 |
SMS.6403 |
Failed to split into strings of the specified size. |
Failed to split into strings of the specified size. |
Contact technical support. |
|
400 |
SMS.6404 |
An error occurred during integer conversion. |
An error occurred during integer conversion. |
Contact technical support. |
|
400 |
SMS.6405 |
Invalid time format. |
Invalid time format. |
Check the time format. |
|
400 |
SMS.6407 |
Current quota is not enough, please use MgC. |
Insufficient quota. Please use MgC. |
Use MgC for migration. |
|
400 |
SMS.6501 |
You can add up to 1,000 source servers. |
You can add up to 1,000 source servers. |
Delete the source servers that have been migrated. |
|
400 |
SMS.6502 |
Environment check cannot be performed on the source server in the CHECKING state. |
Environment check cannot be performed on the source server in the CHECKING state. |
Contact technical support. |
|
400 |
SMS.6503 |
Failed to obtain the OS version of the source server. |
Failed to obtain the OS version of the source server. |
Enter the OS version of the source server. |
|
400 |
SMS.6504 |
Unsupported source server OS version or firmware type. |
Unsupported source server OS version or firmware type. |
Review which source server OSs and firmware types are supported. |
|
400 |
SMS.6505 |
Unknown source firmware type. It must be BIOS or UEFI. |
Unknown source firmware type. It must be BIOS or UEFI. |
Use another migration method. |
|
400 |
SMS.6506 |
Failed to obtain the number of source server CPUs. |
Failed to obtain the number of source server CPUs. |
Contact technical support. |
|
400 |
SMS.6507 |
Failed to open the system directory of the source server. |
Failed to open the system directory of the source server. |
Contact technical support. |
|
400 |
SMS.6508 |
Incompatible disk format on the source server. Only GPT and MBR are compatible. |
Incompatible disk format on the source server. Only GPT and MBR are compatible. |
Use another migration method. |
|
400 |
SMS.6509 |
Incompatible file system of the source server. |
Incompatible file system of the source server. |
Use another migration method. |
|
400 |
SMS.6510 |
The source server OS is an OEM system. |
The source server OS is an OEM system. |
Activate the system after migration. |
|
400 |
SMS.6511 |
The source server lacks driver files. |
The source server lacks driver files. |
Contact technical support. |
|
400 |
SMS.6512 |
The system services required for the migration on the source server are not running normally. |
The system services required for the migration on the source server are not running normally. |
Contact technical support. |
|
400 |
SMS.6513 |
No administrator permissions on the source server. |
No administrator permissions on the source server. |
Check whether the current account has the administrator permissions. |
|
400 |
SMS.6514 |
Failed to obtain the memory size of the source server. |
Failed to obtain the memory size of the source server. |
Contact technical support. |
|
400 |
SMS.6515 |
The source server is paravirtualized. |
The source server is paravirtualized. |
Use another migration method. |
|
400 |
SMS.6516 |
The Linux bootloader must be GRUB. |
The Linux bootloader must be GRUB. |
Check whether the Linux bootloader is GRUB. |
|
400 |
SMS.6517 |
rsync not installed on the source server. |
rsync not installed on the source server. |
Install rsync on the source server. |
|
400 |
SMS.6518 |
The source server has a raw device. |
The source server has a raw device. |
Use another migration method. |
|
400 |
SMS.6519 |
Failed to obtain disk information. |
Failed to obtain disk information. |
Contact technical support. |
|
400 |
SMS.6520 |
The source server is not in the AVAILABLE state. |
The source server is not in the AVAILABLE state. |
Check the source server status. |
|
400 |
SMS.6521 |
Token-based authentication failed. |
Token-based authentication failed. |
Use the correct token. |
|
400 |
SMS.6522 |
The X-Auth-Token header field is missing. |
The X-Auth-Token header field is missing. |
Add X-Auth-Token. |
|
400 |
SMS.6523 |
Apply for the permission required to operate SMS. |
Apply for the permission required to operate SMS. |
Ensure that you have the sms_administrator permission. |
|
400 |
SMS.6524 |
This operation is not allowed because you are not an OBT user. |
This operation is not allowed because you are not an OBT user. |
Join the OBT. |
|
400 |
SMS.6525 |
Insufficient balance. |
Insufficient balance. |
Ensure that the account balance is no less than ¥100 CNY. |
|
400 |
SMS.6526 |
Insufficient quota to clone the target server. |
Insufficient quota to clone the target server. |
Increase the cloud server quota. |
|
400 |
SMS.6527 |
The resource in the task does not belong to you. |
The resource in the task does not belong to you. |
Check the resources that belong to you. |
|
400 |
SMS.6528 |
Complete real-name authentication to invoke the SMS APIs. |
Complete real-name authentication to invoke the SMS APIs. |
Complete real-name authentication first. |
|
400 |
SMS.6529 |
SMS API call failed. Your account is in arrears. |
SMS API call failed. Your account is in arrears. |
Ensure that the account balance is no less than ¥100 CNY. |
|
400 |
SMS.6530 |
Invalid source server IP address. |
Invalid source server IP address. |
Enter a correct source server IP address. |
|
400 |
SMS.6531 |
The boot partition does not exist. |
The boot partition does not exist. |
Check whether the boot partition of the source server exists. |
|
400 |
SMS.6532 |
The system disk must be on the first disk. |
The system disk must be on the first disk. |
Check whether the system disk is on the first disk. |
|
400 |
SMS.6533 |
VSS not installed on the source server. |
VSS not installed on the source server. |
Check whether VSS has been installed and started. |
|
400 |
SMS.6534 |
No system directory information read. |
No system directory information read. |
Contact technical support. |
|
400 |
SMS.6535 |
Servers booted with UEFI do not support auto-creation of target servers for migration. |
Servers booted with UEFI do not support auto-creation of target servers for migration. |
Create a target ECS booted with UEFI and select the ECS as the target server. |
|
400 |
SMS.6536 |
The source server runs Windows 2003. Network may be unavailable after migration. |
The source runs Windows Server 2003. Network may be unavailable after migration. |
Upgrade the system and perform the migration. |
|
400 |
SMS.6537 |
SMS cannot migrate system disks larger than 1 TB. |
SMS cannot migrate system disks larger than 1 TB. |
Decrease the size of the source system disk. |
|
400 |
SMS.6538 |
The new partition or logical volume size is less than the used space size. |
The new partition or logical volume size is less than the used space size. |
Ensure that the new partition or logical volume size is at least 1 GB larger than the used space size. |
|
400 |
SMS.6540 |
Partitions on target servers running Windows cannot be reduced. |
Partitions on target servers running Windows cannot be reduced. |
Resize the partitions on source disks and restart the Agent |
|
400 |
SMS.6544 |
Network condition for migration is poor. |
Network condition for migration is poor. |
Contact technical support. |
|
400 |
SMS.6547 |
Excessive read/write latency has been detected for the source disks. It may slow down the migration or synchronization. |
Excessive read/write latency has been detected for the source disks. It may slow down the migration or synchronization. |
Optimize the disk performance. |
|
400 |
SMS.6548 |
The migration network performs poorly. It may slow down the migration or synchronization. |
The migration network performs poorly. It may slow down the migration or synchronization. |
Optimize the network performance. |
|
400 |
SMS.6560 |
Failed to obtain the project-level token. |
Failed to obtain the project-level token. |
Contact technical support. |
|
400 |
SMS.6561 |
The target server is not booted with UEFI. Create a target server using the image whose boot mode is UEFI. |
The target server is not booted with UEFI. Create a target server using the image whose boot mode is UEFI. |
Create a target server using the image whose boot mode is UEFI. |
|
400 |
SMS.6601 |
Invalid OS type. |
Invalid OS type. |
Set os_type by referring to SMS API Reference. |
|
400 |
SMS.6602 |
Invalid target server EIP. |
Invalid target server EIP. |
Enter an IP address in the correct format. |
|
400 |
SMS.6603 |
The connection to SMS was lost. |
The connection to SMS was lost. |
Re-establish the connection between the source server and SMS. For details, see "Migration Network" in SMS FAQs. |
|
400 |
SMS.6604 |
Failed to obtain ACL or firewall details for the target server. |
Failed to obtain ACL or firewall details for the target server. |
Contact technical support. |
|
400 |
SMS.6605 |
ACL or security group configuration error. |
ACL or security group configuration error. |
Modify the ACL or security group configuration. |
|
400 |
SMS.6610 |
The OS in the task conflicts with the source server OS. |
The OS in the task conflicts with the source server OS. |
Check whether the OS in the task is consistent with the source server OS. |
|
400 |
SMS.6611 |
Insufficient partition space than required. |
Insufficient partition space than required. |
Increase the partition space. |
|
400 |
SMS.6612 |
Invalid partition size. The partition size must be an integer multiple of MB. |
Invalid partition size. The partition size must be an integer multiple of MB. |
Enter a valid partition size. |
|
400 |
SMS.6613 |
33 MB of space must be reserved for GPT disks. |
33 MB of space must be reserved for GPT disks. |
Reserve 33 MB of space for GPT disks. |
|
400 |
SMS.6614 |
The target disk space must be greater than the total space of all partitions. |
The target disk space must be greater than the total space of all partitions. |
Increase the target disk space. |
|
400 |
SMS.6615 |
The target server has been added to a migration task. |
The target server has been added to a migration task. |
Change another server. |
|
400 |
SMS.6616 |
The current OS does not support block-level migration. |
The current OS does not support block-level migration. |
Use another migration method. |
|
400 |
SMS.6617 |
The current kernel does not support block-level migration. |
The current kernel does not support block-level migration. |
Use another migration method. |
|
400 |
SMS.6618 |
Failed to obtain kernel details. |
Failed to obtain kernel details. |
Contact technical support. |
|
400 |
SMS.7101 |
Template does not exist. |
Template does not exist. |
Check whether the template exists. |
|
400 |
SMS.7111 |
All tasks associated with this template must be deleted first. |
All tasks associated with this template must be deleted first. |
Delete the associated tasks first. |
|
400 |
SMS.7112 |
Duplicate template name. |
Duplicate template name. |
Change the template name. |
|
400 |
SMS.7301 |
The specified migration project does not exist. |
The specified migration project does not exist. |
Check whether the migration project exists. |
|
400 |
SMS.7303 |
Invalid migration project parameters. |
Invalid migration project parameters. |
Check the project parameters. |
|
400 |
SMS.7304 |
The default migration project does not exist. |
The default migration project does not exist. |
Create a default migration project first. |
|
400 |
SMS.7311 |
All source servers associated with the migration project must be deleted first. |
All source servers associated with the migration project must be deleted first. |
Delete all associated source servers first. |
|
400 |
SMS.7312 |
Duplicate migration project name. |
Duplicate migration project name. |
Change the migration project name. |
|
400 |
SMS.7313 |
The default migration project already exists. |
The default migration project already exists. |
Contact technical support. |
|
400 |
SMS.7321 |
The region name in the template is inconsistent with that in the migration project. |
The region name in the template is inconsistent with that in the migration project. |
Contact technical support. |
|
400 |
SMS.7501 |
No application ID generated. |
No application ID generated. |
Contact technical support. |
|
400 |
SMS.7602 |
The specified source server does not exist. |
The specified source server does not exist. |
Check whether the source server exists. |
|
400 |
SMS.7604 |
Failed to generate the source server ID. |
Failed to generate the source server ID. |
Contact technical support. |
|
400 |
SMS.7605 |
There is a migration task on the source server. |
There is a migration task on the source server. |
Delete the task and create a new one. |
|
400 |
SMS.7606 |
No migration task running on the source server. |
No migration task running on the source server. |
Contact technical support. |
|
400 |
SMS.7703 |
Task does not exist. |
Task does not exist. |
Check whether the task exists. |
|
400 |
SMS.7705 |
An error occurred when processing JSON files during task creation. |
An error occurred when processing JSON files during task creation. |
Contact technical support. |
|
400 |
SMS.7706 |
Task update failed. |
Task update failed. |
Contact technical support. |
|
400 |
SMS.7711 |
Invalid task name. |
Invalid task name. |
Enter a valid task name. |
|
400 |
SMS.7712 |
Invalid task type. |
Invalid task type. |
Enter a valid task type. |
|
400 |
SMS.7713 |
Only tasks in the Ready for next, Paused, or Error state can be started. |
Only tasks in the Ready for next, Paused, or Error state can be started. |
Change the task status. |
|
400 |
SMS.7714 |
Only running tasks can be paused. |
Only running tasks can be paused. |
Change the task status. |
|
400 |
SMS.7715 |
Only tasks in the Finished state or in the Continuous synchronization stage can be synchronized. |
Only tasks in the Finished state or in the Continuous synchronization stage can be synchronized. |
Change the task status. |
|
400 |
SMS.7716 |
Logs can be collected only after the current log collection is completed. |
Logs can be collected only after the current log collection is completed. |
Wait until the current log collection is complete. |
|
400 |
SMS.7717 |
Logs can be collected after the migration task is started. |
Logs can be collected after the migration task is started. |
Start the task first. |
|
400 |
SMS.7718 |
Only tasks in the Synchronization failed state can be rolled back. |
Only tasks in the Synchronization failed state can be rolled back. |
Change the task status. |
|
400 |
SMS.7719 |
Tasks in current state cannot be deleted. |
Tasks in current state cannot be deleted. |
Change the task status. |
|
400 |
SMS.7721 |
Only target servers in tasks in the Continuous synchronization state can be cloned or started. |
Only target servers in tasks in the Continuous synchronization state can be cloned or started. |
Change the task status. |
|
400 |
SMS.7722 |
Only tasks where the target servers have successfully started can be restarted. |
Only tasks where the target servers have successfully started can be restarted. |
Check whether the target server for the task has been started successfully. |
|
400 |
SMS.7723 |
Failed to delete the task. Ensure that the Agent is connected. |
Failed to delete the task. Ensure that the Agent is connected. |
Ensure that the Agent is connected. |
|
400 |
SMS.7724 |
No project ID found. |
No project ID found. |
Contact technical support. |
|
400 |
SMS.7725 |
No region information found. |
No region information found. |
Contact technical support. |
|
400 |
SMS.7726 |
Failed to update the migration status or stage of the source server. Field copystate or migrationcycle is missing in the request body. |
Failed to update the migration status or stage of the source server. The copystate or migrationcycle field is missing in the request body. |
Add the copystate or migrationcycle field to the request body. |
|
400 |
SMS.7727 |
Failed to update the migration status or stage of the source server. Field copystate or migrationcycle in the request body is empty. |
Failed to update the migration status or stage of the source server. The copystate or migrationcycle field in the request body is empty. |
Specify a value for copystate or migrationcycle in the request body. |
|
400 |
SMS.7728 |
Change server replication state or migration cycle failed. Values of copystate and migrationcycle do not match. |
Failed to update the migration status or stage for the source server. Fields copystate and migrationcycle do not match. |
Setcopystate and migrationcycle according to the following rules:
-
If the value of migrationcycle is checking, the value of copystate can be unavailable, waiting, or unconnected.
-
If the value of migrationcycle is setting, the value of copystate can be waiting or unconnected.
-
If the value of migrationcycle is replicating, the value of copystate can be initialize, replicate, deleting, stopping, error, stopped, or unconnected.
-
If the value of migrationcycle is syncing, the value of copystate can be syncing, cloning, deleting, stopping, error, stopped, or unconnected.
-
If the value of migrationcycle is cutovering, the value of copystate can be cutovering, deleting, stopping, error, stopped, or unconnected.
-
If the value of migrationcycle is cutovered, the value of copystate can be finished, deleting, stopping, error, stopped, or unconnected.
|
|
400 |
SMS.8101 |
Failed to stop the target server. |
Failed to stop the target server. |
Contact technical support. |
|
400 |
SMS.8102 |
The target server is missing. |
The target server is missing. |
Set the parameter for the target server. |
|
400 |
SMS.8103 |
The target server does not exist. |
The target server does not exist. |
Check whether the server has been deleted. |
|
400 |
SMS.8104 |
Failed to obtain details about the target server. |
Failed to obtain details about the target server. |
Contact technical support. |
|
400 |
SMS.8105 |
Failed to obtain the details about disks on the target server. |
Failed to obtain the details about disks on the target server. |
Contact technical support. |
|
400 |
SMS.8106 |
Invalid information about disks on the target server. |
Invalid information about disks on the target server. |
Check whether the target disk information is correct. |
|
400 |
SMS.8107 |
No agent image found on the target server. |
No agent image found on the target server. |
Check whether the image has been deleted. |
|
400 |
SMS.8108 |
Disk attachment failed. |
Disk attachment failed. |
Contact technical support. |
|
400 |
SMS.8109 |
No source server found. |
No source server found. |
Check whether the server record has been deleted. |
|
400 |
SMS.8110 |
Disk detachment failed. |
Disk detachment failed. |
Contact technical support. |
|
400 |
SMS.8111 |
No disk information found. |
No disk information found. |
Check whether the target disk information is correct. |
|
400 |
SMS.8112 |
No snapshot information found. |
No snapshot information found. |
Check whether the snapshot exists. |
|
400 |
SMS.8113 |
The snapshot does not exist. |
The snapshot does not exist. |
Check whether the snapshot has been deleted. |
|
400 |
SMS.8114 |
Failed to unlock the target server. |
Failed to unlock the target server. |
Check whether you have the permission to perform this operation. |
|
400 |
SMS.9001 |
Invalid parameters. |
Invalid parameters. |
Check whether the parameters are correctly specified. |
|
400 |
SMS.9002 |
User tags are not supported. |
User tags are not supported. |
User tags are not supported temporarily. |
|
400 |
SMS.9003 |
Insufficient permissions. |
Insufficient permissions. |
Obtain corresponding fine-grained permissions. |
|
400 |
SMS.9004 |
The current account does not have the permission to execute policy {0}. |
Insufficient permissions to perform {0}. |
Obtain corresponding fine-grained permissions. |
|
400 |
SMS.9005 |
Failed to bind the enterprise project. |
Failed to bind the enterprise project. |
Contact technical support. |
|
400 |
SMS.9905 |
Password query is not allowed on tasks in the current state. |
Password query is not supported for tasks in the current state. |
Query passwords only when the task is in a replicating or syncing state. |
|
403 |
SMS.6542 |
Your account has been frozen! |
Your account has been frozen. |
Contact technical support. |
