Error Service or view is not available for the selected object is displayed when selecting VCF instance in VCF operations UI

Products

• VCF Operations

Issue/Introduction

• Navigating to  Fleet Management → Lifecycle → VCF Instances → Select VCF instance name and the following error is displayed in the UI : 

  Service or view is not available for the selected object. Try again later. Should the issue continue please check the adapter Collection Status.

• vCenter collection status for Infrastructure Management Adapter is Collecting , None when navigating to Inventory → Expand VCF Instances → Select vCenter instance → hover of 3 dots  next to Policy on the right hand side
• /storage/log/vcops/log/config-drift-plugin.log shows error similar to: 

  2026-01-13T11:40:38.535Z ERROR config-drift-plugin 83543 [ops@4413 threadId="5715" threadName="ServerConnection on port 10000 Thread 14"] [com.vmware.vrops.config.manager.ConfigResourceManager.isLicenseValid] - License does not contain required features for vcenter host: <vCenterFQDN>
  2026-01-13T11:40:38.536Z ERROR config-drift-plugin 83543 [ops@4413 threadId="5715" threadName="ServerConnection on port 10000 Thread 14"] [com.vmware.vrops.config.manager.ConfigResourceManager.getVCsFromVCFInstances] - Error fetching VCF-managed VCs for IDs: [############-####-####-#############]java.lang.NullPointerException: Cannot invoke "String.replaceAll(String, String)" because "resourceVersion4D" is null

•  Cloud Proxy has the same name as an analytics node in the VCF operations cluster

Environment

VCF 9.0.x

Cause

The Infrastructure Management adapter's getCollectorId() method matches adapter instances by name rather than by unique identifier/resourceKey.  Example below:

Primary Node Infrastructure Management Adapter: Infrastructure Management Adapter (VCF-Ops-01)
Cloud Proxy Infrastructure Management Adapter: Infrastructure Management Adapter (vcf-ops-01)

Because the code compares names (using case-insensitive matching), the collector's VIM adapter (vcf-ops-01) retrieves the collector ID from the primary node (VCF-Ops-01) instead of its own.

After initial configuration the VCF/vCenter/NSX adapters were moved to the Cloud Proxy (vcf-ops-01), leaving the primary node (VCF-Ops-01) without these adapters, the collector's Infrastructure Management adapter failed to discover them. This happened because it was incorrectly querying the primary node's adapters (which no longer had any of these adapters assigned).

Resolution

1. Open VCF Operations UI
2. Navigate to Administration → Cloud Proxies → Click on the relevant Cloud Proxy name → Click on the pencil icon beside the Cloud Proxy name → Rename the Cloud Proxy so that it does not match the name of any other node in the cluster.