• Cannot log in to the vSphere Data Protection Restore Client.
• The vSphere Data Protection Restore Client returns these errors:
  
  Login failed. Cannot locate login client (VM_IP_address) in VDP.
  Login failed. Cannot locate vm in vCenter
  
  
• In the /space/avamar/var/flr/server_logs/flr-server.log file, you see entries similar to:
  
  INFO [http-nio-8543-exec-7]-vi.VIAccess: Attempting to obtain AVE VM with IP Address: [172.16.2.159] INFO [http-nio-8543-exec-7]-vi.VIAccess: Local Client not found WARN [http-nio-8543-exec-7 security.CustomSecurityService: FLR login attempt failed with error code: [cannot.locate.in.vcenter] com.emc.flr.exceptions.LoginException: CANNOT_LOCATE_VDP_LOGIN_CLIENT xx:xx:xx:xx
  
  Where the IP address of xx:xx:xx:xx belongs to a machine that is not protected by the VDP appliance.

This issue can occur in these situations:

• If virtual machine from which the vSphere Data Protection Restore Client was launched has never been added to a backup job on the VDP appliance used in the URL to access the Restore Client.
• If the network appliance is using network address translation (NAT) and is sending all VDP traffic through a proxy/firewall.
• If the user did not install VMware Tools in the virtual machine trying to access the portal.
• If using Windows Server running vCenter with Microsoft SQL Server 2008 RTM (Version 10.0.1600.22(x64)).
  There is a known issue when a complex query is run that contains aggregate functions, join functions and distinct
  functions in sub queries. This may cause the File Level Restore (FLR) to return incorrect results and display the error:
  
  Login failed. Cannot locate login client (VM_IP_address) in VDP.
  
  
• If there are multiple virtual machines with the same IP address in the vCenter Server inventory.