Author Topic: License File not being deployed  (Read 3148 times)

0 Members and 1 Guest are viewing this topic.


  • Guest
License File not being deployed
« on: March 30, 2015, 09:34:17 PM »
We are running into some systems where the license file is not being deployed.  I was wondering if anyone else has run into this.  In the logs on the client machine, we get this

[2015/03/30 15:26:44.439,2816] Obtained server IP address: X.X..X
[2015/03/30 15:26:44.439,2816] Creating server connection socket
[2015/03/30 15:26:46.080,2816] Connection to server created with 0x00000000 error code...
[2015/03/30 15:26:46.080,2816] Connected to server...
[2015/03/30 15:26:46.080,2816] Last resident change:
[2015/03/30 15:26:46.080,2816] Space available at temp directory: 2869768192 bytes...
[2015/03/30 15:26:46.080,2816] Agent installation GUID: 6b69c40d-0425-4538-8cc5-5f9412eafc44
[2015/03/30 15:26:46.095,2816] Unable to perform pop from server, error 0x7FFF0021 occured...
[2015/03/30 15:26:46.095,2816] Cannot connect to server, error 0x7FFF0021...
[2015/03/30 15:26:46.095,2816] Exception 0x7FFF0021 generated in CClient::PopupThread()

On the server side, we see this pop up a lot

[2015/03/30 15:27:35.943,1636] Engine is not handled, probably out of licenses...

Our license file is loaded and we have plenty of licenses so I am not sure why this is happening.  The machines have been discovered on the AEA console.  This doesn't happen on every machine, just some of them.  Any help would be greatly appreciated!


  • Guest
Re: License File not being deployed
« Reply #1 on: March 31, 2015, 01:54:54 AM »
Are you sure you have enough licenses? Licenses are handed out when a device is DISCOVERED. Not when it is actually installed on the machine. How many devices have been discovered and how many licenses do you have?
(If you are out of licenses you should see a key or lock icon next to the computer name in AEA)
« Last Edit: March 31, 2015, 02:05:40 AM by VincentArriola »


  • Guest
Re: License File not being deployed
« Reply #2 on: March 31, 2015, 01:36:15 PM »
I believe I figured out the issue.  I did not realize Avast assigns the licenses when they are discovered, not when it is installed.  I had more machines discovered than I had licenses.  I just added additional licenses and so far it seems to have resolved the problem.  Thanks for the response Vincent