Help Center/ Migration Center/ FAQs/ Known Issues and Solutions
Updated on 2025-07-18 GMT+08:00
View PDF
Share

Known Issues and Solutions

Known Issues and Solutions About 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 Windows source servers must at least be 256 MB.

Run the systeminfo command 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.

The SMS migration process is running on the source server. If you want to migrate data again, stop the migration process by running the shutdown.sh script in the /root/Edge/SMS-Agent directory on Linux or by stopping the SMSAgentDeploy process in the Task Manager on Windows. Delete the migration task on the SMS console, return to the workflow, and try the step again.

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; Available: y

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 step.

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 step.

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, the system generates different disk IDs for the server.

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.0317

Insufficient server 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.0401

Download SMS-Agent installation package to source server failed.

Download SMS-Agent from the SMS console, and view the error message displayed during the download. The possible causes usually are network disconnection and failed execution of the download command.

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 /rda/ 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 reported the error message is "SMS-Agent startup failed. For details, view the SMS migration logs on the source server," go to the following directory on the source server to view SMS run logs:
    • Linux: /rda/SMS-Agent/agent/Logs
    • Windows: C:\SMS-Agent-Py2\Logs

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:

  • Linux: /rda/SMS-Agent/agent/Logs
  • Windows: C:\SMS-Agent-Py2\Logs

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.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 the source server runs Linux, go to the /rda/SMS-Agent/ directory and run the restart.sh command to restore the connection. If the source server runs Windows, perform the migration again.

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. If the access key has expired, re-generate a temporary one by referring to Configuring a Temporary Access Key for Huawei Cloud. Then, return to the MgC console and retry the workflow.

SMS-Workflow.0503

Migration task failed. SMS.xxxx

Go to the SMS console to view the error message and solution.

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.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.

Access 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 stop servers in the *** status. Manually stop them and try again.

Access the ECS console, manually stop the server, and retry the workflow.

SMS-Workflow.1204

Change the IP address of server *** failed. Failure cause: ***
  • Failure cause: The IP address has been used.

    Unbind and release the private IP address and try again. If the fault persists, contact technical support or submit a service ticket.

  • Failure cause: The IP address is not in the subnet.

    Use a VPC and subnet that match the private IP address of the source server to create a migration workflow again. If the fault persists, contact technical support or submit a service ticket.

  • Failure cause: Success to change ip, but failed to the same private IP address as the source host

    Try again. If the fault persists, contact technical support or submit a service ticket.

  • Failure cause: Failed to switch the VPC.

    Try again. If the fault persists, contact technical support or submit a service ticket.

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

Parameter "Region" is empty.

Contact technical support or submit a service ticket.

Server-Workflow.0006

Pre-migration check 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 try again.

Server-Workflow.0010

Request *** failed. Failure cause: ***. Try again.

Try again or find a solution here. 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.

Known Issues and Solutions About 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

Parameter "Region" is empty.

Contact technical support or submit a service ticket.

AZ-Workflow.0006

Pre-migration check 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 try again.

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 *** in current state cannot be migrated.

Check whether the source server is normal. If it is abnormal, contact ECS technical support.

AZ-Workflow.0202

AZ *** not found.

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 the task again.

AZ-Workflow.0302

Insufficient server quota.

Increase the server quota for your account and try the task again.

AZ-Workflow.0303

Insufficient vCPU quota.

Increase the vCPU quota for your account and try the task again.

AZ-Workflow.0304

Insufficient memory quota.

Increase the memory quota for your account and try the task 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, but 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

Parameter "disk_infos" 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. Access the CBR console and check whether backups are created.

AZ-Workflow.0502

Failed to associate source server *** with vault ***.

Contact technical support or submit a service ticket.

AZ-Workflow.0503

Vault *** is unavailable (***).

Delete the vault and retry the migration task.

AZ-Workflow.0901

Failed to stop servers in the *** status. Manually stop them and try again.

Access 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.

Access 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 *** not found or unavailable.

Access the IMS console and check the image status. Contact the IMS support to confirm whether the image can be restored. If it cannot, contact technical support or submit a service ticket.

AZworflow.0901

Servers in the *** status cannot be stopped. Manually stop them and try again.

Access the ECS console, manually stop the server, and retry the workflow.

AZworflow.0902

Stopping server timed out. Try again or manually stop the server and try again.

Access the ECS console, manually stop the server, and retry the workflow.

AZ-Workflow.1001

Delete full-ECS image *** 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 backup *** 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

Parameter "server_id" 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 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.

