License error message: There is no valid license for Agent
Article ID: 89885
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
License error message: There is no valid license for Agent
Environment
Release: AOATAM99000-8.0-Automic-One Automation Tools-Application Manager
Component:
Component:
Resolution
Detailed Description and Symptoms
Investigation
Solution
When attempting to start an agent, the following error message occurs:
U0034036 There is no valid license for Agent '<Agent name>' (License class '#', license category '<category>', platform 'EX.OS.*').
Investigation
Open the System Overview in Client 0 and choose License. Look for the Platform, Class, and Category that matches the error message. Count is the amount of agents that are allowed to run. Processors is the amount of processors for that Platform, Class, and Category that are allowed to run. The Used (Host) column is also very important to look at it. It will have a number like:
00004 (00020)
The first number is the number of agents in that Platform, Class, and Category that are currently running. The second number is the number of processors those agents are using. In the example above, there are 4 agents running on 20 processors.
There are a few reasons that the "no valid license" error will occur. Either there are not enough licenses for another agent to be added to the count, or there are not enough licenses for the processors to be added. These are outlined below:
*) If in the example above, the number in the "Count" column is 4 and another agent is started, it will receive this error because my Used (Host) column shows that 4 agents are already started.
*) If in the example above, the number in the "Count" column is 5 and the number in the "Processors" column is 20 and another agent is started, it will receive this error because the Used (Host) column shows that 20 processors are already being used.
*) If in the example above, the number in the "Count" column is 5 and the number in the "Processors" column is 22 and another agent is started that receives this error, it is important to double check how many processors that agent might be using. If it has 4 processors, then this will be too many (20 + 4 is 24 which goes above 22) and will cause the error.
Other investigation:
*) Be sure the category in the error message matches the one you are attempting to use
*) Check your license_class= setting in the agent's ini file to be sure you are using the correct class
00004 (00020)
The first number is the number of agents in that Platform, Class, and Category that are currently running. The second number is the number of processors those agents are using. In the example above, there are 4 agents running on 20 processors.
There are a few reasons that the "no valid license" error will occur. Either there are not enough licenses for another agent to be added to the count, or there are not enough licenses for the processors to be added. These are outlined below:
*) If in the example above, the number in the "Count" column is 4 and another agent is started, it will receive this error because my Used (Host) column shows that 4 agents are already started.
*) If in the example above, the number in the "Count" column is 5 and the number in the "Processors" column is 20 and another agent is started, it will receive this error because the Used (Host) column shows that 20 processors are already being used.
*) If in the example above, the number in the "Count" column is 5 and the number in the "Processors" column is 22 and another agent is started that receives this error, it is important to double check how many processors that agent might be using. If it has 4 processors, then this will be too many (20 + 4 is 24 which goes above 22) and will cause the error.
Other investigation:
*) Be sure the category in the error message matches the one you are attempting to use
*) Check your license_class= setting in the agent's ini file to be sure you are using the correct class
Solution
There are a few methods to follow for a solution:
1) Follow the steps above to be sure that the license has enough agents allowed for the count and processors. If there are not, please contact Support.
2) If the count and processors are correct, check the Category for the agent and make sure it is correct. Sometimes licenses will have a "Production" category and another category like "Production-Other". If the agent is supposed to be "Production-Other", but is showing up as "Production", take the steps below to change this:
*) Go to System Overview in Client 0 and choose Agents (executors in 6.00A) and then right-click on the agent throwing the error and choose "Edit".
*) Go to the Attributes tab of the agent and choose the correct Category from the drop-down menu.
3) Be sure the correct license_class= setting is being used in the ini file
Problem persists:
If the above steps were tried and the error still persists, please contact Support and send the following:
*) In Client 0, go to System Overview, License, and send us a screenshot of the platform EX.OS.UNX, Category Production. We're mostly interested in the Platform, Category, Count, Processors, and Used (HOST) column.
*) Also in Client 0 System Overview, go to the executors and sort by JCL Variant. Here, we're most interested in the Name, JCL Variant, HW, SW, License Class, and License Category
*) Finally, we'll need the full executor log from a failed startup.
1) Follow the steps above to be sure that the license has enough agents allowed for the count and processors. If there are not, please contact Support.
2) If the count and processors are correct, check the Category for the agent and make sure it is correct. Sometimes licenses will have a "Production" category and another category like "Production-Other". If the agent is supposed to be "Production-Other", but is showing up as "Production", take the steps below to change this:
*) Go to System Overview in Client 0 and choose Agents (executors in 6.00A) and then right-click on the agent throwing the error and choose "Edit".
*) Go to the Attributes tab of the agent and choose the correct Category from the drop-down menu.
3) Be sure the correct license_class= setting is being used in the ini file
Problem persists:
If the above steps were tried and the error still persists, please contact Support and send the following:
*) In Client 0, go to System Overview, License, and send us a screenshot of the platform EX.OS.UNX, Category Production. We're mostly interested in the Platform, Category, Count, Processors, and Used (HOST) column.
*) Also in Client 0 System Overview, go to the executors and sort by JCL Variant. Here, we're most interested in the Name, JCL Variant, HW, SW, License Class, and License Category
*) Finally, we'll need the full executor log from a failed startup.
Feedback
Yes
No
Powered by
