Download PDF
Download page License Errors and Troubleshooting.
License Errors and Troubleshooting
This page covers license errors and troubleshooting in the Controller UI.
The Controller UI for observing and managing licenses differs based on the AppDynamics licenses you purchased. If you purchased licenses in the Infrastructure-based Licensing model, your UI displays usage data based on a unified package metering unit, compared to licenses within the Agent-based model, which displays data based on an agent metering unit. If you want to learn more about licensing models, see AppDynamics Licensing.
License Errors
License error notifications display in the Controller next to Settings 
. This table below lists possible error messages and their causes.
| Error Message | Cause |
|---|---|
| Invalid license key | Cannot find allocation by license key because of an invalid license key. May be caused by a license rule mismatch or typo in the configuration, or missing authorization headers when connecting to the Controller. |
| Cannot match filter conditions for allocation <allocation-name> (Id = <allocation-id>): hostId = <host-id>, appId = <app-id>, appName = <app-name> | Reported application or server does not match conditions defined in the allocation rule (application/server scope). |
| License limit exceeded for License Rule "<allocation-name>" (Id = <allocation-id>) of Account Id = <account-id>. AgentType: <agent-type>, Host: <host>, Considered packages: <considered-packages>, Application: <application-name>, Node Id: <node-id>. | License limit was exceeded on the allocation rule level. There are no available units across any of the packages provisioned for the allocation rule. |
| License limit exceeded for Account Id = <account-id>. License Rule: <allocation-name>, AgentType: <agent-type>, Host: <host>, Considered packages: <considered-packages>, Application: <application-name>, Node Id: <node-id>. | License limit check passed for the allocation rule level but was exceeded on the system (Controller) level. |
| System account license limit exceeded for <package-name>. Account Id: <account-id>, License Rule: <allocation-name>, AgentType: <agent-type>, Host: <host>, Considered packages: <considered-packages>, Application: <application-name>, Node Id: <node-id>. | License limit checks passed for the allocation rule and account level but was exceeded on system (Controller) level. |
Troubleshoot Licenses
Licensed Agent Not Registering
If a licensed agent cannot register with the Controller:
- Check that the user account has a product license for the relevant agent type.
- If the user account has license rules defined, verify that the rules have the correct number of license units allocated. See License Rules Best Practices.
To change the number of allocated units in a rule:- Click Settings
> License > License Rules. - Open a rule and click Edit
. - Under License Allocation, change the number of licenses and apply the change.
- Click Settings
License Errors
License error notifications display in the Controller next to Settings . This table below lists possible error messages and their causes.
| Error Message | Cause |
|---|---|
<Agent type String> agent on host "<host name>" is not authorized to report to application "<application name>". Reason: Missing access key. or Agent license request denied. Agent type: <agent type string>; Node: <node name>; Tier: <Tier name>; Application: <application name>; Host: <hostId>; Reason: Missing access key. | Access key is missing from the agent request. For example, if the Controller returns a
Node (tier) names are only provided for app agents. |
| Agent license request denied. Agent type <agent type string>; Node: <node name>; Tier: <Tier name>; Application: <application name>; Host : <hostId>; Reason: Access Key used is not account access key. | Access key provided is not the account access key for the Database Agent. |
Agent license request denied. Agent type: <agent type string>; Node: <node name>; Tier: <Tier name>; Application: <application name>; Host : <hostId>; Reason: Invalid access key. or <Agent type String> agent on host "<host name>" is not authorized to report to application "<application name>". Reason: Invalid access key. | The license rule that was retrieved for a specific access key provided by the agent, is incorrect. This error may also occur when there is a misconfiguration. For example, the access key was updated directly in database but the caches did not include that update, then an access key mismatch will occur.
Node (tier) names are only provided for app agents. |
| Agent license request denied. Agent type <agent type string>; Node: <node name>; Tier: <Tier name>; Application: <application name>; Host : <hostId>; License Rule: <license rule name> ; Reason: No license available. | No licenses are available during agent registration.
Node (tier) names are only provided for app agents. |
<Agent type String> agent on host "<host name>" is not authorized to report to application "<application name>". The host or application is not included in the scope of license rule "<license rule name>". or <Agent type String> agent on host "<host name>" is not authorized to this Controller.The host or application is not included in the server scope of license rule "<license rule name>". | Agent is configured with an access key that is restricted to particular hosts or applications. |
Troubleshoot Licenses
If a licensed agent cannot register with the Controller:
- Check that the user account has a product license for the relevant agent type.
- If the user account has license rules defined, verify that the rules have the correct number of license units allocated. See License Rules Best Practices.
To change the number of allocated units in a rule:- Click Settings > License > Rules.
- Open a rule and click Edit .
- Under License Allocation, change the number of licenses and apply the change.
- Click Settings