Troubleshooting issues with mapping multiple users in vCenter
This topic describes how to troubleshoot the issue that you encounter when working with multiuser mapping for managing vCenters.
Issue | Workaround |
|---|---|
The error Could not find automation principal with ID '2' occurs when attempting to browse the vCenter server using a mapped Automation Principal that lacks the necessary access permissions. | As an RBACAdmin, provide read permission to the mapped Automation Principal for the specified roles and the vCenter server. |
When you attempt to browse the vCenter, the error appears: Failed to establish connection either because of invalid web service details or web service is down. Check logs for further details. : on host <VCName> and proxy host <ProxyServerName>
| As an RBACAdmin, perform one of the following tasks:
|
The following error appears when you try to browse vCenter with a non BLAdmins role. Access Denied Role.Read on <Role_name> | As an RBACAdmin, provide read permission to non BLAdmins role. |
The error No access allowed for Property: VIRTUAL_ENTITY_CONNECTION appears in the following situations:
| As an RBACAdmin, perform the following steps:
|