Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
786 questions
Azure Migrate: Error 661 when performing test migration
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 59%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
Dan McShane
1
Reputation point
Hi, I'm receiving the following error when attempting to test migrate a VMware server using Azure Migrate. Is someone able to assist?
Thanks,
Error ID
661
Error Message
The requested operation failed with reason: 'VM Provisioning Failed. VM Name: , OperatingSystem: , VM Size: Standard_E2s_v3, Status: Provisioning failed : ProvisioningState/failed/OSProvisioningTimedOut : OS Provisioning for VM 'am-tempaa2a7174' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. For details on how to check current provisioning state of Windows VMs, refer to https://aka.ms/WindowsVMLifecycle and Linux VMs, refer to https://aka.ms/LinuxVMLifecycle. , VM running : PowerState/running : , .'.
Possible causes
An internal operation involving creation of temporary VM created by Azure Site Recovery to configure failover/migrated VM failed to provision in time.
Recommendation
Retry the operation. If the issue persists, contact support.
First Seen At
1/5/2021, 8:52:22 PM
Error ID
539
Error Message
The requested action couldn't be performed by the 'VMwareCbt' Replication Provider.
Possible causes
The Provider action failed. Check other errors for more information.
Recommendation
Resolve the issue and retry the operation.
{count} votes
-
SadiqhAhmed-MSFT 44,336 Reputation points Microsoft Employee2021-01-06T13:38:16.367+00:00 @Dan McShane Can you pick a different VM size other than "Standard_E2s_v3" and re-run replication?
-
Dan McShane 1 Reputation point
2021-01-06T13:48:41.837+00:00 Hi Sadiqh. After changing the size, are you saying I should stop the replication, and fully re-replicate the machine? Or simply start the test migration again?
Thanks! -
SadiqhAhmed-MSFT 44,336 Reputation points Microsoft Employee
2021-01-06T13:53:28.18+00:00 @Dan McShane Yes, start test migration once again and it should succeed.
-
Dan McShane 1 Reputation point
2021-01-06T15:20:09.5+00:00 Hi, this did not resolve the issue unfortunately.
Sign in to comment
Sign in to answer