Traps VDI license validation failed

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Traps VDI license validation failed

L1 Bithead



We have detected that the agents are not registering in the ESM console. If we check the agent's console, it shows that it's connecting correctly to the Server, but in the console the agent does not appear.


If we force the heartbeat, the agent changes the status to unlincesed, and it appears in the console like unlicensed too. There are more than 6000 licenses free so we do not understand why it changes to unlicensed status.


If we force once more the heartbeat, the status changes to correct, and it appears correctly in the ESM console. But after 5 minutes it disappears again from the console.


After reviewing the configuration, we have disabled the check of the ESM of automatic license revocation. After we have changed this configuration, the agents have started connecting correctly. Also we have checked that some agents that are connected to the ESM have the last heartbeat from last week, and they are still running. So we do not kn ow if there is a reporting issue too.


After disabling the check of the license revocation, we have checked that some VDI pools are not connecting to the ESM. They are having the same issue with the automatic license revocation disabled.


Why can be this happen?





L1 Bithead

Hi @JokinLete, did you manage to fix this issue? Could you share the solution? We are experiencing the same problem on our end.



We have deployed a new installation with same infrastructure using the latest version of Traps ESM.With the new version is seems that it is solved, but we have not change the VDI Endpoints to the new infrastructure.


What version are you using?How is the license revocation configured?



ESM server is 4.2.3 with the VDI machines being 4.0.1 Automatic license revocation is enabled and is set to every 31 days.  


Thank you 




Can you check the agent logs, and also the logs of the Core and Console?


Also are you able to upgrade the agent version? 4.0.1 is not supported by Paloalto so if you open a TAC case they will tell you to upgrade it.



We are in the process of rolling out a new VDI environment with the latest TAC version. The current environment is 4.0.1 however we could potentially roll out a new version if this will fix the issue.


The agent logs don't seem to be showing anything of interest - agent logs are just showing agent status changing and content updates etc, however the ESM logs do have one error which is agent license validation failed. 

  • 5 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!