Resolving License Exceed Issues in APM Plugin (Failover Setup)

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

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:
  1. If the file <OPM_Home>/AppManager/working/classes/ApmPlugin_AdventNetLicense.xml is 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).