question

DavidLane-4954 avatar image
0 Votes"
DavidLane-4954 asked SadiqhAhmed-MSFT commented

Error: The operation VirtualDiskSnapshotOpen failed with the error 'Unknown error' [Unknown error]" 180001

I'm trying to get agentless replication working for migrating some VMs from vmware to azure, but getting this very unhelpful error:

Error ID 180001
The last replication cycle for the virtual machine 'vmName' failed. The operation VirtualDiskSnapshotOpen failed with the error 'Unknown error' [Unknown error]


The only reference to that Error ID is https://docs.microsoft.com/en-us/troubleshoot/system-center/dpm/vnext-dpm-error-codes and https://social.technet.microsoft.com/wiki/contents/articles/10183.azure-backup-errors-and-events-portal.aspx, with the message "The selected recovery point does not exist. Choose another recovery point."

I have granted the account all the requested permissions in vCenter and can see it creating, removing and consolidating snapshots, so I really can't understand the problem. I haven't seen a solution posted to this anywhere, can anybody help?

azure-migrate
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @DavidLane-4954 Sorry for the inconvenience this must have caused!

Please make sure that this VM doesn't have snapshots
Check if storage vMotion occurred
ESX of the virtual machine is connected
Validate gateway services on Azure Migrate side as mentioned on the article below.

More information
https://docs.microsoft.com/en-us/azure/migrate/troubleshoot-changed-block-tracking-replication#disposeartefactstimedout

0 Votes 0 ·

No snapshots as portal prevents you from setting up a replication when there are
No storage vMotions
test-netconnection exi host -p 902 successful
Updated the VDDK to 6.7.3 EP1 released 2021-10-14, rather than the one linked to in the setup wizard which is from 2018
Used storage explorer to upload a file to a test blob container in the migrategwsa storage account
Connected to Service Bus with Explorer and 'peeked' at messages, not connection failed message
test-netconnection Key Vault URI -P 443 successful

Still getting the same replication error message.

0 Votes 0 ·

I think the issue could be from VMware side not on Azure migrate side. May be a compatibility issue. For now, I suggest reaching out to Azure technical support team by raising a support request for further investigation. Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.

0 Votes 0 ·
Show more comments

Thanks for the suggestion to check the password for symbols for the account used to log in vcenter, I can’t believe it but that worked! I had a £ in the password. The VM synced and I ran a successful test migration. I hope you will update the official documentation as I think lots of people use symbols in their passwords as a matter of course nowadays.

0 Votes 0 ·

Thanks for the feedback. We will work with the content team and try to add that point in the documentation.


If the response helped, do "Accept Answer" and up-vote it

0 Votes 0 ·

1 Answer

SadiqhAhmed-MSFT avatar image
0 Votes"
SadiqhAhmed-MSFT answered

@DavidLane-4954 Thanks for the confirmation. Glad to know the suggestions below helped solve the issue.

Sharing the solution with broader community for better visibility

Please check if you are using any special character in vcenter account password, which was set up for this purpose.
If yes, please update the password without any special characters and see if the replication cycle succeeds.


If the response helped, do "Accept Answer" and up-vote it

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.