NetWorker: vCenter plug-in and VCUI login fails with "vCenter not registered with NetWorker server"

• Logging in to the NetWorker plug-in in the VMware vCenter web client or through the NetWorker vCenter User Interface (VCUI) returns an error stating "vCenter not registered with NetWorker server"

• The vcui.log on the NetWorker (authc) server shows:

The vCenter server was added to NetWorker using its shortname alias. The NetWorker VMware Integration Guide states that using a different FQDN alias or shortname alias for the vCenter server when adding it to NetWorker is not supported for the vCenter plug-in.
The VMware Integration Guide is available through: https://www.dell.com/support/home/product-support/product/networker-family/docs

It is not possible to use the vCenter web client's NetWorker plug-in or the vCenter User Interface (VCUI) if the vCenter was added to NetWorker using its shortname alias. When a vCenter is added to NetWorker, the vCenter name is embedded into any backups performed; meaning in order to perform restores from the vCenter, it must exist in NetWorker. The name exists as a client identifier for the vCenter server in the database and doesn't utilize DNS to resolve the shortname to the FQDN. If the shortname "NSR Hypervisor" resource is removed from NetWorker in order to add it back with FQDN you cannot recover any VM backups taken from the old "shortname" entry. A duplicate entry for the vCenter using FQDN cannot be added if an entry using the shortname already exists. This issue was raised to NetWorker engineering and there was no supported method determined for correcting this configuration issue.

The NetWorker vCenter plug-in and VCUI are not required for performing VMware backup/restore operations; the following user interfaces can still be used if the vCenter was added using its shortname alias:

• NetWorker Management Console (NMC) - java based console.
• NetWorker Web User Interface (NWUI) - HTML based console.