Known Issues and Solutions

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 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 Edge 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 inSMS 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 /rda/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; and 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.

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

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 reported error message is "System.OutOfMemoryException," see What Can I Do If the StartUpAgent Step Fails and the Error Message "System.OutOfMemoryException" Is Displayed?.
• If the reported error message is " SMS-Agent startup failed, Cause: the SMS-Agent is not running, please try again", you can try again. If the retry fails, rectify the fault by referring to step 2 in What Can I Do If the StartUpAgent Step Fails and the Error Message "System.OutOfMemoryException" Is Displayed?.

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

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

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 server and try again.

Go to 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

The Region parameter is empty.

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

Go to the CBR and IMS consoles to manually delete 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.

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

Go to the CBR and IMS console to manually clear 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 *** 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 target specifications, and create a migration workflow again.

AZ-Workflow.0402

Disk type *** is not available in AZ ***.

Delete the migration workflow, modify the recommended target specifications, and create a migration workflow again.

AZ-Workflow.0403

Disk type *** is sold out in AZ ***.

Delete the migration workflow, modify the recommended target specifications, and create a migration workflow again.

AZ-Workflow.0404

The source server has *** NICs. Flavor *** supports a maximum of *** NICs. Select another flavor.

Delete the migration workflow, modify the recommended target specifications, and create a migration workflow again.

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.

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

AZworflow.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: ***

Go to the IMS console to manually delete these images (whose names start with AZM_Create_Temp__xxx), and try again.

AZ-Workflow.1002

Delete backups failed. Failure cause: ***

Go to the CBR console to manually delete these backups (whose names start with AZM_Create_Temp__xxx), and try again.

AZ-Workflow.1003

Delete vault *** failed. Failure cause: ***

Go to the CBR console to manually delete the vault (whose name starts with AZM_Create_Temp__xxx), and try again.

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.

OMS-Workflow.0002

Storage workflow was abnormal.

Contact technical support or submit a service ticket.

OMS-Workflow.0011

System exception

Contact technical support or submit a service ticket.

OMS-Workflow.0013

Invalid parameters.

Rectify the fault based on the error message.

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 error message. If the fault persists, contact technical support or submit a service ticket.

OMS-Workflow.0202

Start cluster failed.

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

OMS-Workflow.0501

Delete cluster failed.

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

OMS-Workflow.0401

Task failed.

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

OMS-Workflow.0402

Task exception.

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

MgC.01000002

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

Task name already exists.

Enter another task name.

MgC.000030002

Create collection task failed.

Contact technical support or submit a service ticket.

MgC.000030003

Involved collection task not found.

Associate the collection item with another collection task.

MgC.000030004

Collection item already exists.

Check whether the collection item has already been associated with the collection task, or contact technical support.

MgC.000030005

Add collection item failed.

Contact technical support or submit a service ticket.

MgC.000030006

Add data source failed.

Contact technical support or submit a service ticket.

MgC.000030007

Delete collection task failed.

Refresh the task list to check whether the collection task has been deleted, or contact technical support.

MgC.000030008

Delete collection item failed.

Refresh the collection item list to check whether the collection item has been deleted, or contact technical support.

MgC.000030009

Collection task not found.

Refresh the collection task list and check whether the collection task exists.

MgC.000030010

Collection item not found.

Refresh the collection item list and check whether the collection item exists.

MgC.000030011

Add data source failed.

Contact technical support or submit a service ticket.

MgC.000030012

Data source not found.

Refresh the collection item list and check whether the data source exists.

MgC.000030013

Re-collect data source failed.

Refresh the collection item list and check whether the data source exists, or contact technical support.

MgC.000030014

Delete data source failed.

Refresh the collection item list and check whether the data source has been deleted, or contact technical support.

MgC.000030015

Edit data source name failed.

Refresh the collection item list and check whether the data source exists, or contact technical support.

MgC.000030016

Re-collection failed.

Refresh the collection item list and check whether the collection item exists, or contact technical support.

MgC.000030017

Incorrect data source settings.

Check whether the data source settings are correct.

MgC.000030018

Re-collect data source failed.

Check whether the collection uses APIs and the status is completed.

MgC.000030019

Delete data source failed.

Only data sources in the collection failed or completed status can be deleted.

MgC.000030020

Delete collection item failed.

Only collection items in the waiting status can be deleted.

MgC.000030021

Delete collection task failed. There are running collection items.

Refresh the collection item list and check whether there are running collection items. If there are running collection items, the collection task cannot be deleted.

MgC.000030022

The file to import is too large.

