missing endpointsBesides adding a ton of new features, some customers have reported missing endpoints after a successful upgrade to the new vRealize Automation 7.3 which was released May 16, 2017.  In the Infrastructure tab, Endpoints page does not show any or only few endpoint types and endpoints are missing and in the Management Agent log located at C:\Program Files (x86)\VMware\vCAC\Management Agent\Logs on the primary Model Manager Web node, you see entries similar to:

##Upgrading Infrastructure Endpoints to Endpoint Configuration Service equivalent in Cafe
 "C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe" UpgradeEndpoints -v
 Starting upgrade for endpoint . [ID : b167a417-ee4d-48b3-9742-21868aee04bf] [Name : AWS]
 System.AggregateException: One or more errors occurred. ---> VMware.Cafe.JsonResponseException: System exception.
 at VMware.Cafe.JsonRestClient.<HandleErrorResponse>d__2`1.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
From what I understand this is caused by the asynchronous way scripts are run during the upgrade. In some environments some script run faster than expected and finish before some other scripts do. VMware solved this by running the scripts synchronously and created a new build for vRealize Automation 7.3. So if you have downloaded a version 7.3 before May 28 then re-download a new copy which includes this fix.

To resolve the missing endpoints issue

  1. Log in to the primary IaaS Model Manager Windows machine.
    Note:The primary IaaS Model Manager Windows machine is the machine that has the C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data folder.
  2. Open command prompt in Administrator mode.
  3. Run these commands in the same order:
    • cd C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe
    • vcac-config.exe RegisterCatalogTypesAsync -v
    • vcac-config.exe UpgradeEndpoints -v
Now the endpoints should be visible under Endpoints page of the Infrastructure tab.
This actually ‘registers’ the existing endpoint within the upgraded installation, the endpoint where never really gone. So, if you have manually re-created endpoints you will now see duplicate endpoints. If that is the case, please contact VMware Support to remove the newly added endpoints and note the KB article ID 2150252 in the problem description.