Known Issues and Solutions About 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 migrated cluster is located.

OMS-Workflow.0023

Abnormal node.

Check whether the ports allowed by the security group rules of the cluster node meet the requirements. For details about the requirements, see:

Migration Cluster Resources and Settings

OMS-Workflow.0024

Cluster not found.

Check whether the cluster is 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.0201

Create cluster failed.

Rectify the fault based on the keywords in ErrorReason. Generally, the fault is 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

Workflow creation failed.

Rectify the fault based on the keywords in ErrorReason. Generally, the fault is 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

Cluster deletion failed.

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

Execute migration task failed. Some objects might fail to be migrated.

If the error message is "Migration failed. Failure files exist," rectify the fault by referring to Error Codes.

OMS-Workflow.0402

Migration task execution failed.

Rectify the fault based on the exception cause. If the fault persists, contact technical support or submit a service ticket.

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 external storage device.

Try again. If the fault persists, contact technical support or submit a service ticket.

OMS.01003

Migration source or target unavailable.

Check the connection settings for source and target.

OMS.01006

Object list file too large.

Make sure that the 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 file 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 can, 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.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.04006

Execute migration task failed.

Check the list of failed objects to determine the failure cause.

OMS.03003

AK/SK verification failed. Ensure AK/SK is 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.

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.

Check the connection or network settings.

OMS.03021

Execute command failed.

Check the connection settings for the NAS server or the network settings.

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.

Retry the task 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.

Known Issues and Solutions About MgC

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 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 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 the credential on the Credentials page.

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

Could not query domain names in pagination mode.

Debug 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 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 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 the correct table headers.

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 content.

Check whether the import template was modified or download the template again.

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 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.00020321

Server assessment failed. Matched target specifications not found in target AZ.

Handle this issue by referring to What Can I Do If a Server Assessment Fails and the System Displays a Message Indicating No Proper Specifications Are Matched?

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.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," it indicates an issue with the network connection between the MgC Agent and the source server. Check and restore the network connection and try again. The MgC Agent log file is located at:

  • Linux: /opt/cloud/MgC-Agent/logs/agent-server/run.log
  • Windows: C:\MgC-Agent\logs\agent-server\run.log

MgC.00000045

Command execution by MgC Agent timed out.

This issue is usually caused by network connection problems. Check whether the network settings of the source server meet the requirements. Alternatively, view the MgC Agent (formerly Edge) logs to locate the fault. The logs are located at:

  • Linux: /opt/cloud/MgC-Agent/logs/agent-server/run.log
  • Windows: C:\MgC-Agent\logs\agent-server\run.log

Known Issues and Solutions About Resource Assessment

Error Code

Description

Solution

MgC.00000001

Network connection error.

Try again. If the fault persists, contact technical support or submit a service ticket.

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.00020202

Server assessment failed. Source server ID not found.

The source server ID is missing. Perform a deep collection for the server and try again.

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.00020205

No EVS disk types match source server.

Update the assessment policy and try again.

MgC.00020206

Query IMS images failed.

Try again. If the fault persists, contact technical support or submit a service ticket.

MgC.00020207

Disk type matching source server sold out in target region.

Update the assessment policy and try again.

MgC.00020208

Query EVS AZ availability failed.

Try again. If the fault persists, contact technical support or submit a service ticket.

MgC.00020209

Source server runs Windows. Matched target specifications do not support Windows.

Update the assessment policy and try again.

MgC.00020210

Source server runs Linux. Matched target specifications do not support Linux.

Update the assessment policy and try again.

MgC.00020211

No images match source server specifications.

Query IMS images failed. Try again. If the fault persists, contact technical support or submit a service ticket.

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.

The disk IDs of the source server are invalid. Perform a deep collection for the server 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

Server assessment results not found.

Try again. If the fault persists, contact technical support or submit a service ticket.

MgC.00020215

Modify server assessment results failed.

Try again. If the fault persists, contact technical support or submit a service ticket.

MgC.00020216

Modify server assessment results failed. No matched specifications.

Try again. If the fault persists, contact technical support or submit a service ticket.

MgC.00020217

Modify server assessment results failed. No images match.

Try again. If the fault persists, contact technical support or submit a service ticket.

MgC.00020218

Modify server assessment results failed. Disk size too large.

Downsize disks and try again.

MgC.00020219

Failed to create an assessment for cross-AZ migration. Target AZ is missing.

Select a 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.

Modify the disk size.

MgC.00020229

Server assessment failed. Source server specifications information is missing.

The source server specifications information is missing. Perform a deep collection for the server and try again.

