6.2

Table Of Contents
Problem
Data collection fails for a vSphere endpoint. The log messages return an error similar to the following:
This exception was caught: The attached endpoint
'vCenter' cannot be found.
Cause
The endpoint name you configure in vRealize Automation must match the endpoint name provided to the
vSphere proxy agent during installation. Data collection fails for a vSphere endpoint if there is a mismatch
between the endpoint name and the proxy agent name. Until an endpoint with a matching name is
configured, the log messages return an error similar to the following:
This exception was caught: The attached endpoint
'expected endpoint name' cannot be found.
Solution
1 Select Infrastructure > Monitoring > Log.
2 Look for an Attached Endpoint Cannot be Found error message.
For example,
This exception was caught: The attached endpoint
'expected endpoint name' cannot be found.
3 Edit your vSphere endpoint to match the expected endpoint name shown in the log message.
a Select Infrastructure > Endpoints > Endpoints.
b Click the name of the endpoint to edit.
c Enter the expected endpoint name in the Name text box.
d Click OK.
The proxy agent can commute with the expected endpoint and data collection is successful.
Create a vSphere Endpoint with Networking Integration
IaaS administrators create endpoints that allow vRealize Automation to communicate with the vSphere
environment, a vCloud Networking and Security or an NSX instance.
Note You do not have to create endpoints one at a time. You can also create endpoints by importing
them from a CSV file.
Prerequisites
n
Log in to the vRealize Automation console as an IaaS administrator.
IaaS Configuration for Virtual Platforms
VMware, Inc. 19