The maximum file size allowed is 10 MB.

MgC.000030023

Invalid file name.

Enter a valid file name.

MgC.000030024

Invalid file format.

Import a file in the correct format.

MgC.000030025

Add data source failed. Uploaded file not found.

Check whether the file has been successfully imported or import the file again.

MgC.000040001

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

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

Credential not found.

Check whether the selected credential can be found on the Credentials page.

MgC.000040004

Credential expired.

Update the credential on the Credentials page.

MgC.000040005

Wrong credential type. Select AK/SK credentials.

Select AK/SK credentials.

MgC.000040006

Invalid MSE configuration file.

Check whether the selected credential and regions are correct.

MgC.000040007

Incorrect file format.

Upload a file in the correct format.

MgC.000040008

Could not obtain Nacos accessToken.

Check whether the username and password entered in the configuration information are correct.

MgC.000040009

Could not parse Nacos authentication information.

Contact technical support or submit a service ticket.

MgC.000040010

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

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

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

Invalid AK/SK.

Check whether the AK/SK pair recorded in the selected credential is correct.

MgC.000040014

Could not invoke the Alibaba Cloud Kafka SDK.

Check whether the selected credential and regions are correct, or check whether the Alibaba Cloud Kafka service is enabled for the account that the credential belongs to.

MgC.000040015

Could not invoke the Alibaba Cloud Topic SDK.

Debug API GetInstanceList 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.000040016

Could not invoke the Alibaba Cloud RDS SDK.

Check whether the selected credential and regions are correct, or check whether the Alibaba Cloud RDS service is enabled for the account that the credential belongs to.

MgC.000040017

Could not invoke the Alibaba Cloud RDS schema SDK.

Debug API DescribeDatabases 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.000040018

Create Alibaba Cloud SLB SDK client failed.

Check whether the selected credential and regions are correct.

MgC.000040019

Uploaded file contains invalid data.

Enter valid values.

MgC.000040020

Uploaded file failed the verification.

Contact technical support or submit a service ticket.

MgC.000040021

Required fields are missing in uploaded file.

Specify required fields.

MgC.000040022

Table headers of uploaded file are incorrect.

Enter a correct table header.

MgC.000040023

Table headers of uploaded file are invalid.

Check whether non-customized table headers in the template have been modified.

MgC.000040024

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

Invalid file content.

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

MgC.000050001

Maximum tags reached.

Delete unnecessary tags and try again.

MgC.000050002

Add tag failed.

Contact technical support or submit a service ticket.

MgC.000050003

Tag not found.

Check whether the tag is available.

MgC.000050004

The tag has been associated with resources.

Select another tag or dissociate from resources.

MgC.000050005

Update tag failed.

Contact technical support or submit a service ticket.

MgC.000050006

The parameter for querying the tag set is empty.

Set the tag query parameters.

MgC.000050007

Associate tag with resources failed.

Contact technical support or submit a service ticket.

MgC.000050008

The tag was not associated with the resources

Check whether related resources and the tag have been associated, or contact technical support.

MgC.000060001

ID not found.

Contact technical support or submit a service ticket.

MgC.000060002

Modify data failed.

Contact technical support or submit a service ticket.

MgC.000060003

Data import failed.

Contact technical support or submit a service ticket.

MgC.000060004

Name already exists.

Enter another name.

MgC.000060005

File upload failed.

Contact technical support or submit a service ticket.

MgC.000060006

File download failed.

Contact technical support or submit a service ticket.

MgC.000060007

Uploaded file not found or expired.

Upload a new file, or rename the file and upload it again.

MgC.000060008

Producer and consumer in a raw in sheet "MQ" are in different environments.

Check whether the producer and consumer environments in the MQ sheet of the imported file are consistent.

MgC.000060009

Producers or consumers specified in sheet "MQ" are not found in sheet "Application".

Ensure that the producer and consumer services or microservices in the MQ sheet have been supplemented in the Application sheet of the imported file.

MgC.000060010

Column "MICROSERVICE" in sheet "Application" is required.

Add microservices in the Application sheet to the imported file.

MgC.000060011

Columns "PRODUCER" and "CONSUMER" in sheet "MQ" are required.

Add the producer and consumer services or microservices to the MQ sheet of the imported file.

MgC.00180036

Daily workflow quota exhausted.

Switch to another project or delete a completed workflow in the current project.

MgC.00180037

Maximum resources for a workflow reached.

Ensure that no more than 100 resources are included in the workflow.

MgC.00180038

Too many resources being migrated.

Switch to another project or wait until in-progress workflows to complete.

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.