Error: Another VCF Operations instance already provides license and Client plug-in management

Products

• VCF Operations

Issue/Introduction

When attempting to configure vCenter integration in VCF Operations 9.x, the integration may fail during the registration handshake. This issue typically presents as a banner notification in the UI or a specific Java error in the application logs.

Symptoms

• Users receive a banner notification: "Another VCF Operations instance already provides license and vSphere Client plug-in management for this vCenter system."
• Application logs or UI details show the underlying error: Unable to register with Center, Reason: Cannot invoke "String.length()" because "<parameter1>" is null.

Environment

• VCF Operations 9.0 
• VMware vCenter Server 8.0/9.0

Cause

In VCF 9.x, the Fleet Management service is a mandatory architectural component for lifecycle management and license coordination. This error occurs if the Fleet Management appliance is missing, unregistered, or has an inactive API service, resulting in null responses when the integration suite attempts to coordinate asset IDs.

Resolution

Ensure all prerequisites for VCF 9.x management lifecycle are met before performing vCenter integration.

Deploy the VCF Operations fleet management Appliance

1. Deploy the VCF Operations Fleet Management appliance OVF if it is not already present in the environment.  
2. Log in to the VCF Operations Admin UI.
3. Navigate to System Status > Fleet Management.
4. Register the appliance and verify the status is "Active" and "Ready."
5. Ensure the appliance is updated to version 9.0.2.0200 or higher to maintain version compatibility.
6. Re-attempt the vCenter integration toggle for "License and vSphere Client Plug-in management."

Additional Information

• Refer to the VCF 9.x deployment guides.
• Users are recommended to subscribe to this article for updates on this integration requirement.  Subscribe to a Broadcom knowledge article by article or product