Resolving License Exceed Issues in APM Plugin (Failover Setup)
Overview
In failover (Primary–Secondary) deployments of the APM Plugin, license exceed or license validation issues may occur in the secondary APM Plugin server after a switchover. This typically happens when the license file is not properly applied across all secondary APM Plugin servers.
Observed Behavior
- License exceed error displayed in APM Plugin
- Monitoring stops after failover
- Features become restricted due to license validation failure
- Mismatch in license usage between Primary and Secondary servers
Cause
Note: License validation is performed locally on each APM Plugin server.
If the AdventNetLicense.xml file in the Secondary server is:
- Missing
- Outdated
- Different from the Primary server
License-related errors may occur during or after failover.
Resolution Steps
Primary Method: Apply License via UI (Recommended)
Recommended: Apply the same license used in the Primary server directly through the Secondary APM Plugin UI.
- Login to the Secondary APM Plugin server UI.
- Click on Apply License (Refer sample screenshot below).
- Upload the license file present in the Primary server ( <OPM_Home>/AppManager/working/classes/AdventNetLicense.xml ).
Example of license exceed message displayed in APM Plugin UI
Alternate Method: Manual License File Replacement
If applying the license via UI is not feasible, follow the manual method below:
- Copy <OPM_Home>/AppManager/working/classes/AdventNetLicense.xml from the Primary server.
- Replace it in the same location on the Secondary server (<OPM_Home>/AppManager/working/classes/ ).
- Restart the OPM service on the Secondary server.
Note:
- If the file
<OPM_Home>/AppManager/working/classes/ApmPlugin_AdventNetLicense.xmlis present on the Primary server, please copy it as well and replace it in the same location on the Secondary server.
Additional Information
Warning: If the license file is not consistent across servers,
license exceed errors may recur after switchover.
- Ensure license file consistency across all APM Plugin servers.
- If the issue persists, contact support and share the latest APM Support Information File (SIF).
New to ADSelfService Plus?
Related Articles
Troubleshooting Applications Manager Plugin database migration failure after service pack upgrade of OPM and APM plugin
When upgrading OpManager from version 12.6.xxx to 12.7.xxx and updating the APM Plugin to 1651x, particularly when using Postgresql as the backend database, an essential one-time migration occurs. This migration involves moving our backend Postgresql ...Upgrade guide for OpManager v 12.7 and APM Plugin
After downloading the service pack for OpManager and the compatible service pack for Applications Manager Plugin (APM Plugin) to OpManager installed server, start the upgrade process for OpManager and APM Plugin by following the steps below: Note: If ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...Troubleshooting Applications Manager Plugin (APM Plugin) issues in OpManager/OpManager Plus
Browse through the following topics to troubleshoot the actual problems encountered in Applications Manager Plugin (APM Plugin) for OpManager and resolve them accordingly: APM Plugin is down abnormally If the APM plugin is installed as a service, ...APM Plugin migration from 32-bit to 64-bit installation
To migrate APM Plugin from 32-bit to 64-bit installation, follow the steps given below: Perform a database backup of the 32-bit APM Plugin setup and place it anywhere outside the Applications Manager folder directory. Make sure to take a VM snapshot ...