===== [V7] ISSUE:"Failed to restore "New Virtual Machine". Reason = "Fail to set entity permission. Error=Unknown error from class "com.vmware.vim25.UserNotFound" when restoring a guest VM to another VMware ESXi host =====
Article ID: 5265
Reviewed: 2017-08-07

Product Version:
AhsayOBM: 7.5.0.0 to 7.x
OS: All

ATTENTION 1st January, 2022: v7 officially End-of-Life [details] ===== Problem Description ===== When performing a restore (Run Direct or traditional restore) to another VMware ESXi host the following error message is shown:

No. Type Timestamp Log
* ... ... ...
* erro YYYY/MM/DD hh:mm:ss Failed to restore "New Virtual Machine". Reason = "Fail to set entity permission. Error=Unknown error from class "com.vmware.vim25.UserNotFound""
* info ... ...

Cause:
This is a known issue on AhsayOBM when restoring a guest VM to an alternate location or standby VMware host.

This issue occurs if the VMware user account assigned to the guest VM on the original VMware host does not exist on the standby VMware host.

===== Resolution ===== To workaround this issue:

  1. Login to the standby VMware host using vSphere using root credentials.


  2. Check the vSphere [Recent Task] list to identify which user accounts is missing on the VMware host.


  3. Go to [Inventory]>[Users] tab.


  4. Right click and [Add] the missing user account.


  5. After adding the new account, run the restore again.
===== Keyword ===== VMware ESXi, vCenter, Run Direct, user permission, user groups, alternate location, vSphere, restore