Error Codes and Solutions
Error Codes for Server Migration Workflows
| Error Code | Description | Solution |
|---|---|---|
| SMS-Workflow.0101 | Parameter * is empty. | Check whether any recommended server parameters (image and disk) are missing, or contact MgC technical support to check whether parameter *** is empty in the workflow database. |
| SMS-Workflow.0102 | Parameter *** contains special characters. | Contact MgC technical support to check whether parameter *** contains special characters in the workflow database. |
| SMS-Workflow.0103 | PowerShell version must be 3.0 or later. | Open PowerShell on the server where the MgC Agent (formerly Edge) is installed and run the $host command to check the PowerShell version. If the current version is earlier than 3.0, you are advised to reinstall the MgC Agent on a server running Windows Server 2012 or later. Generally, Windows Server 2012 and later versions provide PowerShell 3.0 or later. |
| SMS-Workflow.0201 | Available memory on the Windows source server is less than 256 MB. | Run the systeminfo command in the CLI window to check available memory, release sufficient memory, and try again. |
| SMS-Workflow.0202 | Linux source servers failed the migration feasibility check. | Find the solution based on the error code in SMS documentation or contact SMS technical support.
|
| SMS-Workflow.0203 | A migration program is running on a source server. |
|
| SMS-Workflow.0301 | Create VM failed. | Common causes include insufficient quotas and recommended images or flavors that do not meet requirements. Locate the fault based on the error message or ECS error code. |
| SMS-Workflow.0302 | The target VM is abnormal. | Check whether the associated target ECS is, for example, locked or frozen. |
| SMS-Workflow.0303 | Disks not found on target VM. | Check whether the target VM has disks attached. If no, attach disks and try again. |
| SMS-Workflow.0304 | System disk not found on target VM. | Check whether the target VM has a system disk attached. If no, attach one and try again. |
| SMS-Workflow.0305 | Obtain IP address of target VM failed. | If you are migrating over a public network, check whether there is an EIP bound to the target VM. If there is no EIP bound, bind one and try again. |
| SMS-Workflow.0306 | Target server does not have the same number of disks as source server. | The target server has fewer disks than the source server. Attach disks as large as the source ones to the target server. Then try again. |
| SMS-Workflow.0307 | Target server has disks smaller than source server. | The xth disk (* GB) of the target server is smaller than the paired one (* GB) of the source server. Adjust the disk size of the target disk and try again. |
| SMS-Workflow.0308 | Insufficient ECS quota. Requested: x; Available: y | Release unnecessary ECSs or submit a service ticket to increase the quota. |
| SMS-Workflow.0309 | Insufficient CPU quota. Requested: x; Available: y | Release unnecessary resources or submit a service ticket to increase the quota. |
| SMS-Workflow.0310 | Insufficient memory quota. Requested: x MB; Available: y MB | Release unnecessary resources or submit a service ticket to increase the quota. |
| SMS-Workflow.0311 | The disk type of the target server is missing. Check the disk type recommended on the "Migration Solutions" page. | Check whether the recommended target disk type is empty. If it is, assess the source server again and retry the workflow. |
| SMS-Workflow.0312 | The disk size of the target server is missing. Check the disk size recommended on the "Migration Solutions" page. | Check whether the recommended target disk size is empty. If it is, assess the source server again and retry the workflow. |
| SMS-Workflow.0313 | Invalid source disk IDs used for generating target recommendations. Assess the source server again. | Assess the source server and try the workflow step again. This is because if a source server is collected twice, new disk IDs are generated for it. Assess the source server and try the workflow step again. |
| SMS-Workflow.0314 | Firmware inconsistency between source and target servers. | The firmware type of the target server must be the same as that of the source server. Reconfigure the firmware type of the target server and try again. |
| SMS-Workflow.0315 | Failed to obtain target image ID. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0316 | Insufficient EIP quota. | Increase the EIP quota of the account and try again. |
| SMS-Workflow.0317 | Insufficient ECS quota. | Increase the server quota for your account and try again. |
| SMS-Workflow.0318 | Insufficient vCPU quota. | Increase the vCPU quota for your account and try again. |
| SMS-Workflow.0319 | Insufficient memory quota. | Increase the memory quota for your account and try again. |
| SMS-Workflow.0321 | Flavor {} unavailable. | Try again. If the fault persists, delete the workflow and use another target flavor. You can also contact technical support or submit a service ticket. |
| SMS-Workflow.0401 | Download SMS-Agent installation package to source server failed. | Download the SMS-Agent from the SMS console, and check the error message displayed during the download. Possible causes include network disconnection, download command exception, or insufficient disk space. |
| SMS-Workflow.0402 | Decompress SMS-Agent installation package failed on the source server. | One possible cause is that the tar command fails to be executed. Go to the /edge/ directory on the source server and run the tar -zxvf SMS-Agent.tar.gz command to view the error details. |
| SMS-Workflow.0403 | Install SMS-Agent on Windows failed. | Check whether the SMSAgentDeploy.exe file is in the C:\SMS-Agent-Py2\ directory on the source server. If it is not there, delete the SMS-Agent-Py2 folder and double-click the installation package with the same name in drive C. |
| SMS-Workflow.0404 | Start SMS-Agent failed. |
If the fault persists, contact SMS technical support to view the migration logs. |
| SMS-Workflow.0405 | Obtain cloud-region.json failed. | Log in to the source server and view the error information in the SMS run logs located in:
If the fault cannot be located, contact SMS technical support to view the migration logs. |
| SMS-Workflow.0406 | Failed to verify SMS-Agent version. | If you use an ECS agency to log in to the MgC Agent, check whether the source SMS-Agent version is earlier than 25.2.0. If it is, suspend and delete the existing workflow, create a workflow, and migrate the data again. Alternatively, use a key pair to log in to the MgC Agent for migration. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0407 | Clear the source SMS-Agent failed. |
|
| SMS-Workflow.0501 | Could not find the migration task on the SMS console. | Go to the SMS console and check whether the migration task has been deleted. If the migration task has been deleted by mistake, create a migration workflow again on the MgC console. |
| SMS-Workflow.0502 | The source server is disconnected from the SMS server. | Log in to the SMS console and check whether the migration task is in the Disconnected status. If it is, rectify the fault by referring to How Do I Restore the Connection Between the Agent and SMS? If the connection to MgC is set up through federated authentication, check whether the temporary access key for Huawei Cloud has expired on the MgC Agent console.
|
| SMS-Workflow.0503 | Migration task failed. SMS.xxxx | Read the error message and select a troubleshooting method accordingly.
If the error information does not contain the preceding error code, try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0504 | The migration task is paused or being paused. | Retry this step to continue the migration. |
| SMS-Workflow.0505 | Obtain source server information failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0506 | Obtain migration task information failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0507 | Issue migration command failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0508 | The current migration task is empty. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0509 | Delete SMS migration task failed. | Go to the SMS console and manually delete the task. After the deletion is complete, return to the MgC console and try again. NOTICE: Only tasks in the paused, completed, or error state can be deleted. |
| SMS-Workflow.0510 | Query migration progress failed. | Try again. |
| SMS-Workflow.0511 | The target configuration already exists in the server migration task. Delete it manually on the SMS console. | Go to the SMS console and manually delete the target configuration. After the deletion is complete, return to the MgC console and try again. NOTICE: Only tasks in the paused, completed, or error state can be deleted. |
| SMS-Workflow.0512 | Failed to delete the target configuration. Delete it manually on the SMS console. | Go to the SMS console and manually delete the target configuration. After the deletion is complete, return to the MgC console and try again. NOTICE: Only tasks in the paused, completed, or error state can be deleted. |
| SMS-Workflow.0513 | Incorrect transit IP address. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0514 | Invalid configuration of whether to install the password reset plug-in. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0003 | Input parameters are not in the standard JSON format. | Contact technical support or submit a service ticket to check whether the input parameters in this step are correct. |
| SMS-Workflow.0902 | Stopping server timed out. Try again or manually stop the server and try again. | Go to the ECS console, manually stop the server, and retry the workflow. If the fault persists, contact technical support or submit a service ticket. |
| SMS-Workflow.0901 | Failed to shut down servers in the *** status. Manually shut down the servers and try again. | Go to the ECS console, manually stop the servers, and retry the workflow. |
| SMS-Workflow.1204 | Change the IP address of server *** failed. Failure cause: *** |
|
| Server-Workflow.0001 | Workflow step *** not found. | Contact technical support or submit a service ticket. |
| Server-Workflow.0002 | Workflow lacks parameter ***. | Contact technical support or submit a service ticket. |
| Server-Workflow.0003 | Workflow parameter *** contains special characters. | Contact technical support or submit a service ticket. |
| Server-Workflow.0004 | Network error ***. Please try again. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| Server-Workflow.0005 | Missing region parameter. | Contact technical support or submit a service ticket. |
| Server-Workflow.0006 | Pre-migration verification failed. | Contact technical support or submit a service ticket. |
| Server-Workflow.0007 | An unknown error occurred during the migration. | Contact technical support or submit a service ticket. |
| Server-Workflow.0008 | Unknown error. | Contact technical support or submit a service ticket. |
| Server-Workflow.0009 | Clearing resources failed. | Access the CBR and IMS consoles, manually delete the temporary resources (whose names start with AZM_Create_Temp__xxx), and retry the workflow task. |
| Server-Workflow.0010 | Request *** failed. Failure cause: ***. Try again. | Try again. You can also rectify the fault by referring to "SMS.xxxx Error Codes" or "Error Codes for Other Cloud Services." If the fault persists, contact technical support or submit a service ticket. |
| Server-Workflow.0011 | Query *** progress failed. Failure cause: *** | Contact technical support or submit a service ticket. |
| Server-Workflow.0012 | Step *** is an instant action | Contact technical support or submit a service ticket. |
| Server-Workflow.0013 | Verify template version failed. | Contact technical support or submit a service ticket. |
| MgC.00000305 | SMS response exception. Failure cause: *** | SMS response exception. Locate the fault and handle the error by referring to Error Codes. |
| MgC.00000308 | Parse SMS response failed: Unexpected data format. | Failed to parse the SMS response because the returned data is not as expected. Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000301 | Obtain device version info failed. | Check whether IoTDA can be accessed.
|
| MgC.00020287 | Firmware mismatch between selected image and source server. Select another image. | Select an image that matches the source firmware type. |
| MgC.00020288 | Target system disk smaller than the minimum required by selected image. Configure a larger system disk or select an image with lower storage demands. | Select an image with lower capacity requirements or expand the system disk of the target server to meet the minimum image requirements. |
| MgC.00020289 | Insufficient flavor memory to meet image requirements. | Select a proper target server flavor. |
| MgC.00020296 | Source disk not found on the source server. | Check the source server's readiness again, or re-collect its resources in depth. Then, configure the target server. |
| MgC.00030206 | MgC Agent currently down. | Perform the following operations:
|
| MgC.00030147 | Workflow not found. | Check whether the workflow has been deleted. |
| SERVER.00010001 | Connection timed out. | Use the correct IP address and network. |
| SERVER.00010007 | Workflow script execution failed. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| SERVER.00010004 | Failed to create a script folder using the SFTP service. |
Possible causes are:
|
| SERVER.00010006 | Insufficient permission to push Linux scripts. | Check whether the credential bound to the source server is the root account and password. Obtain them on the credential management page on the MgC Agent console.
|
Error Codes for Cross-AZ Migration Workflows
| Error Code | Description | Solution |
|---|---|---|
| AZ-Workflow.0001 | Workflow step *** not found. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0002 | Workflow lacks parameter ***. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0003 | Workflow parameter *** contains special characters. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0004 | Network error ***. Please try again. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| AZ-Workflow.0005 | The Region parameter is empty. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0006 | Pre-migration verification failed. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0007 | An unknown error occurred during the migration. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0008 | Unknown error. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0009 | Clearing resources failed. | Access the CBR and IMS consoles, manually delete the temporary resources (whose names start with AZM_Create_Temp__xxx), and retry the workflow task. |
| AZ-Workflow.0010 | Request *** failed. Failure cause: ***. Try again. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| AZ-Workflow.0011 | Query *** progress failed. Failure cause: *** | Contact technical support or submit a service ticket. |
| AZ-Workflow.0012 | Step *** is an instant action | Contact technical support or submit a service ticket. |
| AZ-Workflow.0101 | Source server *** not found. | Check whether the server ID is the source server ID and whether the source server can be found. |
| AZ-Workflow.0102 | Source server *** is not ready for migration. | Check whether the source server is normal. If it is abnormal, contact ECS technical support. |
| AZ-Workflow.0202 | AZ *** does not exist. | Delete the migration workflow, create a cross-AZ migration application, and select an available AZ. |
| AZ-Workflow.0201 | AZ *** is unavailable. | Delete the migration workflow, create a cross-AZ migration application, and select another AZ. |
| AZ-Workflow.0301 | Insufficient quotas. | Increase quotas and try again. |
| AZ-Workflow.0302 | Insufficient ECS quota. | Increase the ECS quota and try again. |
| AZ-Workflow.0303 | Insufficient vCPU quota. | Increase the vCPU quota and try again. |
| AZ-Workflow.0304 | Insufficient memory quota. | Increase the memory quota and try again. |
| AZ-Workflow.0401 | Flavor *** is unavailable. | Delete the migration workflow, modify the recommended server specifications, and create a new workflow. |
| AZ-Workflow.0402 | Disk type *** is not available in AZ ***. | Delete the migration workflow, modify the recommended disk specifications, and create a new workflow. |
| AZ-Workflow.0403 | Disk type *** is sold out in AZ ***. | Delete the migration workflow, modify the recommended disk specifications, and create a new workflow. |
| AZ-Workflow.0404 | The source server has *** NICs. Flavor *** supports a maximum of *** NICs. Select another flavor. | Delete the migration workflow, modify the recommended disk specifications, and create a new workflow. |
| AZ-Workflow.0405 | Parse disk information failed. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0406 | The disk_infos parameter is empty. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0501 | Create backups failed. Failure cause: *** | Rectify the fault based on the error message. Go to the CBR console to check whether backups are created. |
| AZ-Workflow.0502 | Unable to associate source server *** with vault ***. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0503 | Vault *** is unavailable. | Delete the vault and try again. |
| AZ-Workflow.0901 | Failed to shut down servers in the *** status. Manually shut down the server and try again. | Go to the ECS console, manually stop the server, and retry the workflow. |
| AZ-Workflow.0902 | Stopping server timed out. Try again or manually stop the server and try again. | Go to the ECS console, manually stop the server, and retry the workflow. |
| AZ-Workflow.0601 | Create incremental backups failed. Failure cause: *** | Rectify the fault based on the error message, contact technical support, or submit a service ticket. |
| AZ-Workflow.0701 | Create full-ECS image failed. Failure cause: *** | Rectify the fault based on the error message, contact technical support, or submit a service ticket. |
| AZ-Workflow.0801 | Create target server failed. Failure cause: *** | Rectify the fault based on the error message, contact technical support, or submit a service ticket. |
| AZ-Workflow.0802 | Servers with system disks larger than 1 TB cannot be migrated. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0803 | Invalid size of disk ***. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0804 | Source server *** not found in VPC ***. | Contact technical support or submit a service ticket. |
| AZ-Workflow.0805 | Image *** is not found or unavailable. | Go to the IMS console to check the image status and contact IMS support to confirm whether the image can be restored automatically. If it cannot, contact technical support or submit a service ticket. |
| AZ-Workflow.0901 | Servers in the *** status cannot be stopped. Manually shut down servers and try again. | Go to the ECS console, manually stop the server, and retry the workflow. |
| AZ-Workflow.0902 | Stopping server timed out. Try again or manually stop the server and try again. | Go to the ECS console, manually stop the server, and retry the workflow. |
| AZ-Workflow.1001 | Delete full-ECS images failed. Failure cause: *** | Access the IMS console, manually delete these images (whose names start with AZM_Create_Temp__xxx), and retry the workflow task. |
| AZ-Workflow.1002 | Delete backups failed. Failure cause: *** | Access the CBR console, manually delete the server backups (whose names start with AZM_Create_Temp__xxx), and retry the workflow task. |
| AZ-Workflow.1003 | Delete vault *** failed. Failure cause: *** | Access the CBR console, manually delete the vault (whose name starts with AZM_Create_Temp__xxx), and retry the workflow task. |
| AZ-Workflow.1101 | The server_id parameter is empty. | Contact technical support or submit a service ticket. |
| AZ-Workflow.1102 | Create system disk images failed. IMS error code: ***, error message: *** | Retry the task again or contact the IMS support. |
| AZ-Workflow.1201 | Target server has an EIP bound. Unbound the EIP and try again. | Check whether the target server has an EIP bound and whether the EIP is one bound to the source server. If it is not, unbind the EIP from the target server. |
| AZ-Workflow.1202 | Source server *** is not stopped. Manually stop it and try again. | Check whether the source server is stopped. If it is not, stop it and try again. |
| AZ-Workflow.1203 | Target server *** is not stopped. Manually stop it and try again. | Check whether the target server is stopped. If it is not, stop it and try again. |
| AZ-Workflow.1204 | Change the IP address of server *** failed. Failure cause: *** | Rectify the fault based on the error message, contact technical support, or submit a service ticket. |
Error Codes for Object Storage Migration Workflows
| Error Code | Description | Solution |
|---|---|---|
| OMS-Workflow.0002 | Unknown OMS error. | Contact technical support or submit a service ticket. |
| OMS-Workflow.0011 | System error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS-Workflow.0013 | Invalid request parameters. | Rectify the fault based on the error message. For example: If the error message is "The maxSubtaskNum more than node * 10," add migration nodes to the migration cluster and try again. |
| OMS-Workflow.0018 | The project ID is different from that in the token. | Check whether the right project ID or token is used. |
| OMS-Workflow.0019 | The region in the token is different from the region where the migration cluster is located. | Use the token of the region where the migration cluster is located. |
| OMS-Workflow.0023 | Abnormal node. | Check whether the required ports are allowed by the security group rules of the cluster node. For details about the requirements, see: |
| OMS-Workflow.0024 | Cluster not found. | Check whether the cluster can be found in the cluster list. |
| OMS-Workflow.0025 | Node not found. | Check whether the node exists in the corresponding cluster. |
| OMS-Workflow.0026 | Task not found. | Check whether the task exists in the task list. |
| OMS-Workflow.0027 | Deliver task failed. | The task cannot be synchronized to the cluster. Create another one. |
| OMS-Workflow.0201 | Create cluster failed. | Rectify the fault based on the keywords in ErrorReason. This error is usually caused by insufficient resources or permission issues. ECS Error Codes, VPC Error Codes, NAT Gateway Error Codes, VPCEP Error Codes, and LTS Error Codes |
| OMS-Workflow.0202 | Failed to query the workflow creation details. | Rectify the fault based on the keywords in ErrorReason. This error is usually caused by insufficient resources or permission issues. ECS Error Codes, VPC Error Codes, NAT Gateway Error Codes, VPCEP Error Codes, and LTS Error Codes |
| OMS-Workflow.0501 | Failed to query the cluster deletion details. | Rectify the fault based on the keywords in ErrorReason. Generally, the fault is caused by the failure to clear some resources due to permission issues. ECS Error Codes, VPC Error Codes, NAT Gateway Error Codes, VPCEP Error Codes, and LTS Error Codes |
| OMS-Workflow.0401 | Migration task execution failed. Some objects might fail to be migrated. | If the error message is "Migration failed. Failure files exist," Rectify the fault by referring to Viewing the List of Failed Objects. |
| OMS-Workflow.0402 | Connect to the tenant cluster failed. | Ensure that the tenant cluster is running properly and the network connection is normal. |
| OMS-Workflow.0601 | Delete task failed. | Rectify the fault based on the cause. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01001 | Local data write failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01002 | An exception occurred when local data uploaded to an external storage device. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01003 | Source unavailable. | Check the source connection parameters. |
| OMS.01006 | Object list files too large. | Make sure that each list file does not exceed 300 MB. |
| OMS.01007 | Metadata of object list file not found. | Check the metadata of the list file. |
| OMS.01008 | URL decoding failed. | Check whether the URLs in the list file are correctly encoded. |
| OMS.01009 | Invalid resource path. | Check whether the list file path is correct. |
| OMS.01012 | List file not found. | Check whether the list file exists. |
| OMS.01015 | Read list file failed. | Check the status of the list file and ensure that the file is readable. If the file is normal and readable, try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01016 | Maximum rows (100,000) reached for list file. | Modify the list file to ensure that the number of rows is less than 100,000. |
| OMS.01017 | Content-Type of list file must be text/plain. | Check whether the list file is in TXT format and whether the Content-Type metadata is text/plain. |
| OMS.01018 | Content-Encoding of list files not empty. | Ensure that the Content-Encoding attribute is empty. |
| OMS.01019 | Download list failed. | Check the status of the list file and ensure that the file is readable. If the file is normal and readable, try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01020 | Read block file failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01021 | Listing failed object lists failed. | Check whether the failed object lists can be found. If they cannot, create a migration workflow again. |
| OMS.01023 | List file must be TXT. | Ensure that the list file is a .txt file. |
| OMS.01024 | Maximum list files (10,000) exceeded. | Ensure that the number of list files in the specified path is less than 10,000. |
| OMS.01025 | Save task information failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.01047 | Insufficient permissions for source credentials or key file. | Verify the permissions of your source AK/SK or key file. |
| OMS.01048 | Insufficient permissions for target credentials. | Verify the permissions of your target AK/SK. |
| OMS.01049 | Target unavailable. | Check the target connection parameters. |
| OMS.01050 | Row size too large in the list file (max. 16 KB). | Make sure that the size of each line in the list file is less than 16 KB. |
| OMS.04002 | List files failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.04003 | Start migration failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.04004 | Migration nodes not found in the cluster. | Ensure that the network between the source end, target end, and cluster is normal and the cluster is available. |
| OMS.04005 | List nodes not found in the cluster. | Ensure that the network between the source end, target end, and cluster is normal and the cluster is available. |
| OMS.04006 | Execute migration task failed. | Check the list of failed objects to determine the failure cause. |
| OMS.03003 | AK/SK verification failed. Ensure that the AK/SK pairs are valid. | Check whether the AK/SK pairs for accessing the source and the target are correct. |
| OMS.03004 | List objects failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.03005 | List buckets failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.03009 | Source CDN verification failed. | Check whether the CDN configuration is correct. |
| OMS.03010 | Run mount failed. | Mounting the NAS system failed. Check the connection or network settings. |
| OMS.03011 | Write data to stream failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.03015 | SMB connection failed. | Connecting to the SMB server failed. Check the connection or network settings. |
| OMS.03021 | Execute command failed. | Check the connection and network settings of the NAS server. |
| OMS.106303 | Delete NAT gateway failed. | Try again or manually delete the NAT gateway. |
| OMS.106705 | Create LTS host group failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.16008 | Restart migration task failed. | Try again or check whether the master node in the involved cluster is online. |
| OMS.106501 | Create security group failed. | Check the parameters and try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100003 | Operation error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100014 | Duplicate graph names not allowed. | Modify the graph name. |
| OMS.100110 | Max. API call failures reached. | Too many failures occurred in a short period, and the operation has been locked. Try again 60 seconds later. |
| OMS.100301 | Cluster unavailable. | Keep the cluster in a healthy state. |
| OMS.100407 | Unexpected node status. Delete cluster failed. | Check the node status. If the fault persists, contact technical support or submit a service ticket. |
| OMS.020145 | Max. retries reached. | Try again in 60 seconds. |
| OMS.06002 | Encrypt string failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.04034 | Execute migration task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.03060 | Invalid service type in the connection string. | Check the service type. |
| OMS.03061 | Invalid resource type in the connection string. | Check the resource type. |
| OMS.03062 | Required permissions not configured in the connection string. | Check the permissions. |
| OMS.03063 | Connection string expired. | Check the validity period of the connection string. |
| OMS.03059 | Invalid connection string. | Check the connection string. |
| OMS.100000 | System error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100001 | Resource not found. | Check whether the URL is valid. |
| OMS.100002 | Invalid parameters. | Check the parameters and try again. |
| OMS.100004 | Save data to database failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100005 | Update database failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100006 | Executor thread interrupted. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100007 | Executor error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100008 | Execute task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100009 | Create job failed. | Check whether the parameters are empty. |
| OMS.100010 | Cluster not found. | Create a cluster and try again. |
| OMS.100011 | Node not found. | Add a node. |
| OMS.100012 | Method or interface not implemented. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100013 | Update job status failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100015 | Invalid request parameters. | Check the parameters and try again. |
| OMS.100101 | Unauthorized. | Obtain authorization first. |
| OMS.100102 | Not logged in. | Log in first. |
| OMS.100103 | Login timed out. | Log in again. |
| OMS.100104 | Incorrect project. | Select another project. |
| OMS.100105 | Incorrect region. | Select another region. |
| OMS.100106 | op_service role missing. | Ensure that the account has the op_service role. |
| OMS.100107 | Not OMS internal user. | Ensure that the account is an OMS user. |
| OMS.100108 | Token verification failed. | Obtain a new token. |
| OMS.100109 | op account parameter missing. | Check whether the op account parameter is empty. |
| OMS.100201 | Task not found. | Check whether the task is normal. |
| OMS.100202 | Unexpected task status. | Check whether the task is in a paused, failed, or abnormal status. Only tasks in these statuses can be retried. |
| OMS.100203 | Deletion not supported. | Check whether the task is in a succeeded, failed, waiting, error, paused, or deletion failed status. Only tasks in these statuses can be deleted. |
| OMS.100204 | Pause not supported. | Check whether the task is running. |
| OMS.100205 | Task settings not found. | Check the task settings. |
| OMS.100206 | Task update failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100207 | Update migration statistics failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100208 | Publish SMN messages failed for task. | Check whether the SMN configuration exists. |
| OMS.100209 | Cluster unavailable. | Check whether the cluster is available. |
| OMS.100210 | Task type mismatch. | Only list migration is supported for HTTP or HTTPS sources. |
| OMS.100302 | Unfinished tasks found in cluster. | Wait until the tasks are complete and try again. |
| OMS.100304 | Delete cluster failed. | Check whether the cluster can be deleted. |
| OMS.100305 | Plugin upgrade failed for cluster. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100306 | Failed to update basic cluster information. | Check whether the cluster basic information is empty. |
| OMS.100307 | Failed to update cluster extension information. | Check whether the cluster extension information is empty. |
| OMS.100308 | Delete node failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100309 | Node reinstallation failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100310 | Retry node creation failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100311 | Retry cluster creation failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.1003012 | Insufficient quota. | Check whether the VPCEP quota is sufficient. |
| OMS.1003013 | Insufficient node quota. | Check whether the node quota is sufficient. |
| OMS.1003014 | The master node could not run. Try another cluster. | Select another cluster. |
| OMS.1003015 | Reinstallation not supported for master node. Try for cluster instead. | Try for cluster instead. |
| OMS.1003016 | Retry not supported for master node. Try for cluster instead. | Try for cluster instead. |
| OMS.1003017 | Failed to save cluster-level rate limiting rules. Invalid rate limiting settings. | Invalid rate limiting settings. |
| OMS.1003018 | The name already exists. | Change the name. |
| OMS.1003019 | Invalid parameters. | Check the parameters. |
| OMS.1003032 | Retry not supported in current status. | Retries are not supported in online status. |
| OMS.1003020 | No available migration node or list node. | Add migration or list nodes first. |
| OMS.1003021 | Some migration nodes or list nodes are abnormal. | Check whether the migration or list nodes are available. |
| OMS.1003022 | Master node abnormal. | Check whether the master node is available. |
| OMS.1003023 | A cluster must contain at least one master node, one migration node, and one list node. | Check whether the cluster is healthy. |
| OMS.1003024 | Installation failed. The cluster version is empty. | Contact technical support or submit a service ticket. |
| OMS.1003025 | Update node status failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.1003026 | The cluster does not need to be reclaimed. | Check the cluster status. |
| OMS.1003027 | Update cluster status failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.1003028 | Node specifications not found. | Modify the node specifications. |
| OMS.1003029 | A node must have at least 2 vCPUs and 4 GB memory. | Modify the node specifications. |
| OMS.1003030 | No upgrade to the cluster version is required. | The cluster version is already up to date. |
| OMS.1003031 | Plugin upgrade not supported for clusters using CentOS. | Only clusters using the HCE image are supported. |
| OMS.1003033 | Operation not supported for current cluster version. | Delete this old cluster and create a new one. |
| OMS.100401 | HTTP exception. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100402 | List buckets failed. | Ensure that you have the permissions to list buckets. |
| OMS.100403 | List objects failed. | Ensure that you have the permissions to list objects. |
| OMS.100404 | Source CDN verification failed. | Check whether the CDN information is valid. |
| OMS.100405 | The endpoint is empty. | Check the endpoint. |
| OMS.100406 | The migration task is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.100501 | Quota service error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106001 | An error occurred during the invocation of the external interface. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106101 | Failed to install node in cluster. | Wait until the node is offline and try again. |
| OMS.106102 | Failed to reinstall node in cluster. | The node is offline and cannot be reinstalled. |
| OMS.106103 | Failed to check the running status of the master node. | Check whether the master node is healthy. |
| OMS.106104 | Modify node quota failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106105 | List nodes failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106106 | Create migration task failed. | Check the authorization information or task configuration information. |
| OMS.106107 | Restart migration task failed. | Check whether the master node in the cluster is healthy. |
| OMS.106108 | Pause migration task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106109 | Delete migration task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106110 | Update migration task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106111 | Query migration task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106112 | Prepare backup failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106113 | Create restoration task failed. | Check the authorization information or task configuration information. |
| OMS.106114 | Sync cluster bandwidth failed. | Check whether the bandwidth configuration information is correct. |
| OMS.106115 | Update remote node failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.106116 | Agent node failed health check. | Check whether the migration or list nodes are healthy. |
| OMS.106201 | Create ECS failed. | Check whether the ECS service is available. |
| OMS.106202 | Create ECS failed. | Check whether the ECS service is available. |
| OMS.106203 | Obtain ECS job details failed. | Check whether the ECS service is available. |
| OMS.106204 | Obtain ECS port details failed. | Check whether the ECS service is available. |
| OMS.106205 | Obtain ECS details failed. | Check whether the ECS service is available. |
| OMS.106206 | Delete ECS failed. | Check whether the ECS service is available. |
| OMS.106207 | Change ECS specifications failed. | Check whether the ECS service is available. |
| OMS.106208 | List AZs failed. | Check whether the ECS service is available. |
| OMS.106209 | List ECS flavors failed. | Check whether the ECS service is available. |
| OMS.106210 | Obtain ECS flavor failed. | Check whether the ECS service is available. |
| OMS.106211 | Query extended ECS flavor information failed. | Check whether the ECS service is available. |
| OMS.106301 | Create NAT gateway failed. | Check whether the NAT gateway service is available. |
| OMS.106302 | Query NAT gateway details failed. | Check whether the NAT gateway service is available. |
| OMS.106304 | Create SNAT rule failed. | Check whether the NAT gateway service is available. |
| OMS.106305 | Query details of fault rules failed. | Check whether the NAT gateway service is available. |
| OMS.106306 | List SNAT rules failed. | Check whether the NAT gateway service is available. |
| OMS.106307 | Delete SNAT rule failed. | Check whether the NAT gateway service is available. |
| OMS.106308 | List DNAT rules failed. | Check whether the NAT gateway service is available. |
| OMS.106401 | Publish SMN message failed. | Check whether the SMN service is available. |
| OMS.106502 | Delete security group failed. | Check whether the VPC service is available. |
| OMS.106503 | Create security group rule failed. | Check whether the VPC service is available. |
| OMS.1065054 | List security group rules failed. | Check whether the VPC service is available. |
| OMS.106505 | Delete security group rule failed. | Check whether the VPC service is available. |
| OMS.106506 | Query security group details failed. | Check whether the VPC service is available. |
| OMS.106507 | Buy EIP failed. | Check whether the VPC Endpoint service is available. |
| OMS.106508 | Obtain EIP details failed. | Check whether the VPC Endpoint service is available. |
| OMS.106509 | Delete EIP failed. | Check whether the VPC Endpoint service is available. |
| OMS.106601 | Create VPC endpoint service failed. | Check whether the VPC Endpoint service is available. |
| OMS.106602 | Query VPC endpoint service details failed. | Check whether the VPC Endpoint service is available. |
| OMS.106603 | Create VPC endpoint failed. | Check whether the VPC Endpoint service is available. |
| OMS.106604 | Query VPC endpoint details failed. | Check whether the VPC Endpoint service is available. |
| OMS.106605 | Delete VPC endpoint service failed. | Check whether the VPC Endpoint service is available. |
| OMS.106606 | Delete VPC endpoint failed. | Check whether the VPC Endpoint service is available. |
| OMS.106607 | Approve VPC endpoint connection failed. | Check whether the VPC Endpoint service is available. |
| OMS.106608 | Update trust list failed. | Check whether the VPC Endpoint service is available. |
| OMS.106701 | Create LTS access configuration failed. | Check whether the LTS service is available. |
| OMS.106702 | Obtain LTS access configuration failed. | Check whether the LTS service is available. |
| OMS.106703 | Delete LTS access configuration failed. | Check whether the LTS service is available. |
| OMS.106704 | Obtain host failed. | Check whether the LTS service is available. |
| OMS.106706 | Add host to LTS host group failed. | Check whether the LTS service is available. |
| OMS.106707 | Obtain LTS host group details failed. | Check whether the LTS service is available. |
| OMS.106708 | Delete host group failed. | Check whether the LTS service is available. |
| OMS.106709 | Create LTS log group failed. | Check whether the LTS service is available. |
| OMS.106710 | Obtain log group details failed. | Check whether the LTS service is available. |
| OMS.106711 | Delete LTS log group failed. | Check whether the LTS service is available. |
| OMS.106712 | Create log stream failed. | Check whether the LTS service is available. |
| OMS.106801 | Obtain KMS details failed. | Contact technical support or submit a service ticket. |
| OMS.106802 | Authentication failed. | Use a valid tenant account to access the correct project. |
| OMS.106803 | Query KMS key failed or key is unavailable. | Add the kms:cmk:get action for OMS to query keys and go to DEW to configure keys. |
| OMS.106804 | Create DEK failed. | Add the kms:dek:create action for OMS to create DEKs, or contact technical support. |
| OMS.106805 | Decrypt DEK failed. | Add the kms:dek:decrypt action for OMS to decrypt DEKs, or contact technical support. |
| OMS.106806 | Failed to encrypt/decrypt data using the KMS DEK. | Contact technical support or submit a service ticket. |
| OMS.107001 | Query pay-per-use price failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.108001 | Retry extended attributes failed. | Check whether the status of extended attributes is "update failed". |
| OMS.108002 | Update extended attributes failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.108003 | Add extended attributes failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.109001 | Query image failed. | Check whether the IMS service is available. |
| OMS.110001 | Node connection failed. Try again or check whether subnet ACLs deny the connection. If the fault persists, contact customer service. | Try again or check whether subnet ACLs deny the connection. If the fault persists, contact customer service. |
| OMS.020101 | Download package from OBS failed. | Check whether the permissions are sufficient and whether the package exists. |
| OMS.020102 | Set up SSH connection failed. | The username and password are incorrect, or the IP address of the server is unreachable. |
| OMS.020103 | Upload failed. | Try again later. |
| OMS.020104 | File upload failed. | Try again later. |
| OMS.020105 | Node already deployed. | Do not perform the operation repeatedly. |
| OMS.020106 | SSH connection to node timed out. | The username and password are incorrect, or the IP address of the server is unreachable. |
| OMS.020107 | Verify SSH connection to node failed. | The username and password are incorrect, or the IP address of the server is unreachable. |
| OMS.020108 | SSH connection to node rejected. | The username and password are incorrect, or the IP address of the server is unreachable. |
| OMS.020109 | Other deployments failed. | Try again later. |
| OMS.020110 | Deployment timed out. | Try again later. |
| OMS.020111 | A subtask with the same ID is running on the node. | Do not perform the operation repeatedly. |
| OMS.020112 | Local data write failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.020113 | An exception occurred when data was written from the local node to the external storage. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.020114 | Abnormal source or target. | Check whether the source or target is normal. |
| OMS.020115 | The OBS connection is abnormal. | Check whether the connection information is correct and whether the network is normal. |
| OMS.020116 | An exception occurred when OBS files were parsed. | Check whether you have the required permissions. |
| OMS.020117 | An exception occurred when OBS files were read. | Check whether you have the required permissions. |
| OMS.020118 | Heartbeat lost. | Check whether the connection information is correct and whether the network is normal. |
| OMS.020119 | Source initialization failed. | Check whether the connection information is correct and whether the network is normal. |
| OMS.020120 | Target initialization failed. | Check whether the connection information is correct and whether the network is normal. |
| OMS.020121 | Migration/Comparison manager not found. | Check whether the migration/comparison manager exists. |
| OMS.020122 | Persistent write failed. | Check whether the connection information is correct and whether the network is normal. |
| OMS.020123 | Insufficient quotas. | Increase the quotas. |
| OMS.020124 | Object list files too large. | Modify the object list files. |
| OMS.020125 | Metadata attributes of object list file not found. | Ensure that the metadata attributes of the object list file exist. |
| OMS.020126 | Decoding using the URL decoder failed. | Check whether the URLs are valid. |
| OMS.020127 | Migration nodes not found in cluster. Check whether network between the source or target and the cluster is normal and whether the cluster is available. | Check whether network between the source or target and the cluster is normal and whether the cluster is available. |
| OMS.020128 | List nodes not found in cluster. Check whether network between the source or target and the cluster is normal and whether the cluster is available. | Check whether network between the source or target and the cluster is normal and whether the cluster is available. |
| OMS.020129 | Invalid source path. | Check whether the source path is valid. |
| OMS.020130 | Invalid target path. | Check whether the target path is valid. |
| OMS.020131 | Source verification failed. | Check the source information. |
| OMS.020132 | Target verification failed. | Check the target information. |
| OMS.020133 | Reading object list files failed. | Check whether you have the required permissions. |
| OMS.020134 | Listing object list files failed. | Check whether you have the required permissions. |
| OMS.020135 | Object list files too large. | Check the object list files. |
| OMS.020136 | Too many rows in object list files. | Check the object list files. |
| OMS.020137 | Object list files not found. | Check the object list files. |
| OMS.020138 | Invalid source AK/SK. | Check whether the AK/SK pair is valid. |
| OMS.020139 | Invalid target AK/SK. | Check whether the AK/SK pair is valid. |
| OMS.020140 | An error occurred when list files were read. | Check whether you have the required permissions. |
| OMS.020141 | List files too large. | Check the list files. |
| OMS.020142 | Too many rows in list files. | Check the list files. |
| OMS.020143 | Invalid Content-Type attribute of list files. | Check the list files. |
| OMS.020144 | Content-Encoding of list files not empty. | Check the list files. |
| OMS.020146 | Change cluster failed. | Try again later. |
| OMS.020147 | Execute migration task failed. Check "failedReportPath". | Check the failure report path. |
| OMS.020153 | Invalid service type for connection string. The Blob service type must be included. | Check whether the connection string contains the Blob service type. |
| OMS.020154 | Invalid resource types for connection string. The container and object resource types must be included. | Check whether the connection string contains the container and object resource types. |
| OMS.020155 | Invalid connection string permissions. The read and list permissions must be included. | Check whether the connection string has the required permissions. |
| OMS.020156 | Check the validity period of the connection string. | Check the validity period of the connection string. |
| OMS.020157 | Invalid connection string. | Modify the connection string. |
| OMS.020148 | An error occurred. Try again later or contact customer service. | Contact customer service. |
| OMS.020149 | Failed to list failed block files. | Check large object files. |
| OMS.020150 | Invalid list file format. | Check the list files. |
| OMS.020151 | List file names must end with .txt. | Check the list files. |
| OMS.020152 | Object list files exceed the limit. | Check the list files. |
| OMS.003026 | Restore object failed. | Ensure that you have the permissions to restore objects. |
| OMS.003020 | Initialize client failed. | Verify user permissions and network connectivity. |
| OMS.003024 | AK/SK verification failed. Ensure that the AK/SK pairs are valid. | Ensure that the AK/SK pairs are valid. |
| OMS.003019 | List objects failed. | Ensure that you have the permissions to list objects. |
| OMS.003021 | List buckets failed. | Ensure that you have the permissions to list buckets. |
| OMS.003003 | Failed to read fileAttribute. | Check the file permissions. |
| OMS.003010 | Failed to obtain inputSteam. | Check the file permissions. |
| OMS.003023 | Obtain object metadata failed. Source object archived. | Check object metadata. |
| OMS.003027 | Source CDN verification failed. | Check whether the CDN information is valid. |
| OMS.003028 | Empty request parameters. | Check whether the parameters are empty. |
| OMS.003002 | Execute mount command failed. | Verify that the SFS file system has the required access permissions. |
| OMS.003011 | Failed to write to inputSteam. | Check the file permissions. |
| OMS.003012 | Create link failed. | Check whether the network is normal. |
| OMS.003013 | Obtain link failed. | Check whether the network is normal. |
| OMS.003005 | Failed to write fileAttribute. | Check the file permissions. |
| OMS.003008 | Connection through smbConnector failed. | Check network connectivity to the SMB service. |
| OMS.003009 | Disconnection failed. | Try again later. |
| OMS.003018 | Invalid object names. Backslashes (\) are not allowed. | Check the object names. |
| OMS.003006 | Create parent directory failed. | Check whether the parent directory already exists. |
| OMS.003025 | Initiate multipart upload failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.003029 | Query multipart upload task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.003001 | Execute command failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.007002 | Failed to start task and save task information. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.003030 | The current object is not archived. | Check whether the object is archived. |
| OMS.003031 | Object already restored. | There is no need to restore it again. |
| OMS.003032 | Object being restored. | There is no need to restore it again. |
| OMS.003033 | Access denied. | Check whether you have the required permissions. |
| OMS.003034 | Operation not supported for objects in current status. | Check the object status. |
| OMS.020998 | Pause task failed. | Try again later. |
| OMS.020999 | Pause subtask failed. | Try again later. |
| OMS.000000 | An error occurred. Try again later or contact customer service. | Try again later. |
| OMS.000001 | Update failed. Try again later. | Try again later. |
| OMS.000002 | Creation failed. Try again later. | Try again later. |
| OMS.000003 | Database operation failed. Try again later. | Try again later. |
| OMS.000004 | Invalid mode. Check and try again. | Check the mode. |
| OMS.000006 | Token missing. | Check the token. |
| OMS.000007 | Invalid token. | Check the token. |
| OMS.000008 | Invalid parameters. | Check the parameters. |
| OMS.000005 | Remote URL call failed. Check and try again. | Check and try again. |
| MgC.00000304 | OMS response exception. Reason: *** | OMS response exception. Locate the fault and handle the error by referring to Error Codes. |
| MgC.00000307 | Parse OMS response failed: Unexpected data format. | Failed to parse the OMS response because the returned data is not as expected. Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.001000 | Invalid parameter type. Enter valid parameters. | Enter valid parameters. |
| OMS.001001 | Type mismatch. Enter a correct type. | Enter a correct type. |
| OMS.001002 | Failed to retrieve files from URLs (UTF-8). | Check whether the URLs are valid. |
| OMS.001003 | Read files from OBS failed. | Check whether the file permissions are correct and whether the files exist. |
| OMS.001004 | Failed to obtain metadata of object list files. The metadata is empty. | Check whether the metadata of object list files exists. |
| OMS.001005 | Invalid Content-Type attribute. | Check the file attributes. |
| OMS.001006 | Content-Encoding not empty. | Check the file attributes. |
| OMS.001007 | Unable to read failed object list. It is locked. | Check the file permissions. |
| OMS.001008 | List file must be TXT. | Check the file attributes. |
| OMS.002000 | Duplicate node name or IP address. Enter valid parameters. | Enter valid parameters. |
| OMS.002001 | SSH connection failed. The username and password are incorrect or the server IP address is unreachable. | The username and password are incorrect, or the IP address of the server is unreachable. |
| OMS.002002 | Node not found. Enter valid parameters. | Enter valid parameters. |
| OMS_INTERNAL.002000 | File upload failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS_INTERNAL.002001 | Script execution failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.0003000 | Empty request parameters. | Check the parameters. |
| OMS.003007 | Attribute parameters are empty. | Check the parameters. |
| OMS.003014 | Delete redundant benchmark file failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.003015 | Failed to verify the OBS connection. | Check whether the OBS service is normal. |
| OMS.003004 | Failed to read the attributes of the permission file. | Check the file permissions. |
| OMS.003016 | No bucket access permissions or bucket not found. | No permissions to access bucket or bucket not found. |
| OMS.003017 | Failed to verify OBS write permissions. | Check whether you have the write permissions. |
| OMS.003022 | Prefix verification failed. | Check whether the prefixes are valid. |
| OMS.004000 | Task not found. | Create a task first. |
| OMS.004001 | Failed to delete the running task. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004002 | Failed to pause task and update task status. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004003 | Modify task failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004004 | Failed to start task and reset task status. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004005 | Delete task failed. Task not found. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004006 | Start task failed. Invalid task status. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004007 | Start task failed. Failed to update site information. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.004008 | Task creation failed. Node not found. | Check whether the migration or list nodes exist. |
| OMS.004009 | Task creation failed. The site is empty. | Check whether the migration or list nodes exist. |
| OMS.004010 | Task creation failed. The site already exists. | Check whether the SSH connection is normal. |
| OMS.004011 | Failed to query task list. Invalid task names. | Check whether the task names are valid. |
| OMS.004012 | Pause task failed. Invalid task status. | Check the task status. |
| OMS.004013 | Concurrent subtasks: from 1 up to 10 times the number of migration nodes. | Modify the number of subtasks. |
| OMS.004014 | The overwriting policy cannot be modified when the task is running or has already succeeded. | Check the task status. |
| OMS.004016 | Query task monitoring data failed. Invalid time range. | Modify the time range. |
| OMS.004015 | Task creation failed. Metadata migration is not supported for the current location. | Metadata migration is not supported for the current location. |
| OMS.004017 | The start time must be earlier than the end time. | The start time must be earlier than the end time. |
| OMS.004018 | Time ranges in rate limiting rules cannot overlap. | The start time must be earlier than the end time. |
| OMS.004019 | Up to six rate limiting rules can be configured. | Up to six rate limiting rules can be configured. |
| OMS.004020 | The start time and end time are required. | Specify the start and end times. |
| OMS.004021 | Start task failed. Task settings are missing. | Add task settings first. |
| OMS.004022 | Task creation failed. Invalid task type. | Modify the task type. |
| OMS.004023 | Task creation failed. Invalid task settings. | Modify the task settings. |
| OMS.005000 | Initialize queue client failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.005001 | Stop queue client failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.005002 | Queue client not initialized. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.005003 | Failed to create the persistent sequence node. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.005004 | Node not found. | Check whether the node exists. |
| OMS.005005 | Delete queue data failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.006001 | Failed to lock the task to update the last delivery time of migration subtasks. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS_006002 | Save key content failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS_006003 | SCC hardware synchronization failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS_006004 | Parameters for updating SCC are incorrect. | Check the parameters. |
| OMS_006005 | Re-initialize SCC instance failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.007001 | Session connection error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| OMS.007002 | Failed to start task and save task information. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MGC-OBS-Plugin.0002 | Access bucket failed. | Try again later. If the fault persists after several retries, perform the following operations: Create an OBS destination bucket and configure its basic information. Then, create a migration plan, deselect Create a destination bucket automatically, and configure the destination bucket for migration. |
| MGC-OBS-Plugin.0003 | Insufficient permission to access the source bucket. | Verify that the source bucket exists and that your credentials have the obs:bucket:HeadBucket permission.
After the preceding requirements are met, try again. If the fault persists after several retries, perform the following operations: Create an OBS destination bucket and configure its basic information. Then, create a migration plan, deselect Create a destination bucket automatically, and configure the destination bucket for migration. |
| MGC-OBS-Plugin.0005 | Failed to obtain the source bucket metadata. | Verify that the source bucket exists and that your credentials have the obs:bucket:HeadBucket permission.
After the preceding requirements are met, try again. If the fault persists after several retries, perform the following operations: Create an OBS destination bucket and configure its basic information. Then, create a migration plan, deselect Create a destination bucket automatically, and configure the destination bucket for migration. |
| MGC-OBS-Plugin.0006 | Insufficient permission to access the destination bucket. | Verify that the destination bucket exists and that your credentials have the obs:bucket:HeadBucket permission.
After the preceding requirements are met, try again. If the fault persists after several retries, perform the following operations: Create an OBS destination bucket and configure its basic information. Then, create a migration plan, deselect Create a destination bucket automatically, and configure the destination bucket for migration. |
| MGC-OBS-Plugin.0007 | Create destination bucket failed. | Verify that the destination credentials have the obs:bucket:CreateBucket permission.
|
| MGC-OBS-Plugin.0008 | Failed to obtain the source bucket properties. | Verify that the source credentials have the following permissions: Obtaining the bucket BPA configuration: obs:bucket:GetBucketPublicAccessBlock Obtaining the bucket policy: obs:bucket:GetBucketPolicy Obtaining the bucket ACL: obs:bucket:GetBucketAcl Obtaining the lifecycle configuration of a bucket: obs:bucket:GetLifecycleConfiguration Obtaining the bucket quota: obs:bucket:GetBucketQuota Obtaining the user-defined domain name of a bucket: obs:bucket:GetBucketCustomDomainConfiguration Obtaining the event notification configuration of a bucket: obs:bucket:GetBucketNotification Obtaining the default storage class of a bucket: obs:bucket:GetBucketStoragePolicy Obtaining the versioning status of a bucket: obs:bucket:GetBucketVersioning Obtaining the cross-region replication configuration of a bucket: obs:bucket:GetReplicationConfiguration Obtaining the bucket tag: obs:bucket:GetBucketTagging Obtaining the encryption configuration of a bucket: obs:bucket:GetEncryptionConfiguration Obtaining the direct reading configuration of Archive objects in a bucket: obs:bucket:GetDirectColdAccessConfiguration Obtaining the website configuration of a bucket: obs:bucket:GetBucketWebsite Obtaining the CORS configuration of a bucket: obs:bucket:GetBucketCORS Obtaining the logging configuration of a bucket: obs:bucket:GetBucketLogging
|
| MGC-OBS-Plugin.0009 | Failed to set the properties of the destination bucket. | Verify that the destination credentials have the following permissions: Obtaining the bucket BPA configuration: obs:bucket:GetBucketPublicAccessBlock Obtaining the bucket policy: obs:bucket:GetBucketPolicy Obtaining the bucket ACL: obs:bucket:GetBucketAcl Obtaining the lifecycle configuration of a bucket: obs:bucket:GetLifecycleConfiguration Obtaining the bucket quota: obs:bucket:GetBucketQuota Obtaining the user-defined domain name of a bucket: obs:bucket:GetBucketCustomDomainConfiguration Obtaining the event notification configuration of a bucket: obs:bucket:GetBucketNotification Obtaining the default storage class of a bucket: obs:bucket:GetBucketStoragePolicy Obtaining the versioning status of a bucket: obs:bucket:GetBucketVersioning Obtaining the cross-region replication configuration of a bucket: obs:bucket:GetReplicationConfiguration Obtaining the bucket tag: obs:bucket:GetBucketTagging Obtaining the encryption configuration of a bucket: obs:bucket:GetEncryptionConfiguration Obtaining the direct reading configuration of Archive objects in a bucket: obs:bucket:GetDirectColdAccessConfiguration Obtaining the website configuration of a bucket: obs:bucket:GetBucketWebsite Obtaining the CORS configuration of a bucket: obs:bucket:GetBucketCORS Obtaining the logging configuration of a bucket: obs:bucket:GetBucketLogging
|
| MGC-OBS-Plugin.0014 | System error. | Try again later. If the fault persists after several retries, contact MgC technical support. |
| MGC-OBS-Plugin.0016 | Access OMS failed. | Try again later. If the fault persists after several retries, contact MgC technical support or rectify the fault by referring to OMS Error Codes. |
| MGC-OBS-Plugin.0017 | Too many buckets under the tenant. | The current tenant has reached the maximum limit of 100 buckets. To proceed, create a migration plan using an existing destination bucket, or delete unnecessary buckets to free up space. |
MgC Error Codes
| Error Code | Description | Solution |
|---|---|---|
| MgC.00030101 | Unknown error. | There are many possible causes for this error, for example, the network could be abnormal. Try this workflow step again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00010532 | Involved collection task not found. | Associate the collection item with another collection task. |
| MgC.00010533 | Add data source failed. | Contact technical support or submit a service ticket. |
| MgC.00010534 | Data source not found. | Refresh the collection item list and check whether the data source exists. |
| MgC.00000101 | Could not collect information from Alibaba Cloud RM. | Debug the API SearchResources by following the instructions provided in the Alibaba Cloud Resource Management Documentation and locate the fault cause based on the returned error code, or contact Alibaba Cloud technical support. |
| MgC.00000102 | Could not collect information from Alibaba Cloud RM. | Debug the API GetResourceConfiguration by following the instructions provided in the Alibaba Cloud Resource Management Documentation and locate the fault cause based on the returned error code, or contact Alibaba Cloud technical support. |
| MgC.00000103 | Credential not found. | Check whether the selected credential can be found on the Credentials page. |
| MgC.00000104 | Credential expired. | Update it in the Credential Mgmt area. |
| MgC.00000105 | Wrong credential type. Select AK/SK credentials. | Select AK/SK credentials. |
| MgC.00000106 | Incorrect file format. | Upload a file in the correct format. |
| MgC.00000107 | Failed to query domain names by page. | Debug the API DescribeDomains by following the instructions provided in the Alibaba Cloud Resource Management Documentation and locate the fault cause based on the returned error code, or contact Alibaba Cloud technical support. |
| MgC.00000108 | Could not query DNS records in pagination mode. | Debug the API DescribeDomainRecords by following the instructions provided in the Alibaba Cloud Resource Management Documentation and locate the fault cause based on the returned error code, or contact Alibaba Cloud technical support. |
| MgC.00000109 | Could not invoke the Alibaba Cloud WAF SDK. | Debug the API DescribeDomains by following the instructions provided in the Alibaba Cloud Resource Management Documentation and locate the fault cause based on the returned error code, or contact Alibaba Cloud technical support. |
| MgC.00000110 | Create Alibaba Cloud SLB SDK client failed. | Check whether the selected credential and regions are correct. |
| MgC.00000111 | Uploaded file contains invalid data. | Enter valid values. |
| MgC.00000112 | Uploaded file failed the verification. | Contact technical support or submit a service ticket. |
| MgC.00000113 | Required fields are missing in uploaded file. | Specify required fields. |
| MgC.00000114 | Table headers of uploaded file are incorrect. | Enter a correct table header. |
| MgC.00000115 | Table headers of uploaded file are invalid. | Check whether non-customized table headers in the template have been modified. |
| MgC.00000116 | Unexpected domain names found in "Domain" sheet. | Ensure that domain names entered in the "Application" and "MQ" sheets have been entered in the "Domain" sheet. |
| MgC.00000117 | Invalid file format. | Check whether the import template was modified or download the template again. |
| MgC.00000142 | Insufficient permission. | Confirm your access key is valid and the IAM policy allows necessary actions. For details about the permission requirements, see Data Collection from AWS |
| MgC.00000200 | File upload failed. | Contact technical support or submit a service ticket. |
| MgC.00000201 | File download failed. | Contact technical support or submit a service ticket. |
| MgC.00000202 | Uploaded file not found in OBS or expired. | Upload a new file, or rename the file and upload it again. |
| MgC.00010531 | Parameter check failed. | The source resource information is insufficient. Perform a deep collection to gather more details. |
| MgC.00030142 | Daily workflow quota exhausted. | Switch to another project or delete a completed workflow in the current project. |
| MgC.00030143 | Maximum resources for a workflow reached. | Ensure that no more than 100 resources are included in the workflow. |
| MgC.00030148 | Resource deletion not allowed. The workflow was not found or is being deleted. |
|
| MgC.00030149 | Resource deletion failed. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030150 | The resources are being deleted. | Wait until the resource is deleted. |
| MgC.00030151 | Failed to remove resources from migration plan. | Remove resources manually from the migration plan. If the resources cannot be manually removed, contact technical support or submit a service ticket. |
| MgC.00030152 | Failed to clear workflow data. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030153 | Full deletion of resources from workflow is not allowed | Do not delete all resources from the workflow. Retain at least one resource. |
| MgC.00030154 | Execute task failed. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030155 | Request timed out. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030210 | Execute script failed. Click Check Details to go to COC. | Check the failure cause on the COC console. After the error is fixed, retry your operation on the MgC console. Alternatively, skip the abnormal script. |
| MgC.00030213 | Add post-migration stage failed because the workflow has been executed. | Post-migration stages can only be added to stages and steps in the Waiting or Paused status. |
| MgC.00030212 | Add step failed. Max. 10 steps for a post-migration stage. | Delete unnecessary steps before adding new ones. |
| MgC.01000004 | Call FunctionGraph APIs failed. Try again later. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000015 | Deliver command to MgC Agent failed. | Check the MgC Agent (formerly Edge) logs. If the MgC Agent logs record "channel is not opened," the network connection between the MgC Agent and the source server is abnormal. Check and restore the network connection and try again. The MgC Agent log files are located at:
|
| MgC.00000045 | Command execution by MgC Agent timed out. | This issue is usually caused by network connection problems. Try again later. If the error persists, check whether the network settings of the source servers meet the requirements. Alternatively, view the MgC Agent (formerly Edge) logs to locate the fault. The logs are located at:
|
| MgC.00000048 | KMS key unavailable or not found. | Use a valid KMS key. |
| MgC.00000049 | Query KMS key failed. | Try again. If the fault persists, contact technical support. |
| MgC.00050010 | The AK and SK must be updated at the same time. | Update the AK/SK pair and try again. |
| MgC.00050107 | Regions of applications for cross-AZ migration cannot be changed. | Do not change the region of the application for cross-AZ migration. |
| MgC.00050108 | Applications for cross-AZ migration cannot be converted to other applications. | Try other types of applications. |
| MgC.00050201 | IoTDA device ID already exists. | Try to reconnect the MgC Agent to MgC on the MgC Agent console. |
| MgC.00050200 | Delete IoTDA device failed. Network error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00050102 | Application not found based on its ID. | Refresh the page and try again. |
| MgC.00050318 | Application not found based on its ID. | Refresh the page and try again. |
| MgC.00050311 | Query region failed. The application is unavailable in this region. | Create the application in another region or create another application. |
| MgC.00050321 | Target AZ will be decommissioned soon. | Select another AZ. |
| MgC.00050003 | Credential not found. | Create a credential. |
| MgC.00050025 | Credential not found. It cannot be deleted or changed. | Refresh the page and try again. |
| MgC.00050026 | Invalid request parameters. | Check the parameters and try again. |
| MgC.00050009 | Incorrect credential parameters. | Check whether the credential parameters meet requirements. |
| MgC.00050011 | Credential decryption failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00050001 | Invalid credential name. | Check the credential name and change it to a valid name. |
| MgC.00050005 | Invalid credential file. | Check whether the credential file format is correct. |
| MgC.00050004 | The credential already exists. It cannot be created or updated. | Delete the old credential or create a new one. |
| MgC.00050304 | Invalid migration project parameters. | Update the parameter settings. |
| MgC.00050215 | Device not found. | Associate an MgC Agent again. |
| MgC.00050204 | Device quota exhausted. | Delete unneeded MgC Agents and register your agent again. Alternatively, associate your agent with another migration project. |
| MgC.00050211 | Database error. | Contact technical support or submit a service ticket. |
| MgC.00050002 | Add or update credential failed. The certificate name already exists. | Change the credential name and try again. |
| MgC.00050301 | Duplicate project name. | Change the project name and try again. |
| MgC.00050320 | Too many projects. | Delete unneeded projects. |
| MgC.00050113 | The application is in use and cannot be deleted. | Delete the application after it is no longer used. |
| MgC.00050221 | Too many registered devices. | Delete devices that are no longer needed. Alternatively, select another migration project to register the MgC Agent. |
| MgC.00050317 | The resource is included in a migration workflow. Delete the workflow first. | Delete the workflow or remove the resource from the workflow. |
| MgC.00050303 | This is the only migration project and cannot be archived. | Change the migration project to be modified. |
| MgC.00020032 | Bill parsing failed. Max. lines (8,000) reached. | Upload a CSV or PDF file with up to 8,000 lines. |
| MgC.00020029 | Operation failed. Try again. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020228 | ECS not found. | Use another target server and try again. |
| MgC.00020277 | Prefix list file invalid or too large. | The prefix list file is invalid or too large (exceeding 2 MB). Modify the file and try again. |
| MgC.00020278 | Analyze prefix list file failed. | The prefix list file's format is incorrect. Modify the file and try again. |
| MgC.00020279 | The platform type of the source resource is inconsistent with that required by the plan. | Modify the source platform and try again. |
| MgC.00020280 | This migration plan cannot be modified because a workflow has been created for it. | Wait until the workflow is complete and try again. |
| MgC.00020281 | Assessment cannot continue because no bucket resources are added. | Add bucket resources and try again. |
| MgC.00020282 | Too many resources. | A migration plan can include a maximum of 100 resources. To migrate additional resources beyond this limit, create a new migration plan for them. |
| MgC.00020283 | Invalid list path. | Check and correct the list path, and try again. |
| MgC.00020284 | Invalid path prefix. | Check and correct the path prefix, and try again. |
| MgC.00020291 | Unsupported region. | Select a supported region and try again. |
| MgC.00020301 | Duplicate migration plan name. | Change the name and try again. |
| MgC.00020302 | Image ID not found. | Use another image and try again. |
| MgC.00020303 | Resources not found in current plan. | Check the resource list and try again. |
| MgC.00020304 | Too many rows. Limit: {0} | Reduce the number of rows and try again. |
| MgC.00020305 | Server configuration not completed. | Wait until the server configuration is complete and try again. |
| MgC.00020306 | Incorrect disk information. | Check the server disk information and try again. |
| MgC.00020308 | Duplicate resource IDs. | Remove the duplicate resource IDs and try again. |
| MgC.00020309 | Server specifications are empty. Specify specifications. | Specify specifications and try again. |
| MgC.00020310 | Server image is empty. Specify an image. | Specify an image and try again. |
| MgC.00020311 | Server disk is empty. Add disks. | Add disks and try again. |
| MgC.00020316 | Incorrect plan type. | Modify the plan type and try again. |
| MgC.00020319 | Source buckets have been included in other migration plans. | Remove the buckets included in other plans and try again. |
| MgC.00020320 | Target bucket {0} not found. | Use another target bucket and try again. |
| MgC.00020322 | Invalid source file system address or path. | Check and modify the source file system address or path and try again. |
| MgC.00020323 | Invalid target file system address or path. | Check and modify the target file system address or path and try again. |
| MgC.00020324 | The combination of the source file system address and path already exists. | Check and modify the source file system address or path and try again. |
| MgC.00020333 | Invalid list file path. | Check and modify the list file path and try again. |
| MgC.00020335 | The combination of the source file system address and list path already exists. | Check and modify the source file system address or path and try again. |
| MgC.00021145 | A single migration project can contain up to 1,000 migration plans. | Delete the completed migration plans or create a new migration project. |
| MgC.00021146 | There are tasks in progress on the resources. Do not remove the resources. | Wait until the tasks are complete and try again. |
| MgC.00021147 | There are tasks in progress on the resources. Do not delete the migration plan. | Wait until the tasks are complete and try again. |
| MgC.00021148 | There are tasks in progress on the resources. Do not modify the migration plan. | Wait until the tasks are complete and try again. |
| MgC.00021149 | There are tasks in progress on the resources. Do not associate target resources. | Wait until the tasks are complete and try again. |
| MgC.00021150 | There are tasks in progress on the resources. Do not modify target resource configurations. | Wait until the tasks are complete and try again. |
| MgC.00021151 | Add resources failed. They have been added to migration plans. | Remove the resources included in other plans and try again. |
| MgC.00021152 | Too many prefixes. Limit: 1,000 | The number of prefixes exceeds 1,000. Split the prefixes and try again. |
| MgC.00021153 | Prefixes too long. Limit: 1,024 characters | Some prefixes exceed 1,024 characters. Change them and try again. |
| MgC.00021155 | The source and target servers have different numbers of disks. | Use another target server or change the number of disks on the target server and try again. |
| MgC.00021156 | The source and target servers have different disk IDs. | Modify the disks on the target server and try again. |
| MgC.00021160 | The Configurations sheet is not found in the imported file. | Import a file that contains the Configurations sheet. |
| MgC.00021161 | Invalid Azure bucket name. | Name the bucket in the format of storage_account_name/container_name. Do not include slashes (/) in storage_account_name and container_name. Otherwise, the container name cannot be correctly located and the migration fails. |
| MgC.00000046 | Duplicate resources in the request. | Change the source file storage address or source file path and try again. |
| MgC.00000047 | The resource already exists. | Change the source file storage address or source file path and try again. |
| MgC.00000050 | Unsupported encryption algorithm. | For OMS, only AES_256 and SM4 are supported. Choose one and try again. |
| MgC.00030104 | Resources not found. | Check whether the resources are available. |
| MgC.00030105 | Workflow creation failed. Data cannot be inserted into the database. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030106 | Workflow creation failed. Data cannot be inserted into the database. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030107 | Workflow creation failed. Data cannot be inserted into the database. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030108 | Workflow creation failed. Data cannot be inserted into the database. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030109 | Workflow creation failed. Data cannot be inserted into the database. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030110 | Workflow update failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030111 | Workflow update failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030112 | Workflow update failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030114 | Workflow deletion failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030115 | Workflow deletion failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030116 | Workflow deletion failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030117 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030118 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030119 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030120 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030121 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030122 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030123 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030124 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030125 | Workflow query failed. The database is abnormal. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00030126 | Operation not allowed. | The operation is not allowed in the current status. |
| MgC.00030128 | It is not allowed to add a stage before the first phase. | This operation is not allowed on the console. Stages cannot be manually added. |
| MgC.00030129 | The preceding stage is not in the waiting state. No more phases can be added. | This operation is not allowed on the console. Stages cannot be manually added. |
| MgC.00030130 | No step can be added before a repeatable step. | This operation is not allowed on the console. Steps cannot be manually added. |
| MgC.00030131 | The step is not repeatable. | No action is required. The current operation is invalid. Non-repeatable steps cannot be executed repeatedly. |
| MgC.00030135 | Resource assessment not completed. No workflows can be created. | Resources in the application or migration plan have not been assessed or configured. Create a workflow after the assessment or configuration is complete. |
| MgC.00030136 | No resources contained in application. | Add resources to the application, complete the assessment and configuration, and create a workflow. |
| MgC.00030137 | A workflow has been created for the application. | A workflow has been created for the application. No more workflows can be created. Delete the existing workflow and create one again. |
| MgC.00030138 | Some resources have not been rediscovered or pass the precheck. No workflows can be created. | Rediscover resources, complete the precheck, and create a workflow. |
| MgC.00030139 | A workflow has been created for the migration plan. No more workflows can be created. | A workflow has been created for the migration plan. No more workflows can be created. Delete the existing workflow and create one again. |
| MgC.00030140 | The number of times that the step can be repeated exceeds the upper limit. | The step cannot be repeated. You can only go to the next step. |
| MgC.00030141 | Credential expired or not meet workflow requirements. No workflows can be created. | Check whether the credential is correctly configured. |
| MgC.00030144 | Incorrect Cron expression. | Object storage migration supports periodic scheduling. You need to correctly configure the Cron expression. |
| MgC.00030146 | Invalid SMN configuration. | You need to correctly configure SMN and then create a workflow. |
Error Codes for Resource Assessment
| Error Code | Description | Solution |
|---|---|---|
| MgC.00000002 | Invalid token. | Obtain a valid token. |
| MgC.00000003 | Invalid HTTP request method or URL. | Verify that the HTTP request method and URL are correct. |
| MgC.00000004 | Invalid parameter value. | Check the parameters and try again. |
| MgC.00020201 | Server assessment failed. Obtain ECS flavors failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020203 | Server assessment failed. Query IMS images failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020204 | Query EVS disk types failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020206 | Query IMS images failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020208 | Query EVS AZ availability failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020209 | Image assessment failed. No matched Windows images. | Select a private, shared, or KooGallery image that meets the requirements. |
| MgC.00020210 | Image assessment failed. No matched Linux images. | Select a private, shared, or KooGallery image that meets the requirements. |
| MgC.00020211 | Image assessment failed. No matched system images. | Select a private, shared, or KooGallery image that meets the requirements. |
| MgC.00020007 | Server assessment failed. Source disk information is missing. | The source server disk information is missing. Perform a deep collection for the server and try again. |
| MgC.00020212 | Server assessment failed. Invalid source disk IDs. | Check the parameters and try again. |
| MgC.00020213 | Source server being assessed. You cannot assess it again now. | The assessment is in progress. Try again after the current assessment is complete. |
| MgC.00020214 | Assessment results not found. | Check the parameters and try again. |
| MgC.00020215 | Modify assessment results failed. | Check the parameters and try again. |
| MgC.00020216 | Modify server assessment results failed. No matched specifications. | Check the parameters and try again. |
| MgC.00020217 | Modify server assessment results failed. No images match. | Select a private, shared, or KooGallery image that meets the requirements. |
| MgC.00020218 | Modify server assessment results failed. Disk size too large. | Reset the disk capacity and try again. |
| MgC.00020219 | Failed to create an assessment for cross-AZ migration. Target AZ is missing. | Select a different target AZ and try again. |
| MgC.00020220 | Source server is already in target AZ. | Select a different target AZ and try again. |
| MgC.00020221 | Selected OS is different from source OS. | Select another OS and try again. |
| MgC.00020222 | Image not available. | Selected image has been taken offline. Select another one and try again. |
| MgC.00020223 | Modify server assessment results failed. Specified disk size cannot be smaller than source disk size. | Reset the disk capacity and try again. |
| MgC.00020229 | Server assessment failed. Source server specifications are missing. | Select desired specifications. |
| MgC.00020230 | Server assessment failed. No proper target specifications. | Select desired specifications. |
| MgC.00020231 | No specifications match source in target region based on selected assessment policy. | Select the server specifications manually. |
| MgC.00020232 | Server assessment failed. No proper target specifications meet your preferences. | Update the assessment policy and try again, or manually select the specifications. |
| MgC.00020233 | Server assessment failed. No target specifications meet business scenario. | Update the assessment policy and try again, or manually select the specifications. |
| MgC.00071042 | Your preferences could not be met. | Selected disk type not available in current region. Update the assessment policy and try again. |
| MgC.00071072 | Server assessment failed. Matched target specifications not found in target AZ. | Select a different target AZ and try again. Alternatively, modify the target specifications. |
| MgC.00071066 | Source server specifications are not supported. Manually associate an existing target server. | Associate an existing target server. |
| MgC.00070049 | Server assessment failed. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020271 | Flavor abandoned. | Change the specifications and try again. |
| MgC.00020272 | The flavor does not support the disk type. | Change the flavor or disk type and try again. |
| MgC.00020345 | Server purchase failed. | Rectify the fault based on the returned error information. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020346 | Internal service error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.01020275 | Source performance data is missing. Perform a performance collection for the source server. | The source server's performance data is missing. Perform a deep collection for the server and try again. Alternatively, do not set Sizing Criteria to Performance-based in the assessment policy. |
| MgC.01020276 | Source server performance data is missing. Perform a performance collection for source server. | The source server's performance data is missing. Perform a deep collection for the server and try again. Alternatively, do not set Sizing Criteria to Performance-based in the assessment policy. |
| MgC.01020277 | Obtained performance data failed. | The source server's performance data is missing. Perform a deep collection for the server and try again. Alternatively, do not set Sizing Criteria to Performance-based in the assessment policy. |
| MgC.01020299 | The file must be in CSV (UTF-8) format. | Save the CSV file in UTF-8 format. |
| MgC.00070007 | Server assessment failed. Source CPU information is missing. | The source server CPU information is missing. Perform a deep collection for the server and try again. |
| MgC.00020205 | No EVS disk types match source server. | Update the disk assessment preferences and try again, or manually select the disk type. |
| MgC.00000017 | Server assessment failed. Internal service error. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00070008 | Server assessment failed. Source memory information is missing. | The source server memory information is missing. Perform a deep collection for the server and try again. |
| MgC.00070005 | Server assessment failed. Source OS information is missing. | The source server OS information is missing. Perform a deep collection for the server and try again, or manually select the target image. |
| MgC.00070006 | Server assessment failed. No matched images. | Select an image. |
| MgC.00070009 | Server assessment failed. No matched server specifications. | Update the assessment policy and try again, or manually select the specifications. |
| MgC.00020315 | Server assessment failed. No proper target specifications. | Select desired server specifications. |
| MgC.00020321 | Server assessment failed. No matched target specifications in the target AZ. | Update the assessment policy and try again, or manually select the specifications. |
| MgC.00030100 | Unknown error. | There are many possible causes for this error, for example, the network could be abnormal. Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000303 | Call FunctionGraph APIs failed. Try again later. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.01020019 | 32-bit OSs are not supported for public images. | Select a private, shared, or KooGallery image that meets the requirements. |
| MgC.01020020 | Unknown source OS. | Select an image. |
| MgC.01020021 | No matching public image for the source distribution. | Select an image. |
| MgC.01020023 | Redis assessment failed. The platform type is empty | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.01020024 | Redis assessment failed. The instance type, Redis version, or capacity is not defined. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.01020025 | Redis assessment failed. Unsupported instance type. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.01020026 | Redis assessment failed. The Redis mode, instance type, or capacity is not defined. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020343 | No images match source server firmware. | Select a private, shared, or KooGallery image that meets the requirements. |
| MgC.00020207 | Disk type matching the source server has been sold out in the target region. | Update the disk assessment preferences and try again, or manually select the disk type. |
| MgC.00020290 | Server assessment failed. No matched disk specifications. | Update the assessment policy and try again, or manually select the specifications. |
| MgC.00021013 | Server assessment failed. Source disk IDs are missing. | The source server disk IDs are missing. Perform a deep collection for the server and try again. |
| MgC.00070011 | Server assessment failed. No matched server specifications in target AZ. | Update the disk assessment preferences and try again, or manually select the disk type. |
| MgC.00070012 | The target disk type in the target AZ has been sold out. | Update the disk assessment preferences and try again, or manually select the disk type. |
| MgC.00020200 | An error occurred. Try again later or contact customer service. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020224 | Modify server assessment results failed. No matching specifications in current AZ. | Choose a different AZ and modify the specifications again. |
| MgC.00020225 | Modify server assessment results failed. No matching specifications in current region. | Choose a different target region and modify the specifications again. |
| MgC.00020249 | Request failed due to FunctionGraph exception. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00020265 | Resource modification denied. Assessment in progress. | Wait for the assessment to complete before modifying the target specifications. |
| MgC.00020266 | Resource modification denied. Target already bound. | Disassociate the target first and then modify the target specifications. |
| MgC.00020273 | Target server cannot be identical to source server. Choose a different target server. | Choose a different target server for association. |
| MgC.00020274 | Target GPT disk must be at least 1 GB larger than paired source disk. | Manually adjust the target disk size. |
| MgC.00020275 | Insufficient source resource info. Collect source details first. | Collect source details again. |
| MgC.00020287 | Firmware mismatch between selected image and source server. Select another image. | Select an image that matches the source firmware type. |
| MgC.00020288 | Target system disk smaller than the minimum required by selected image. Configure a larger system disk or select an image with lower storage demands. | Select an image with lower capacity requirements or expand the system disk of the target server to meet the minimum image requirements. |
| MgC.00020289 | Insufficient flavor memory to meet image requirements. | Select a proper target server flavor. |
| MgC.00020293 | Windows migration requires the target server to have at least the same number of disks as the source. | Select a target server with the same number of disks as the source server. |
| MgC.00020294 | Windows migration requires the target server disks are at least as large as source server disks. | Resize the target server disks or select a server with disks of at least the same size. |
| MgC.00020295 | System disk not found on target server. | Choose a different target server for association. |
| MgC.00020297 | Supported target server flavors: Normal, Entry, Cpuv1, Cpuv2, Computingv3, Highmem, Saphana, Highcpu, Ultracpu, Fpga, Ascend, GPU, parallel computing, and AdvancedSmb | Select a proper target server flavor. |
| MgC.00020298 | Migration to disk-intensive or ultra-high I/O ECSs is not supported. | Select a proper target server flavor. |
| MgC.00020299 | Arm servers are not supported. | Select a proper target server flavor. |
| MgC.00020300 | BMSs are not supported. | Contact technical support or submit a service ticket. |
| MgC.00020307 | Target region of server does not match recommendation configuration. Perform specification recommendation again. | Perform the specification recommendation again. |
| MgC.00020313 | Target system disk: 40 to 1,024 GB | Enter a proper system disk size for the target server. |
| MgC.00020314 | Target data disk: 10 to 32,768 GB | Enter a proper data disk size for the target server. |
| MgC.00020317 | Query cloud resource quotas failed. | Check whether your cloud resource quotas are sufficient and try again. |
| MgC.00020325 | Some source servers have not been assessed. | Check whether target server specifications have been configured for all source servers to be migrated. |
| MgC.00020326 | Some source servers already have associated target ECSs. | For source servers associated with target servers, associating them with a DeH is not supported. |
| MgC.00020329 | Selected DeH unavailable. | Select an available DeH and try again. |
| MgC.00020330 | Insufficient DeH resources. | Apply for more DeH resources. |
| MgC.00020331 | Specifications mismatch between target server and DeH. | Associate another DeH or modify the target server specifications. |
| MgC.00020332 | Source server already associated with DeH. | To change the target server, disassociate the DeH first. |
| MgC.00020336 | Service ID not found. | Check whether the source or target server exists. |
| MgC.00020339 | Disassociation failed. No target server is associated with the source server. | Check whether the source server has an associated target server. |
| MgC.00020342 | Target association failed. The target server is already associated with another source server. | Choose a different target server for association. |
| MgC.00021144 | Source server access IP or port changed. Perform the readiness check again. | Perform the readiness check again. |
| MgC.00021154 | Invalid target server status. | Supported target server statuses: Running, Stopped, Restarting, or Forcibly Restarting. View the server status on the ECS console. |
| MgC.00020347 | Target server status not met. Supported statuses: Running, Stopped, Restarting, or Forcibly Restarting. View the server status on the ECS console. | Supported target server statuses: Running, Stopped, Restarting, or Forcibly Restarting. View the server status on the ECS console. |
Error Codes for Resource Collection and Discovery
| Error Code | Error Cause | Solution |
|---|---|---|
| MgC.00000001 | Network connection error. | Check the network connection and try again. |
| MgC.00000020 | Parameters do not match. | Check parameter settings and try again. |
| MgC.00000022 | Decrypt data failed. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000300 | Send message to device failed. | Ensure that the device is online. |
| MgC.00000129 | Access Huawei Cloud APIs failed. Check the network. | Check whether the network connection is normal and try again. |
| MgC.00000130 | Incorrect IAM authentication information. Check the AK/SK pair. | Check if the AK/SK pair is correct and up-to-date. |
| MgC.00000131 | Create client on Huawei Cloud failed. | Ensure that all settings are correct and try again. |
| MgC.00000132 | Access key not found or disabled. | Check whether the access key is correct and enabled. The cloud platform uses AK/SK pairs to collect data. AWS uses Amazon Security Token Service (STS) to generate temporary tokens. These temporary ones replace long-term access keys for higher security and are used to access other services to be collected. This error may be caused by STS being disabled in the following AWS regions: Middle East (UAE and Bahrain), Africa (Cape Town), Europe (Milan), and Asia Pacific (Hong Kong). Enable STS on the AWS console to resolve the issue. |
| MgC.00000135 | The request was rejected due to user traffic control. | Try again later to avoid traffic limiting. |
| MgC.00000136 | Request failed. Temporary server error. | Wait until the server recovers and try again. |
| MgC.00000138 | Request signature does not meet Alibaba Cloud requirements. | Ensure that your request signature meets Alibaba Cloud requirements and try again. |
| MgC.00000139 | Specified signature does not match calculated result. | Check your signature and try again. |
| MgC.00000144 | Network connection timed out or error returned. Try again later or contact customer service. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000145 | File parsing failed. | Ensure that the file format and content are correct and try again. |
| MgC.00000146 | Request to Alibaba Cloud APIs denied due to flow control. | Try again later to avoid API traffic limiting. |
| MgC.00000147 | Access Alibaba Cloud server failed. The service is unavailable in the selected region or the Alibaba Cloud credentials do not have sufficient permissions. | Ensure that the service in the selected region is enabled and the credentials are valid. |
| MgC.00000148 | Check proxy settings. | Ensure that the proxy server is configured correctly. |
| MgC.00000149 | Create client on Huawei Cloud failed. | Ensure that all settings are correct and try again. |
| MgC.00000150 | Request to Huawei Cloud APIs denied due to flow control. | Try again later to avoid API traffic limiting. |
| MGC.00000155 | Your account cannot use NAS or does not have sufficient balance. | Ensure that the service in the selected region is enabled. |
| MgC.00000156 | Insufficient permissions. | Ensure that you have the required permissions. |
| MgC.00000160 | The cloud vendor has not released this resource type in the region. | If you have this resource in another region, ensure that you have selected the correct region. If this resource type is not needed in the current region, exclude the region from the collection task to avoid this error. |
| MgC.00000161 | Collector server error. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000162 | Network connection timed out. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000164 | Invalid table headers in uploaded CSV file. | Check whether the table headers and mandatory fields in the uploaded CSV file meet the requirements. For details, see "Constraints" in Importing RVTools Data. For files exported from Alibaba Cloud, delete the extra comma (,) in the table header. |
| MgC.00000169 | File too large. Max. size: 50 MB. | Import a smaller file. |
| MgC.00000172 | Access Alibaba Cloud service failed. | Ensure that the service in the selected region is enabled. |
| MgC.00000173 | Valid credentials, but insufficient permissions. | Check the access policies or the account's permissions. For Alibaba Cloud, check AccessKey or account-level policies on their console. Wait a few minutes for the policy changes to take effect, then retry the collection task. |
| MgC.00010526 | Execute analysis task failed. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00010527 | Task execution timed out. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000174 | Mandatory fields cannot be empty. | Ensure that mandatory fields in the file are not empty. |
| MgC.00000167 | Required columns are missing. | Add the required columns. |
| MgC.00000163 | Request redirected by source. Try again. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000103 | Credential not found. | Upload the right credential. |
| MgC.00000104 | Credential expired. | Update it in the Credential Mgmt area. |
| MgC.01010034 | Resource conversion timed out. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.01010035 | Google Cloud service APIs are disabled. | Enable the related Google Cloud APIs and try again. The following APIs need to be enabled:
|
| MgC.01010036 | The resource connection configuration was modified during the pre-check, which invalidates the pre-check task. | Do not modify the connection configuration during the pre-check, so that results remain valid. If modifications are made, rerun the pre-check. |
| MgC.00010008 | Server access failed. Check the credential, port, server status, and SSH connections. | Check the credential, port, server status, and number of SSH connections. |
| EDGE.00170020 | Resource collection failed. Credential not found. | Upload the right credential. |
| EDGE.00170021 | Credential expired. | |
| EDGE.00170024 | The MgC Agent does not support collection using cloud credentials. | Use a valid credential. |
| EDGE.00170025 | File too large. Max. size: 1 MB. | Upload a file smaller than 1 MB. |
| EDGE.00262003 | Plugin exception. | Try again later. If the fault persists, contact technical support or submit a service ticket. |
| EDGE.00030022 | Collector not installed. | Install the MgC Agent collector. |
| EDGE.00030023 | The collector is offline. | Check whether the MgC Agent (formerly Edge) collector is online. |
| EDGE.00050028 | Collection failed. IP address does not match network range specified for credential. | Upload a credential that matches the IP address range. |
| SERVER.00000011 | The collection scripts were tampered with. | Contact technical support or submit a service ticket. |
| SERVER.00000012 | Mandatory fields missing or empty. | Mandatory fields: OS version, firmware type, number of CPU cores, memory, disk, and OS type.
|
| SERVER.00000002 | Invalid IP address or WinRM not running. | Check whether WinRM is started using winrm quickconfig on the source server. |
| SERVER.00000003 | Incorrect username or password, or mismatch between IP address and username/password pair. | Ensure the username and password are correct and they match the IP address. |
| SERVER.00000006 | Collect required information failed. Check whether .Net Framework, WMI, and COM on the source server are damaged. | Check whether necessary WMI classes are missing in the Windows system. If the WMI classes are missing, rectify the fault or reconfigure the WMI classes. After the fault is rectified, perform a deep collection again. The necessary WMI classes include:
|
| SERVER.00000009 | Plugin exception. | Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket. |
| SERVER.00010038 | The sudo terminal requires password authentication. | Use the root account for collection. If a non-root account is used, add 'mgc_test ALL=(ALL:ALL) NOPASSWD:ALL' under 'root ALL=(ALL:ALL) ALL' or 'root ALL=(ALL) ALL' to the /etc/sudoers file. Replace mgc_test with the account you used. |
| SERVER.00010002 | Connect to SSH failed due to SSH startup failure, incorrect username/password, or unreachable server IP address. | Check SSH, username/password, and server IP address. |
| SERVER.00010003 | Failed to obtain the home directory of the user. | Ensure that the home directory exists and the environment variables for running the command are correct. |
| SERVER.00010008 | tty required for executing sudo is enabled. | The requiretty option is enabled in the sudoers file. This forces sudo to require a tty. But the MgC Agent runs commands over SSH in a non-interactive session, which does not allocate a tty. As a result, sudo fails and returns an error. Solve the problem as follows:
|
| SERVER.00010009 | Algorithm negotiation between client and server failed. |
If the fault persists, contact technical support or submit a service ticket. |
| SERVER.00010010 | Authentication method not supported or authentication failed. |
|
| SERVER.00010035 | Connection timed out. |
|
| SERVER.00010034 | Failed to verify server host key. | Check whether the StrictHostKeyChecking parameter is correctly configured. |
| SERVER.00010036 | Failed to connect to remote server. | Ensure that the IP address of the server is correct. |
| MgC.00030100 | Unknown error. | There are many possible causes for this error, for example, the network could be abnormal. Try again. If the fault persists, contact technical support or submit a service ticket. |
| MgC.00000303 | Call FunctionGraph APIs failed. Try again later. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| PLATFORM.00070001 | Network connection timed out or error returned. Try again later or contact customer service. | Try again. If the fault persists, contact technical support or submit a service ticket. |
| PLATFORM.00070003 | Incorrect username or password. | Check whether your username and password are correct. |
| PLATFORM.00070002 | Access vCenter failed. Check whether the IP address and credential are correct. | Check whether the vCenter IP address and credential are correct and whether the network connection is normal. |
| STORAGE.001009 | Connection failed due to invalid credentials. | Use valid credentials and try again. |
Error Codes for the MgC Agent on Windows
Error Codes for the MgC Agent on Linux
| Error Code | Description | Solution |
|---|---|---|
| EDGE.00261001 | The server IP address or port is unreachable. | Verify that the IP address and port are correct, and ensure that the network connection is normal. |
| EDGE.00261002 | Source port unreachable. | Check whether the source port can be reached using telnet. |
| EDGE.00261003 | SSH connection to source server failed. | Rectify the fault based on the error message. If the fault persists, contact technical support or submit a service ticket. |
| EDGE.00261004 | Invalid username or password. | Ensure that the credential provided to the MgC Agent (formerly Edge) is correct. |
| EDGE.00261005 | Source SFTP unavailable. | Check whether the MgC Agent (formerly Edge) server can access SFTP on the source server. |
| EDGE.00261006 | Source account directory not found. | Check whether the source account directory exists. |
| EDGE.00261007 | tty for running sudo is not disabled. | The requiretty option is enabled in the sudoers file. This forces sudo to require a tty, but the MgC Agent runs commands over SSH in a non-interactive session, which does not allocate a tty. As a result, sudo fails and returns an error. Solve the problem as follows:
|
| EDGE.00261009 | Command execution timed out in workflow step: SourceEnvCheck. Retry operation if needed. |
|
| Command execution timed out in workflow step: StartUpAgent. Retry operation if needed. |
| |
| Command execution timed out in workflow step: SourceEnvClear. Retry operation if needed. |
|
SMS.xxxx Error Codes
If SMS.xxxx error codes are displayed in the failure cause of a server migration workflow, locate the fault and rectify it by referring to SMS Error Codes or Error Codes and Solutions.
Error Codes for Other Cloud Services
| Error Code | Description | Solution |
|---|---|---|
| Ecs.0319 | Insufficient resources for this ECS flavor. | Go to the Migration Solutions or Migration Plans page, modify the target server specifications or use an existing server as the target server. Then try the workflow again. For details about ECS error codes, see ECS Error Codes. |
| Ecs.0707 | Target server flavor not found or unavailable. | Go to the Migration Solutions or Migration Plans page, modify the target server specifications or use an existing server as the target server. Then try the workflow again. For details about ECS error codes, see ECS Error Codes. |
| Ecs.0005 | Invalid parameter. | Find the corresponding solution in the ECS Error Codes. |
| Vpc.0702 | Invalid parameters. | Check whether the parameter values are valid based on the returned error message. For more information, see: |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
