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

David Lane 1 Reputation point
2022-01-24T17:03:54.83+00:00

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://learn.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
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
717 questions
{count} votes

2 answers

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 37,686 Reputation points Microsoft Employee
    2022-02-23T19:31:50.727+00:00

    @David Lane 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

    0 comments No comments

  2. Craig Rickett 1 Reputation point
    2022-11-16T10:48:36.887+00:00

    This can also be caused if one or more Azure Migrate appliances are using the same IP address.

    0 comments No comments