MgC.00020230

Server assessment failed. No proper target specifications.

Update the assessment policy and try again.

MgC.00020231

Server assessment failed. No target specifications meet assessment policy.

Update the assessment policy and try again.

MgC.00020232

Server assessment failed. No proper target specifications meet your preferences.

Update the assessment policy and try again.

MgC.00020233

Server assessment failed. No target specifications meet business scenario.

Update the assessment policy and try again.

MgC.00020343

No images match source server firmware.

Update the assessment policy and try again.

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. or manually 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.

Sms.00070040

Source performance data is missing. Perform a performance collection for source server.

Source server performance data is missing. Perform a deep collection for the server and try again.

Sms.00070041

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.

Sms.00070042

Incorrect CSV file of server performance data.

Launch a performance collection for the server and try again.

Sms.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.

Sms.00070013

Server assessment failed. No matched disk specifications.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070001

Server assessment failed. Internal service error.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.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.

Sms.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.

Sms.00070006

Server assessment failed. No matched images.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070009

Server assessment failed. No matched server specifications.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070040

Server assessment failed. Source performance data is missing.

The source server performance information is missing. Perform a deep collection for the server and try again.

Sms.00070045

Server assessment failed. No matched server specifications.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070041

Server assessment failed. Source performance data is missing.

The source server performance information is missing. Perform a deep collection for the server and try again.

Sms.00070035

Server assessment failed. Source specifications information is missing.

The source server specifications information is missing. Perform a deep collection for the server and try again.

Sms.00070044

Server assessment failed. No matched server specifications in target AZ.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070038

Server assessment failed. No matched server specifications.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070035

Server assessment failed. Source specifications information is missing.

The source server specifications information is missing. Perform a deep collection for the server and try again.

Sms.00070036

Server assessment failed. No matched server specifications.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070037

Server assessment failed. No matched server specifications.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070039

Server assessment failed. No matched server specifications.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

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.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.

Sms.00070017

Server assessment failed. No matched Windows images.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070046

Server assessment failed. No matched images.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070019

Server assessment failed. No matched images.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070018

Server assessment failed. No matched Linux images.

Try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070015

Server assessment failed. Matched disk resources sold out.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070043

Server assessment failed. No matched disk specifications.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070020

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.

Sms.00070021

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.

Sms.00070011

Server assessment failed. No matched server specifications in target AZ.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Sms.00070012

Server assessment failed. Matched server resources sold out in target AZ.

Update the assessment policy and try again. If the fault persists, contact technical support or submit a service ticket.

Known Issues and Solutions About Resource 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.

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.00000140

Other exceptions.

Wait until the server recovers and try again.

MgC.00000144

Other exceptions.

Wait until the server recovers and try again.

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.

MgC.00000148

Check proxy settings.

Ensure that the proxy server is configured correctly.

MgC.00000149

Create client on Alibaba 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.

MgC.00000156

Insufficient permissions.

Ensure that you have the required permissions.

MgC.00000161

Collector server error.

Try again later. If the fault persists, contact technical support or submit a service ticket.

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.

Due to the limited user base of deep collection for databases, containers, and storage, the corresponding plugins are disabled by default. As a result, timeout errors may occur during the task execution. To resolve this, you need to manually start the required plugin. Go to the bin directory in the installation path of the plugin, double-click start.bat to start the plugin. Then perform the collection again. The installation paths of the plugins are as follows:

  • Database: C:\MgC-Agent\tools\plugins\collectors\rda-collector-database\bin
  • Container: C:\MgC-Agent\tools\plugins\collectors\rda-collector-kubernetes\bin
  • Storage: C:\MgC-Agent\tools\plugins\collectors\rda-storage-collector\bin

If the fault persists, contact technical support or submit a service ticket.

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.

Upload a valid credential.

EDGE.00170020

Resource collection failed. Credential not found.

Upload the right credential.

EDGE.00170021

Credential expired.

Extend the validity period of the credential.

EDGE.00170024

The MgC Agent does not support collection using cloud credentials.

Use a valid credential.

EDGE.00170025

Resource collection failed. IP address does not match network range specified for credential.

Upload a credential that matches the IP address range.

EDGE.00260003

Incorrect username or password, or mismatch between IP address and username/password pair.

Check whether the username and password are correct and whether they match the IP address. Ensure that the IP address is correct and try again.

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 (formerly Edge) collector.

EDGE.00030023

The collector was offline.

Check whether the MgC Agent (formerly Edge) collector is online.

SERVER.00000011

The collection scripts were tampered with.

