vRanger GUI Crashes when viewing backup groups (4039654)

This has been seen to be caused by inconsistent naming of hosts within vRanger.

To verify whether this is your issue, go to the "My Inventory" panel and observe the naming of the hosts within the inventory. They should be entered by either IP address or by FQDN (fully qualified domain name).

Remove the vCenter from the vRanger inventory.

1. If no hosts remain in the inventory, that's ok. Inconsistent naming is probably not the issue.
2. If hosts remain, are they still displaying the same name? If not, the inconsistent name could be the issue. This is usuallly caused by credentialing the hosts within vRanger. When hosts are credentialed, vRanger can access the internals of the host and read the name settings on the hosts.

If you see this happening, you can do one of two things.

1. Remove the host from vCenter and readd under a different name. Before doing this, you should vacate each host so that the VMs on the host will not receive no IDs when added back to vCenter.

2. Remove credentials from the hosts. vRanger will then have no access to the internal host settings and will just use the name by which the host was joined to vCenter, not the internally configured name.

3. In some cases, no name has been assigned to to the host, so the host will simply show up as localhost. To fix this, in vCenter, select the host, select the Configuration tab, and configure DNS and Routing with the proper hostname and domain.

When complete, re-add the vCenter to your vRanger configuration.