Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Items in vRA show no fields after the vCAC CAFÉ endpoint in vRO was deleted and recreated (53910)

Last Updated: 4/28/2018Categories: TroubleshootingTotal Views: 8541Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You can see the items in vRA but if you open them they have no fields.

If you look at the resource data of the catalog resources, you see vcoId ( in the format <hostId>/<objectId> which refers to a vCAC CAFE host that does not exist.

Cause

vRA looks up objects based on both the host Id and object Id. Once the host ID is different, objects cannot be retrieved.

Resolution

This is a known issue.
Currently, there is no resolution.

Note: Take a Snapshot of your vRealize Orchestrator appliance before following the steps below.

To work around the issue:

Open the Orchestrator client and go to the Design tab.

Navigate to Resources > Library >vCAC > CAFE.

Export the configuration of an existing host for the same vRA tenant. If you do not have one, create a new host first by running the Add a vRA Host workflow.

Find the id of the deleted host. You can see it by looking at the vcoId field in the resource data of broken catalog resources. Resource data for items can be seen in the vRO inventory. The host id is the part of the vcoId before the forward slash.

Replace the id of the exisiting host with the id of the deleted host in the configuration file you exported in step 3 . Be careful to replace it both under the id.parts.a.string and id.stringRepr tags. Change the name to the id of the deleted host as well. Import the configuration from the new file.

Reboot vRO and verify a new endpoint can be seen in the inventory and has the id of the delete host. Check that the objects are no longer broken in vRA Items.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Application Services

VMware Aria Automation Orchestrator

Related Versions:

VMware vRealize Orchestrator 6.0.x

VMware vRealize Application Services 6.2.x

Take Our Survey

Support Assistant