Operational Defect Database
BugZero updated this defect 50 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 90502
SRM - There are not enough licenses installed to perform the operation
Last update date:
3/30/2024
Affected products:
Site Recovery Manager
Affected releases:
8.x
Fixed releases:
No fixed releases provided.
Description:
Symptoms
SRM displays the error below when performing some operations listed here -ERROROperation FailedThere are not enough licenses installed to perform the operation.12/1/22, 12:29:43 PM -0700 When the current SRM license key has expired Protecting an existing VM in Protection GroupAdding a new VM to Protection Group Performing a failover, failback or re-protect activity NOTE : Site Recovery Manager preserves the license only during an upgrade within the same version, for example, from version 8.3.0.x to version 8.3.1, or from version 8.4.0.1 to version 8.4.0.2. During an upgrade to a different version, for example, from 8.4 to 8.5 or later, Site Recovery Manager reverts to an evaluation license. After the upgrade, you must reinstall your Site Recovery Manager license key.Information That Site Recovery Manager Upgrade Preserves
Cause
Multiple SRM solutions found under vCenter Licenses > Assets > Solutions Improper license key assigned to the SRM solution Insufficient license assigned to the SRM solution SRM solution is still running with an evaluation key (Appropriate license key is still not assigned to SRM solution)Check if the license key has a hard limit on the number of CPUs or VMs it can protect and whether you are hitting that limit, in which case you may have to procure a new license key or talk increase the limit of the existing license by talking to your sales rep or VMware license team.
Resolution
NOTE: The following steps must be performed on Production & Recovery sites. Remove all the SRM solutions from vCenter Licenses > Assets > Solutions Restart srm-server service (Appliance) OR VMware vCenter Site Recovery Manager Server service (Windows); doing this will allow SRM solution to repopulate in vCenter. If step 2 fails - Reconfigure SRM (Appliance) OR run a modify install (Windows) for SRM to re-register its solution with vCenter. Assign a valid SRM license key to the solution, this should resolve the issue.
