Error Codes

Status Code	Error Code	Error Message	Description	Solution
100	SMS.3105	fstab record "%s" is invalid	The fstab record %s is invalid.	Try the task again or contact technical support.
400	SMS.0007	Agent error.	The Agent program is abnormal.	Contact technical support.
400	SMS.0201	Network busy. Source server failed to connect to API Gateway.	The source server's network is busy, and the API gateway cannot be connected.	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/SK pair is correct.	Check whether you are using the correct AK/SK pair for the target platform account and whether the account is frozen.
400	SMS.0203	Connection from source server to API Gateway timed out.	The connection from source server to the 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 permissions.	Obtain the required permissions by referring to "Configuring Permissions" in the official documentation.
400	SMS.0205	AK/SK authentication failed. The time or time zone of the source server is incorrect.	AK/SK authentication failed. The time or time zone of the source server is incorrect.	Change the system time or time zone on the 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 drivers are not available on the source server.	Install the KVM drivers.
400	SMS.0208	Failed to send your service statement confirmation to SMS	Your service statement confirmation failed to be sent to SMS.	Check the network between the source server and the API gateway.
400	SMS.0210	Failed to create file %s on target server	File %s could not be created on the target server.	Check the network and restart the migration task.
400	SMS.0211	Failed to send certificate decryption key to target server	The certificate decryption key failed to be sent to the target server.	Check the network, restart the target server, and restart the migration task.
400	SMS.0212	Agent restarted. Delete the current target configuration and configure the target server again.	The Agent was restarted. Delete the current target server configuration and reconfigure the migration task.	Delete the target configuration and reconfigure the migration task.
400	SMS.0301	Failed to send the network request. Cause: %s	Failed to send the network request. Cause: %s	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 %s. Cause: %s	Unable to access domain name %s. Cause: %s	Check whether the domain name is reachable. If it is not, rectify the fault by referring to "SMS.0303 Unable to access domain name".
400	SMS.0304	Network request TLS/SSL authentication failed. Cause: %s	TLS/SSL authentication failed during the network request. Cause: %s	Rectify the fault by referring to "SMS.0304 SSL/TLS authentication failed."
400	SMS.0401	No project ID found. Cause: %s	Failed to obtain the project ID. Cause: %s	Contact technical support.
400	SMS.0406	No image found. Cause: %s	Failed to obtain the image. Cause %s.	Contact technical support.
400	SMS.0407	No target server information found. Cause: %s	Failed to obtain target server information. 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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the ECS documentation.
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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the ECS documentation.
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. Perform the migration again.
400	SMS.0412	Target server %s does not exist.	Target server %s does not exist.	The target server has been deleted. Perform the migration 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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the OBS documentation.
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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the ECS documentation.
400	SMS.0416	No VPC found. Cause: %s	No VPC found. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
400	SMS.0417	No security group found. Cause: %s	No security group found. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
400	SMS.0418	No subnet found. Cause: %s	No subnet found. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the ECS documentation.
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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the EVS documentation.
400	SMS.0421	Failed to obtain the domain ID. Cause: %s	Failed to obtain the domain ID. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the IAM documentation.
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.	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
400	SMS.0423	The VPC with the specified ID is abnormal.	The VPC with the specified ID is abnormal.	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
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.	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the EVS documentation.
400	SMS.0425	Failed to obtain the JSON configuration file.	Failed to obtain the JSON configuration file.	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	Obtain the required permissions based on the returned information or contact technical support.
400	SMS.0503	Log upload failed. Cause: %s	Log upload failed. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the OBS documentation.
400	SMS.0504	Failed to obtain task details. Cause: %s	Failed to obtain task details. Cause: %s	Start the task again or 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.	Create a migration task again.
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	Restart the task.
400	SMS.0509	The application failed to start because its side-by-side configuration is incorrect.	The application failed to start because its side-by-side configuration is incorrect.	Contact technical support.
400	SMS.0510	Failed to update the replication status to %s.	Failed to update the replication status to %s.	Restart the task.
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.	Restart the task.
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]}	Failed to update source server information. Cause: {0[0]}	Restart the task.
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 the 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 the target configuration, restart the Agent, and expand the target partition.
400	SMS.0520	Failed to obtain the target server password. Cause: %s	Failed to obtain the target server password. Cause: %s	Contact technical support.
400	SMS.0521	Failed to obtain the certificate password. Cause: %s	Failed to obtain the certificate password. Cause: %s	Check the network connection, restart the target server, and restart the migration task.
400	SMS.0522	The parameter contains invalid characters: %s	The parameter contains invalid characters: %s	Check whether the JSON body of the API call is correct.
400	SMS.0601	Target server creation failed. Cause: %s	Target server creation failed. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the ECS documentation.
400	SMS.0602	VPC creation failed. Cause: %s	VPC creation failed. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
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	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the VPC documentation.
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.	Check the destination region information.
400	SMS.0608	Volume creation failed. Cause: %s	Volume creation failed. Cause: %s	Locate the root cause based on the returned error details and rectify the fault by referring to "Error Codes" in the EVS documentation.
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.	Network error between source and target servers.	Check whether the network is functional.
400	SMS.0808	Failed to initialize sync task. Target disks or partitions not found.	Failed to initialize sync task. Target disks not found.	Contact technical support.
400	SMS.1101	Failed to start target server %s.	Failed to start target server %s.	Try again later. Check whether your account has the permission to stop the ECS.
400	SMS.1102	Failed to stop target server %s.	Failed to stop target server %s.	Try again later. Check whether your account has the permission to stop the ECS.
400	SMS.1103	Failed to attach disk %s. Cause: %s	Failed to attach disk %s. Cause: %s	Ensure that the network is connected and try again. If the fault persists, rectify the fault by referring to "Why Can't I Attach My Disk to a Server?" in the EVS documentation.
400	SMS.1104	Failed to detach disk %s. Cause: %s	Failed to detach disk %s. Cause: %s	Rectify the fault by referring to "SMS.1104 Failed to Detach Disk xxx" in the documentation.
400	SMS.1105	Disk creation failed. Cause: %s	Disk creation failed. Cause: %s	Rectify the fault by referring to "SMS.1105 Disk Creation Failed" in the documentation.
400	SMS.1106	Failed to delete disk %s. Cause: %s	Failed to delete disk %s. Cause: %s	Rectify the fault by referring to "SMS.1106 Failed to Delete Disk ***" in the documentation.
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	Ensure that the source server can access the target server through SSH and check whether the agent image version is correct.
400	SMS.1108	Failed to detach disk %s.	Failed to detach disk %s.	Refer to "SMS.1104 Failed to Detach disk xx" in the SMS documentation.
400	SMS.1109	An exception occurred when the private key and certificate were uploaded to target server %s.	An exception occurred when the private key and certificate were uploaded to target server %s.	Contact technical support.
400	SMS.1110	Failed to attach disk %s.	Failed to attach disk %s.	Contact technical support. Ensure stable network connectivity and retry the task. If the fault persists, rectify the fault by referring to "Why Can't I Attach My Disk to a Server?" in the EVS documentation.
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.	Rectify the fault be referring to "SMS.1113 Failed to Reconfigure Partition Details on the Target Server" in the documentation.
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	Wait and try again. If the issue persists, check whether the agent image version is correct.
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.	Wait and try again. If the issue persists, check whether the agent image version is correct.
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.	Failed to run the command on Windows. The cause is that the command or command parameter is empty.	Wait and try again. If the issue persists, check whether the agent image version is correct.
400	SMS.1201	%s not installed.	The specified service %s is not installed.	Contact technical support.
400	SMS.1202	Agent image ID is empty. Create agent image and reconfigure the task.	The agent image ID is empty. Create an agent image and perform the migration again.	Create an agent image according to the documentation and perform the migration again.
400	SMS.1203	Insufficient memory on the source server.	The source server memory is insufficient.	Close unneeded programs on the 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	Rectify the fault by referring to "SMS.1204 Failed to Create File on Source Server" in the documentation.
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.	Rectify the fault by referring to "SMS.1205 Failed to Load WMI" in the documentation.
400	SMS.1301	Failed to write partition information to the configuration file.	Failed to write partition information to the configuration file.	Ensure that the network connection is normal and try again.
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	Wait and try again. If the issue persists, check whether the agent image version is correct.
400	SMS.1313	Failed to create physical volume %s. Cause: %s	Failed to create physical volume %s. Cause: %s	Wait and try again. If the issue persists, check whether the agent image version is correct.
400	SMS.1314	Formatting failed. Partition: %s. Cause: %s	Formatting failed. Partition: %s. Cause: %s	Wait and try again. If the issue persists, check whether the agent image version is correct.
400	SMS.1315	Insufficient free space on target partition %s.	Insufficient free space on target partition %s.	Expand the partition.
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.	The SSH client is not installed. Install the openssh-clients package and check the installation with ssh -V.	Rectify the fault by referring to "SMS.1402 SSH client not installed" in the documentation.
400	SMS.1403	No grub file found. Find it under /boot.	The grub file could not be found. Search for the file in the /boot directory.	Contact technical support.
400	SMS.1404	Disk %s is abnormal. Expected status: %s	The disk %s status is abnormal. The current status is %s, and the expected status is %s.	Check the target disk status. If the status is expected, try the task again.
400	SMS.1405	Failed to obtain information about disk %s. Cause: %s	Failed to obtain information about disk %s. Cause: %s	The network fluctuates or the ECS API responds slowly. Ensure stable network connectivity, wait for a while, and try the task again. Check whether the target disk exists and whether the target server information in the task is correct. If the disk does not exist or the information is incorrect, correctly configure the target server and perform the migration again.
400	SMS.1406	Failed to obtain the EIP. Cause: %s	Failed to obtain the EIP. Cause: %s	Check whether the EIP status is normal and whether the EIP has been modified or deleted.
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	Failed to create a snapshot for disk %s. Cause %s.	Rectify the issue by referring to "SMS.1105 Disk creation failed" in the documentation.
400	SMS.1409	Failed to delete snapshot %s. Cause: %s	Failed to delete snapshot %s. Cause: %s	Ensure stable network connectivity and retry the task later. If the error persists, check whether the disk snapshot can be deleted based on the failure cause and whether the disk snapshot exists or has been deleted.
400	SMS.1410	Snapshot %s does not exist.	Snapshot %s does not exist.	Ensure stable network connectivity and retry the task later. If the error persists, check whether the snapshot has been deleted.
400	SMS.1411	Snapshot %s is in the %s state.	Snapshot %s is in the %s state.	Ensure stable network connectivity and retry the task later. If the error persists, check whether the snapshot status is normal.
400	SMS.1412	Snapshot %s rollback failed. Cause: %s	Snapshot %s rollback failed. Cause: %s	Ensure stable network connectivity and retry the task later. If the error persists, rectify the fault based on the returned error information or 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	Ensure stable network connectivity and retry the task later. If the error persists, rectify the fault based on the returned error information or contact technical support.
400	SMS.1414	The migration module stopped abnormally and cannot synchronize data.	The migration module stopped abnormally and cannot synchronize data.	Rectify the fault by referring to "SMS.1414 The migration module stops abnormally and cannot synchronize data" in the documentation.
400	SMS.1415	Failed to load the I/O monitoring module.	Failed to load the I/O monitoring module.	Rectify the issues by referring to "SMS.1902 Failed to Start the I/O Monitoring Module" in the documentation.
400	SMS.1416	Failed to create tag for server %s. Cause: %s	Failed to tag server %s. Cause: %s	Ensure stable network connectivity and retry the task later. If the error persists, rectify the fault based on the returned error information or contact technical support.
400	SMS.1417	Operation %s failed on server. Cause: %s	Failed to perform operation %s on the server. Cause: %s	Ensure stable network connectivity and retry the task later. If the error persists, rectify the fault based on the returned error information or contact technical support.
400	SMS.1423	Failed to obtain details about DNS server. Cause: %s	Failed to obtain the DNS server information. Cause: %s	Check the DNS configuration on the source server.
400	SMS.1501	OS version not supported.	The OS is not supported.	Check whether the source OS is supported based on the compatibility list.
400	SMS.1502	Target server %s is abnormal. Expected status: %s	The VM %s status is abnormal. The expected status is %s.	Check the status of the target server. If the status is expected, wait and try again.
400	SMS.1503	Disk %s is not the system boot disk.	Disk %s is not the system boot disk.	SMS considers the first disk as the system disk by default. Adjust the disk attachment order.
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.	Ensure that the disks on the source server match those on the target server.
400	SMS.1505	No boot partition found.	The boot partition was not found.	Check whether the system disk on the source server is correctly attached.
400	SMS.1506	No boot disk found.	The boot disk was not found.	Check whether the disks on the source server are correctly attached.
400	SMS.1507	No system partition found.	The system partition was not found.	Check whether the system partition on the source server is correctly mounted.
400	SMS.1508	Mount point, partition, or disk configured in disk.cfg not found.	The mount point, partition, or disk information written in the custom disk configuration file was not found.	Check the disk configuration file.
400	SMS.1509	Invalid disk.cfg file.	The custom disk configuration file is not feasible.	Check the disk configuration file.
400	SMS.1510	Configure advanced option %s failed. Cause: %s.	Failed to configure advanced option %s. Cause: %s	Check and modify the settings.
400	SMS.1511	Failed to check the consistency. Cause: %s	Failed to verify data consistency. Cause: %s	Reconfigure and execute the task, or 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.	The installed Agent cannot migrate the server to this region. Install the latest Agent.
400	SMS.1702	An error occurred when converting the string into the JSON format.	An error occurred during the conversion of the string to JSON.	Reconfigure and execute the task, or contact technical support.
400	SMS.1801	Migration or synchronization task failed.	The migration or synchronization failed.	Contact technical support.
400	SMS.1802	Migration or synchronization task paused.	The migration or synchronization task is suspended.	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.	Contact technical support.
400	SMS.1901	Agent could not read disk information.	The Agent could not read disk information.	Rectify the issue by referring to "SMS.1901 Agent could not read disk information" in the documentation.
400	SMS.1902	Failed to start the I/O monitoring module.	Failed to start the I/O monitoring module.	Rectify the issue by referring to "SMS.1902 Failed to start the I/O monitoring module" in the documentation.
400	SMS.1903	No valid block data found.	Failed to query valid block data.	Try the task again or contact technical support.
400	SMS.1904	Failed to create a snapshot for the Windows server.	Failed to create a snapshot for the Windows server.	Rectify the issue by referring to "SMS.1904 Failed to create a snapshot for the Windows server" in the documentation.
400	SMS.1905	Failed to read the disk information.	Failed to read the volume information.	Try the task again or contact technical support.
400	SMS.1907	Failed to send the migration command.	The Agent failed to send the command.	Try the task again or contact technical support.
400	SMS.1908	Data transmission failed.	The Agent failed to transmit data.	Try the task again or contact technical support.
400	SMS.1909	Data compression failed.	Data compression failed.	Try the task again or contact technical support.
400	SMS.1910	Failed to obtain the I/O monitoring data.	Failed to obtain the I/O monitoring data.	Try the task again or contact technical support.
400	SMS.1911	Boot sector read error.	Failed to read the boot sector.	Try the task again or contact technical support.
400	SMS.2003	Volume reconfiguration failed.	The volume reconfiguration failed.	Try the task again or 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.	Try the task again or 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.	1. Ensure that the disks on the target server are at least as large as those on the source server. If you expand the source server's disks or add new ones after the Agent is registered, register the Agent again and create a new migration task. 2. Out-of-bounds write may occur on the target server. Ensure that each disk on the target server is 1 GB larger than the paired disk on the source server.
400	SMS.2009	Data decompression failed.	Data decompression failed.	Try the task again or contact technical support.
400	SMS.2011	Failed to receive data.	Failed to receive data.	Try the task again or 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.	Try the task again or contact technical support.
400	SMS.2013	Failed to open the disk.	Failed to open the disk.	Try the task again or contact technical support.
400	SMS.2014	Failed to hide the partition information.	Failed to hide the partition information.	Try the task again or contact technical support.
400	SMS.2015	Failed to restore the partition information.	Failed to restore the partition information.	Try the task again or contact technical support.
400	SMS.2016	Drive letter restoration failed.	Drive letter restoration failed.	Try the task again or contact technical support.
400	SMS.2017	Failed to traverse all volumes.	Failed to traverse all volumes.	Try the task again or contact technical support.
400	SMS.2018	Error in reading the volume boot sector.	Failed to read the boot sector of the volume.	Try the task again or contact technical support.
400	SMS.2101	Registry modification failed.	Registry modification failed on Windows.	Try the task again or contact technical support.
400	SMS.2102	Failed to modify the device information.	Failed to modify the device information on Windows.	Try the task again or contact technical support.
400	SMS.2103	Failed to set active partitions.	Failed to set active partitions on Windows.	Try the task again or contact technical support.
400	SMS.2104	Failed to modify BCD configuration.	Failed to modify BCD configuration on Windows.	Try the task again or contact technical support.
400	SMS.2105	Failed to modify boot configuration file.	Failed to modify the boot configuration file on Windows.	Try the task again or contact technical support.
400	SMS.2201	Failed to clear disk information.	Failed to clear disk information during the partitioning and formatting on Windows.	Log in to the target server, run the diskpart clean command, and analyze the error cause based on the command output.
400	SMS.2202	Failed to convert the format of disk %s.	Failed to convert the format of disk %s during the partitioning and formatting on Windows.	1. Go to the config directory in the Agent installation directory on drive C. 2. Change the value of target.disk.pci.mapping in the g-property.cfg file in the directory to False. 3. Delete the disk_mapping.record file from the directory. 4. Delete the target configuration and reconfigure the migration task.
400	SMS.2203	Failed to create partition %s.	Failed to create partition %s during the partitioning and formatting on Windows.	You can try the following solutions: Restart the target server and retry the migration. Re-attach the faulty disk, log in to the target server, manually delete the faulty partition on the Disk Management page, and retry the migration.
400	SMS.2204	Failed to format partition %s.	Failed to format partition %s on Windows.	Try the task again or contact technical support.
400	SMS.2205	Failed to update the partition information.	Failed to update the partition information on Windows.	Try the task again or contact technical support.
400	SMS.2301	Failed to start ntcldst.	Failed to start ntcldst.	Try the task again or 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.	Rectify the issue by referring to "SMS.2802 Failed to Connect to the Target Server. Check Whether Its IP Address Is Reachable and Port 8899 Is Enabled" in the documentation.
400	SMS.3101	Failed to modify the configuration file of the target server. Cause: %s	Failed to modify the configuration file on the target server. Cause: %s	Create an ECS that uses the same or similar OS as the source server, overwrite the /etc/default/grub file on the target server with the content of the file on the ECS, and try the task again.
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	Try the task again or contact technical support.
400	SMS.3103	Failed to execute bootloader on the target server. Cause: %s	Failed to rebuild the bootloader on the target server. Cause: %s	The /usr/lib/grub/i386-pc directory does not exist on the source server. 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	Failed to read /etc/fstab on the source server. Restore the /etc/fstab file on the source server and try again.
400	SMS.3202	Failed to create volume group %s. Cause: %s	Failed to create volume group %s. Cause: %s	Try the task again or contact technical support.
400	SMS.3203	Failed to create logical volume %s. Cause: %s	Failed to create logical volume %s. Cause: %s	Try the task again or contact technical support.
400	SMS.3204	Failed to create swap partition %s. Cause: %s	Failed to create swap partition %s. Cause: %s	Try the task again or 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	Rectify the issue by referring to "SMS.3205 Failed to Mount Partition XXX to Directory XXX" in the documentation.
400	SMS.3206	Failed to obtain the UUID of the partition on the target server. Cause: %s	Failed to query the UUID of the partition on the target server. Cause: %s	1. Check whether the disk is correctly mounted. 2. Check whether the file system is supported for migration. 3. Retry the task or 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	Check whether the disk space is insufficient or 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	Check whether the disk space is insufficient or 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	Check whether the security group or firewall of the target server has restrictions.
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]}	Check whether the security group or firewall of the remote server has restrictions.
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	Failed to download RSA public and private keys. HTTPS Code: %s	Ensure stable network connectivity and retry the task, or contact technical support.
400	SMS.3402	Download of RSA public and private keys failed.	Failed to download the RSA public and private keys.	Ensure stable network connectivity and retry the task, or 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.	Rectify the issue by referring to "SMS.3802 Failed to establish an SSH connection with the target server" in the documentation.
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 due to an error occurred during the public key verification on the target server.	Rectify the issue by referring to "SMS.3803 The connection to the port 22 of target server failed, because an error occurred during the public key verification on the target server" in the documentation.
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 credentials.	Rectify the issue by referring to "SMS.3804 The connection to the port 22 of target server failed due to invalid connection credentials" in the documentation.
400	SMS.3805	The connection to the target server timed out.	The connection to the target server timed out.	Rectify the issue by referring to "SMS.3805 The connection to the port 22 of target server timed out" in the documentation.
400	SMS.3806	The connection to the target server was rejected.	The connection to the target server was rejected.	Rectify the issue by referring to "SMS.3806 The connection to the port 22 of target server was rejected" in the documentation.
400	SMS.3807	Failed to decompress %s.	Failed to decompress file %s.	Check whether the disk space is insufficient or contact technical support.
400	SMS.3808	Failed to ping the target server. Please check whether the ICMP port is enabled.	Failed to ping the target server. Check whether the ICMP port is enabled.	Ensure stable network connectivity and retry the task, or contact technical support.
400	SMS.3809	Failed to replace the RSA certificate on the target server.	Failed to replace the RSA certificate on the target server.	Ensure stable network connectivity and retry the task, or contact technical support.
400	SMS.5101	Agent installation failed.	Agent installation failed.	1. The Agent for Windows could not be launched by double-clicking. Right-click SMS-Agent-py*.exe and view the properties. Select Unlock. 2. The Agent installation failed because files failed to be written. Ensure that there is at least 500 MB of free space on drive C for installing the Agent. This requirement also applies to the Agent for Linux. Ensure that sufficient space is available for decompressing the Agent package to avoid errors during extraction.
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.	Rectify the issue by referring to "SMS.5102 Agent startup failed because the noexec permission is unavailable on /tmp in Linux" in the documentation.
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.	Check whether the /tmp folder exists. If it does not, create the folder. If it does, increase the size of the /tmp folder.
400	SMS.5104	Failed to paste AK or SK.	Failed to paste AK or SK.	Restart the Agent.
400	SMS.5105	Agent startup failed. Insufficient permissions to add files to or delete files from ~.	Agent startup failed. Insufficient permissions to add files to or delete files from the root directory.	Rectify the issue by referring to "Agent Startup Failed. Insufficient Permissions to Add Files to or Delete Files from root" in the documentation.
400	SMS.5106	Internal error. Failed to create a temporary directory.	Internal error. Failed to create a temporary directory.	Run the Agent as an administrator.
400	SMS.5107	Failed to open the file for writing.	The file to be written could not be opened.	Try the task again or contact technical support.
400	SMS.5108	Failed to execute df -TH.	Failed to execute df -TH.	Rectify the issue by referring to"SMS.5108 Failed to execute df -TH" in the documentation.
400	SMS.5109	The application cannot be started due to incorrect parallel configuration.	The application failed to start because its side-by-side configuration is incorrect.	Rectify the issue by referring to "SMS.5109 The application cannot be started due to incorrect parallel configuration" in the documentation.
400	SMS.5110	The Windows Agent unable to launch.	The Agent for Windows could not be launched by double-clicking.	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 were found with the same name.	Try the task again or contact technical support.
400	SMS.5112	Agent main program: linuxmain could not run.	The main program linuxmain of the Agent could not run.	For details, see "SMS.5112 Agent main program linuxmain could not run" in the documentation.
400	SMS.5113	Check %s on Linux timed out.	Checking %s on Linux timed out.	For details, see "SMS.5113 Checking %s on Linux timed out" in the documentation.
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 drivers.	Uninstall the Xen drivers and install the KVM drivers.
400	SMS.5401	Disks of the Windows target server are offline.	Disks of the Windows target server are offline.	This issue may be caused by the disk online policy. Contact technical support.
400	SMS.5402	Network error on the target server running Windows 2003.	Network error on the target server running Windows Server 2003.	Use another migration method.
400	SMS.5403	Progress is slow or suspended.	The migration progress is stuck or too slow.	For details, see "Why the Migration Progress Is Suspended or Slow?" in the documentation.
400	SMS.5404	The target server running CentOS 6.x cannot access the Internet.	After the CentOS 6.x migration is complete, the target server cannot connect to the Internet.	Check whether the dhclient command is missing in the system. If it is missing, the IP address cannot be dynamically obtained. In this case, configure a static IP address for the target server to enable Internet connectivity.
400	SMS.5601	The disk usage changes greatly after migration.	The disk usage changes greatly after migration.	Compare the source and target servers or contact technical support.
400	SMS.5602	Time error occurred in the target server running Linux.	The time of the Linux server is incorrect after migration.	Refer to "What Do I Do If the Linux Source Server's Clocks Are Not Synchronized to the Target Server?" in the documentation.
400	SMS.5603	The target server running Windows cannot access the Internet.	The Windows server cannot access the Internet after the migration.	Refer to "Why Can't a Windows Target Server Access the Internet After the Migration Is Complete?" in the documentation.
400	SMS.5604	The MySQL service on the target server cannot be started.	The MySQL service on the target server cannot be started.	Refer to "How Do I Troubleshoot a MySQL Startup Failure on the Target Server After the Migration?" in the documentation.
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.	Refer to "Why Is the System Recovery Options Window Displayed When the Target Server Is Started?" in the documentation.
400	SMS.5606	Windows fails to start because the Xen driver is abnormal.	The Windows system cannot be started because the Xen drivers are abnormal.	Delete the Xen drivers and synchronize data again.
400	SMS.6000	Service error.	Service error.	Contact technical support.
400	SMS.6001	The source server name is a required field.	The source name is empty.	The source server name must be specified.
400	SMS.6002	Source server name must consist of 1 to 64 characters.	A source server name can contain 1 to 64 characters.	A source server name can contain 1 to 64 characters.
400	SMS.6003	Only letters, digits, underscores (_), dot (.), and hyphens (-) are allowed.	Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed.	Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed.
400	SMS.6004	Invalid subtask name.	The subtask name is invalid.	Enter a valid subtask name.
400	SMS.6005	The status of the sourceServer does not meet the requirements.	The source server status is not expected.	Check the task status, restart SMS Agent, and restart the task.
400	SMS.6006	Source platform information format error.	The format of the source platform information is incorrect.	Restart the SMS Agent.
400	SMS.6010	The request body is not in the JSON format.	The request body is not in JSON format.	Set the request body as required.
400	SMS.6011	The JSON request body does not meet the specifications.	The JSON in the request body is invalid.	Set the request body as required.
400	SMS.6012	Empty request body.	The request body is empty.	Set the request body as required.
400	SMS.6013	Incomplete request parameters.	Request parameters are incomplete.	Add all required request parameters.
400	SMS.6014	The parameter part in the request body is too long.	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.	Ensure stable network connectivity and retry the task, or contact technical support.
400	SMS.6021	The command from the Agent is inconsistent with that from SMS.	The command provided by the client is inconsistent with that on the server.	Enter the command from the server correctly.
400	SMS.6022	Incorrect result format.	The format of "result" is incorrect.	Set "result" in the correct format.
400	SMS.6023	Incorrect result_detail format.	The format of "result_detail" is incorrect.	Set "result_detail" in the correct format.
400	SMS.6030	Invalid source server ID.	The source server ID is invalid.	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 parameter "vm_id" is missing from the target server parameters.	Add the target server ID.
400	SMS.6033	The disk information is missing.	The disk information is missing from the target server parameters.	Add disk information of the target server.
400	SMS.6034	Invalid region name.	The region name is invalid.	Enter a valid region name.
400	SMS.6035	Domain ID is missing.	The request body does not contain a domain ID.	Add a domain ID.
400	SMS.6101	Invalid migration progress.	The migration progress is out of range.	Enter an integer 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 requirements are met.
400	SMS.6103	Disk ID is missing.	The disk ID is missing.	Enter a disk ID.
400	SMS.6104	Physical volume name is missing.	The volume name is missing.	Enter a volume name.
400	SMS.6105	Physical volume size is missing or invalid.	The volume size information is missing or invalid.	Enter a valid volume size.
400	SMS.6106	Failed to obtain migration progress.	Failed to obtain migration progress.	Ensure stable network connectivity and retry the task, or contact technical support.
400	SMS.6301	Database read or write error.	Database read or write error.	An exception occurred during network request parameter verification. Keep the network connection normal and retry the task, or contact technical support.
400	SMS.6302	No migration speed limit found.	No rate limiting information related the task was found.	Reset the rate limit.
400	SMS.6303	The installed Agent is of an earlier version. Download the latest version.	The Agent version is too early. Download the latest Agent.	Download the latest Agent.
400	SMS.6304	Fail to get config information.	Obtaining the configuration information failed.	Ensure stable network connectivity and retry the task, or contact technical support.
400	SMS.6401	Unsupported encoding mode.	The encoding mode is not supported.	Use a correct encoding mode.
400	SMS.6402	The algorithm does not exist.	The algorithm does not exist.	Ensure that the parameters for accessing the API are correct.
400	SMS.6403	Failed to split into strings of the specified size.	The string cannot be evenly divided into the specified length.	Internal server error. Contact technical support.
400	SMS.6404	An error occurred during integer conversion.	An error occurred during integer conversion.	An exception occurred during network request parameter verification. Keep the network connection normal and retry the task, or 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.	The quota is insufficient. 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.	Try the task again or contact technical support.
400	SMS.6503	Failed to obtain the OS version of the source server.	The source server OS version cannot be obtained.	Provide a correct source OS type.
400	SMS.6504	Unsupported source server OS version or firmware type.	The source server OS version or firmware type is not supported.	Check the compatibility list.
400	SMS.6505	Unknown source firmware type. It must be BIOS or UEFI.	The source server firmware failed the check. 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.	Failed to obtain the number of CPUs. Restart the SMS Agent or contact technical support.
400	SMS.6507	Failed to open the system directory of the source server.	Failed to open the system directory.	Try the task again or contact technical support.
400	SMS.6508	Incompatible disk format on the source server. Only GPT and MBR are compatible.	The disk format on the source server is not supported. Only GPT and MBR are supported.	Use another migration method.
400	SMS.6509	Incompatible file system of the source server.	File systems on the source server are not supported.	Use another migration method.
400	SMS.6510	The source server OS is an OEM system.	The source server OS is an OEM system.	You need to activate the system after migration.
400	SMS.6511	The source server lacks driver files.	The source end lacks necessary driver files.	Refer to "SMS.6511 The source server lacks driver files" in the documentation.
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 are not running properly.	Try the task again or contact technical support.
400	SMS.6513	No administrator permissions on the source server.	Administrator permissions are not granted.	Check whether the current account on the source server has the administrator permissions.
400	SMS.6514	Failed to obtain the memory size of the source server.	The memory size could not be obtained.	Restart the SMS Agent or contact technical support.
400	SMS.6515	The source server is paravirtualized.	Paravirtualized source servers are not supported.	Use another migration method.
400	SMS.6516	The Linux bootloader must be GRUB.	Only Linux servers using GRUB are supported.	Check whether the Linux boot mode is GRUB.
400	SMS.6517	rsync not installed on the source server.	rsync is not installed on the source server.	Install rsync on the source server.
400	SMS.6518	The source server has a raw device.	Raw devices are not supported.	Use another migration method.
400	SMS.6519	Failed to obtain disk information.	No disk information is available.	Restart the SMS Agent or contact technical support.
400	SMS.6520	The source server is not in the AVAILABLE state.	The source server is not available.	Check the source server status.
400	SMS.6521	Token-based authentication failed.	Token authentication failed.	Use the correct token.
400	SMS.6522	The X-Auth-Token header field is missing.	X-Auth-Token was not found in the request header.	Add X-Auth-Token to the request header.
400	SMS.6523	Apply for the permission required to operate SMS.	You do not have the permission to use SMS.	Ensure that you have the sms_administrator permissions.
400	SMS.6524	This operation is not allowed because you are not an OBT user.	This operation is restricted to OBT users.	Apply for the OBT.
400	SMS.6525	Account is frozen or restricted. Check account balance and status.	The account or resource is frozen or restricted. Check the account balance and status.	Ensure that the account status is normal and the account balance is sufficient.
400	SMS.6526	Insufficient quota to clone the target server.	The available quota is insufficient to complete the target server cloning operation.	Increase the cloud server quota.
400	SMS.6527	The resource in the task does not belong to you.	The current resource does not belong to the current user.	Check the resources of the current user.
400	SMS.6528	Complete real-name authentication to invoke the SMS APIs.	Users who have not completed real-name authentication cannot call SMS APIs.	Complete real-name authentication first.
400	SMS.6529	Only accounts with sufficient balance and does not have security risks can invoke the SMS APIs.	Accounts in arrears, with an insufficient balance, or with security risks cannot invoke the SMS APIs.	Ensure that the account status is normal and the account balance is sufficient.
400	SMS.6530	Invalid source server IP address.	The source server's IP address is invalid.	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 was not found on the source server.	Check whether VSS has been installed and started.
400	SMS.6534	No system directory information read.	The system directory information is empty.	Restart the SMS Agent or contact technical support.
400	SMS.6535	Servers booted with UEFI do not support auto-creation of target servers for migration.	Automatic creation of target servers is not supported for source servers booted with UEFI.	Create a target server booted with UEFI manually and use it as the target server.
400	SMS.6536	The source server runs Windows 2003. Network may be unavailable after migration.	The source server runs Windows Server 2003. It may experience network exceptions after migration.	Upgrade the system and perform the migration.
400	SMS.6537	SMS cannot migrate system disks larger than 1 TB.	The system disk is larger than 1 TB.	Downsize 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.6539	The disk space is less than the total size of all partitions.	The disk space is less than the total size of all partitions.	The disk space is less than the total size of all partitions.
400	SMS.6540	Partitions on target servers running Windows cannot be reduced.	Partitions on Windows target servers cannot be downsized.	Resize the disks and partitions on the source server and restart the Agent
400	SMS.6541	The VG size is smaller than the combined size of all LVs.	The size of the volume group is smaller than the total size of all logical volumes.	Downsize logical volumes or contact technical support.
400	SMS.6542	Your account has been frozen.	Your account has been frozen.	Unfreeze your account.
400	SMS.6543	There is more than 1 TB of data to be migrated. It may slow down the migration or synchronization.	The total amount of data to be migrated exceeds 1 TB. The migration and synchronization may be slow.	Continue the migration after confirming risks.
400	SMS.6544	Network condition for migration is poor.	The migration network is in poor conditions.	Continue the migration after confirming risks.
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.	The token is called unexpectedly and may pose security risks. 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 an UEFI image.
400	SMS.6562	Failed to obtain target server IP address.	Failed to obtain target server IP address.	Refer to "SMS.6564: Component i386-pc not found on source server. For solution, see SMS API Reference." in the documentation.
400	SMS.6601	Invalid OS type.	Invalid OS type.	Set "os_type" by referring to the 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.	Network request error. Retry the task later or contact technical support.
400	SMS.6605	ACL or security group configuration error.	The ACL or security group settings are incorrect.	Modify the ACL or security group settings.
400	SMS.6610	The OS in the task conflicts with the source server OS.	The task type does not match the source server OS.	Check whether the task type matches 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 1 MB.	Enter a valid partition size.
400	SMS.6613	33 MB of space must be reserved for GPT disks.	33 MB space must be reserved for disks in GPT format.	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 used in a migration task.	Change another server.
400	SMS.6616	The current OS does not support block-level migration.	Block-level migration is not supported for the current OS release.	Use another migration method.
400	SMS.6617	The current kernel does not support block-level migration.	Block-level migration is not supported for the current kernel release.	Use another migration method.
400	SMS.6618	Failed to obtain kernel details.	Failed to obtain kernel details.	Try the task again or contact technical support.
400	SMS.6619	Disk encryption key not available.	The disk encryption key is unavailable.	Check whether the key status is normal and ensure that the AES_256 encryption algorithm is used.
400	SMS.6620	Key %d is not enabled.	Key %d is not enabled.	Check the key status.
400	SMS.7101	Template does not exist.	The 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.7113	Maximum templates reached.	The maximum number of templates is reached.	Go to the SMS console and delete unneeded migration templates.
400	SMS.7301	The specified migration template does not exist.	The specified migration template does not exist.	Check whether the migration template exists.
400	SMS.7303	The default migration template cannot be deleted.	The default project cannot be deleted.	The specified migration template does not exist. Check whether the migration template exists.
400	SMS.7304	The default migration template does not exist.	The default migration template does not exist.	Create a migration template and set it as the default one.
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.	The specified migration template already exists. Use another template.
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.	Try the task again or contact technical support.
400	SMS.7501	No application ID generated.	Failed to generate the application ID.	Try the task again or contact technical support.
400	SMS.7601	Failed to delete the source server because a migration task is running on it.	There is a task on the source server, and the server cannot be deleted.	Try the task again or 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.	Restart the SMS Agent or contact technical support.
400	SMS.7605	The server has been set as the target server of another migration task. Select another server or delete the task associated with the server.	The server has been set as the target server in another migration task. Select another server or delete the migration task associated with the server.	Select another server or delete the migration task associated with the server.
400	SMS.7606	No migration task running on the source server.	No migration task runs on the source server.	The migration task was deleted unexpectedly. Restart the Agent on the source server and reconfigure the migration task.
400	SMS.7703	Task does not exist.	The 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 during JSON file processing for task creation.	The network request parameters are incorrect. Keep the network connection normal and retry the task, or contact technical support.
400	SMS.7706	Task update failed.	Task update failed.	Network request error. Retry the task or contact technical support.
400	SMS.7707	The current Agent version does not support log upload.	The Agent version does not support log upload.	Ensure that the Agent version is 25.2.0 or later.
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 launched.	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 launched can be restarted.	Check whether the target server for the task has been launched 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.	An exception occurred during the verification of task parameters. Restart the Agent on the source server and reconfigure the migration task, or contact technical support.
400	SMS.7725	No region information found.	No region information found.	Try the task again or 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 for the source server. The request body lacks the "copystate" or "migrationcycle" field.	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 for 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.	Set copystate 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.	Try the task again or contact technical support.
400	SMS.8102	The target server is missing.	The target server is missing from the SMS task.	Set target server parameters.
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.	Check whether the target server was deleted. If it was not, 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.	Check whether disks are attached to the target server. If yes, 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.	Network request error. Retry the task or contact technical support.
400	SMS.8109	No source server found.	Source server not found.	Check whether the server record has been deleted.
400	SMS.8110	Disk detachment failed.	Disk detachment failed.	Network request error. Retry the task or 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 permissions to perform this operation.
400	SMS.8115	Maximum templates: 50	A maximum of 50 templates can be created.	Go to the SMS console, delete unneeded migration templates, and try again.
400	SMS.9001	Invalid parameters.	Invalid parameters.	Check whether the parameters are correct.
400	SMS.9002	User tags are not supported.	User tags are not supported.	User tags are not supported.
400	SMS.9003	Insufficient permissions.	Insufficient permissions.	Obtain the required permissions.
400	SMS.9004	The current account does not have the permission to execute policy {0}.	Insufficient permissions to perform {}.	Obtain the required permissions.
400	SMS.9005	Failed to bind the enterprise project.	Failed to bind the enterprise project.	Check whether the enterprise project exists and retry the task, or 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.