vRealize Business for Cloud fails to authenticate to vRealize Operations inconsistently
search cancel

vRealize Business for Cloud fails to authenticate to vRealize Operations inconsistently


Article ID: 339429


Updated On:


VMware Aria Suite


  • User has invalid permissions or credentials when vRealize Business for Cloud attempts to collect data from vRealize Operations in spite of all these criteria are matched:
    • vCenter Sever user has all of the necessary permissions.
    • The Managed Object Browser registration is up to date when checked.
    • vRealize Operations collections are succeeding with the same user for another vCenter Sever.
    • The global permission that is required is set in vRealize Operations.


VMware vRealize Business for Cloud Standard 7.x


This issue occurs because when the MOB registration was updated, it did not set the vCenter Sever for which the vRealize Operations collections are failing as an authentication source. To verify this, check the authorization sources from the vRealize Operations Manager main node by running this command from the command line interface:

 /usr/lib/vmware-vcops/cassandra/apache-cassandra-2.1.8/bin/cqlsh --ssl --cqlshrc /usr/lib/vmware-vcops/user/conf/cassandra/cqlshrc -e "select * from globalpersistence.auth" | grep VCHOST | awk -F'|' '{print $(NF-2)}' | sed -re 's/ *//g'

Note: If vCenter Sever GUID is missing in the output, you must proceed to the resolution.


To resolve this issue, remove the registration entirely.

To remove the registration:
  1. Log in to vRealize Operations Manager:
  2. Navigate to AdministrationSolutions >  vSphere.
  3. Select the vSphere adapter for the vCenter sever that is failing.
  4. Click the Configure button.
  5. Select Manage Registrations.
  6. Delete the old registration entirely before re-registering the adapter instance.
  7. After the new registration is complete select Status in the top right of vRealize Business for Cloud.
  8. Under vCenter Data Collections select Update Now.
vRealize Operations Manager should now allow vRealize Business for Cloud to authenticate to it. We can tail /var/log/vrb/data-collector/itfm-vc-dc.log file to verify successful collection.

If the issue persists, file a support request with VMware Technical Support and note this article ID (000051158) in the problem description. For more information, see How to Submit a Support Request.

Additional Information

The impact and risks of performing this are minimal. Removing the registration of vRealize Operations from vCenter only impact Usage Meter, vRealize Business for Cloud, and specific adapters. The connection will be repaired immediately.

Note:This article assumes that troubleshooting steps done in Troubleshooting vCenter Server data collection failure in vRealize Business for Cloud have been completed.