NVP: vProxy registration does not complete with the message "HTTP Error 500: Failed to find virtual machine with IP address"

• A new NetWorker VMware Protection (NVP) vProxy appliance registration does not complete with the error code:

Unable to register NSR VMware proxy 'vPROXY_NAME': Received an HTTP code: 500, libCURL message: "", vProxy message: "Error received from vProxy ="500: Failed to find virtual machine with IP address "vPROXY_IP_ADDRESS".".  

• This error is seen in the NetWorker server's /nsr/logs/daemon.raw file and in the NetWorker Management Console (NMC) Alerts window.
  • See Dell article 22793, NetWorker: How to use nsr_render_log.
• The new vProxy Wizard does not show any VMware resources.
• The NMC's VMware View tab does not show anything, even after performing a VMware View Refresh:

Figure 1: NMC's VMware View tab does not show anything.

The vCenter was added to NetWorker using a customized role. The VMware user is assigned Global Permissions at the vCenter level but Propagate is set to False.

1. Confirm which user account is used to add a vCenter to NetWorker. This is done using nsradmin command on the NetWorker server:

nsradmin
print type: nsr hypervisor

Figure 2: Result of nsradmin command to find username.
 

2. Log in to the vCenter vSphere web client and log in using the administrator@vsphere.local account (or another administrator level account). 
3. Go to Administration > Access Control > Global Permissions and find the user account from step 1.

Figure 3: Administration > Access Control > Global Permissions > User account from step 1

4. Ensure Propagate checked and identify the Role:

Figure 4: Ensure that Propagate is checked off for the Role.

5. Go to Administration > Access Control > Roles and ensure that it shows the correct VMware user account with Propagate set to True.

Figure 5: Administration > Access Control > Roles > User account with Propagate set to True.

6. Return to the NMC and ensure that VMware View loads and is showing VMware resources.

Figure 6: NMC showing that VMware View loads and has VMware resources.

7. If VMware View loads correctly, return to Devices > VMware Proxies and register the vProxy.