Contact technical support or submit a service ticket.

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:

  • Win32_Processor
  • Win32_Computersystem
  • Win32_DiskPartition
  • Win32_Volume
  • Win32_DiskDrive
  • Win32_networkadapterconfiguration
  • Win32_OperatingSystem
  • Win32_Service
  • Win32_PerfFormattedData_PerfDisk_PhysicalDisk
  • Win32_PerfFormattedData_PerfOS_Processor

SERVER.00000009

Plugin exception.

Try again or refresh the page. If the fault persists, contact technical support or submit a service ticket.

SERVER.00010002

SSH connection failed. Incorrect username or password, or unreachable IP address.

Ensure that the username, password, and IP address are correct.

SERVER.00010009

Algorithm negotiation between client and server failed.
  1. Verify algorithm compatibility for the client and server.
  2. Update the SSH server settings to allow a broader range of algorithms.

If the fault persists, contact technical support or submit a service ticket.

SERVER.00010010

Authentication failed.
  1. Check whether the authentication methods on the client and server are correct.
  2. Check whether multi-factor authentication is enabled on the server. Ensure that multi-factor authentication is disabled.

If the fault persists, contact technical support or submit a service ticket.

SERVER.00010035

Connection timed out.
  1. Extend the request timeout period to 30s for the server.
  2. Check the firewall and security group policies.
  3. Check whether the server restricts the number of concurrent connections.

If the fault persists, contact technical support or submit a service ticket.

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.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.

Known Issues and Solutions About the MgC Agent (Formerly Edge) for Windows

Error Code

Description

Solution

EDGE.00000001

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.

EDGE.00260001

Source IP address unreachable.

Check whether the access IP address is correct.

EDGE.00260002

Source WinRM unreachable.

Make sure that the server credentials added to the MgC Agent match those of the server. The default ports for HTTP and HTTPS via WinRM are 5985 and 5986.

Perform the following steps to check the WinRM status, listening port, and protocol on the source server:

  1. Check the WinRM service status.
    1. Open PowerShell as an administrator. Enter PowerShell in the Windows search box, right-click Windows PowerShell, and choose Run as administrator from the shortcut menu.
    2. Run the following command to check the WinRM service status: 
      Get-Service -Name WinRM
      • If the service status is Running, the WinRM service is started.
      • If the service status is Stopped, the WinRM service is not started. You can run the following command to start the WinRM service and enter y as prompted to confirm the operation: 
        winrm quickconfig
  2. Check the WinRM listening port and communication protocol.

    Run the following command in PowerShell to check the WinRM configuration:

    winrm enumerate winrm/config/listener

    This command displays details about all WinRM listeners, including the listening address, port, and transmission protocol (HTTP or HTTPS).

  3. (Optional) Configure WinRM to use HTTPS.

    If a more secure connection mode is required, configure WinRM to use HTTPS. Ensure that a valid SSL certificate has been installed on the source server.

    1. Run the following command to view the installed SSL certificate and its thumbprint: 
      Get-ChildItem -Path Cert:\LocalMachine\My

      Find a valid SSL certificate and record its thumbprint.

    2. Run the following command to configure WinRM to use HTTPS: 
      New-Item -Path WSMan:\localhost\Listener -Transport HTTPS -Address * -CertificateThumbprint <thumbprint>

      Replace <thumbprint> with the SSL certificate thumbprint you recorded.

    3. Run the following command again to verify that WinRM has been configured to use HTTPS connections: 
      winrm enumerate winrm/config/listener

EDGE.00260003

Invalid source credential.

Check whether the credential provided to the MgC Agent (formerly Edge) is correct.

EDGE.00260004

Insufficient credential permissions.

Check whether the account is in the administrator user group.

EDGE.00260005

Access source WinRM failed.

Check whether the firewall on the source server is disabled.

EDGE.00260006

Necessary components not found at source.

Check whether .NET Framework, WMI, and COM on the source server are damaged.

EDGE.00260007

Edge does not trust source server.
Run the following command on the server where the MgC Agent (formerly Edge) is installed to trust the source server: 
set-item wsman:localhost\\client\\trustedhosts -value *

Known Issues and Solutions About the MgC Agent (Formerly Edge) for Linux

Error Code

Description

Solution

EDGE.00261001

Source IP address unreachable.

Check whether the access IP address is correct.

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 source credential.

Check whether 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.

Comment out the following default values in the source configuration file:

requiretty in the user!/etc/ssh/sshd_config file or Defaults requiretty in the /etc/sudoers file

Issues About 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:

VPC Error Codes