Error Failed to connect to the licensing server

[Xi2 0]

Есть большая проблема, почти во всем предприятии отключился антивирус, статус не активировано.

До этого существовало "клиентское задание" активации. На форуме нашел решение удалить лицензионный ключ  и добавить его заново в ERA, сказано, сделано. Удалил старый ключ, добавил новый, синхронизация прошла.

При создании "клиентское задание" Активации, после выбора лицензии и остальных пунктов, после нажатия FINISH выходит ошибка "Failed to create task: Failed to connect to the licensing server"

При пинге edf.eset.com ничего не выходит:

Обмен пакетами с bal-edf-pcs-app-vmss-02.westus.cloudapp.azure.com [13.91.57.145] с 32 байтами данных:

Превышен интервал ожидания для запроса.

на сайт тоже не входит см скриншот

 

 

 

Machine translation:

There is a big problem, the antivirus has disconnected in almost the entire enterprise, the status is not activated.

Prior to this, there was a "client task" activation. The forum found a solution to remove the license key and add it again to the ERA, said, done. I deleted the old key, added a new one, the synchronization was over.

When creating a "client task" Activation, after selecting a license and other items, after pressing FINISH, the error "Failed to create task: Failed to connect to the licensing server"

When pinging edf.eset.com, nothing comes out:

Packet exchange with bal-edf-pcs-app-vmss-02.westus.cloudapp.azure.com [13.91.57.145] with 32 data bytes:

Timed out request.

Edited April 30, 2019 by Marcos
Machine translation added

[Marcos 5,259]

Are you able to activate Endpoint locally from the machine by entering your license key in the activation window? Did you open edf.eset.com/xml in a browser on the troublesome machine and not on another one, e.g. where ESMC Server is running? Do you use the same proxy setting in the browser and in the ESMC agent and Endpoint?

[Xi2 0]

локальная активация проходит нормально, но достаточно долго выполняется запрос примерно 20-30 секунд.

а при открытии сайта hxxp://edf.eset.com/xml не получает результата, а на "https" в ответ получает 403

и да прокси везде одинаково настроен, без прокси выход не возможен.

 

Machine translation:
local activation is normal, but the query takes about 20-30 seconds to complete for a long time.
but when you open the site hxxp: //edf.eset.com/xml does not get a result, and on the "https" in response it receives 403
and yes, the proxy is the same everywhere, no output is possible without a proxy.

Edited April 30, 2019 by Marcos
Machine translation added

[Marcos 5,259]

Since this is an English forum, please post in English so that moderators or other users can understand and be able to help you.

If you do not speak English, use a translator or contact your local customer care please.

[Xi2 0]

ok, i'll mind it

Edited April 30, 2019 by Xi2

[Cheeta_N 0]

Go to License Management and remove license. Add your license key again, then create new client task.

If you are using EBA or Security Administrator account you should re-add license key in the appropriate account and synchronize license in ERA\ESMC.

 

Edited April 30, 2019 by Cheeta_N

[Xi2 0]

okay? i've installed ESMC VA joined it to domain and still getting error with activation, in client tasks.

What i need to do, to make it working?

[Marcos 5,259]

Please provide the trace log from the ESMC server in a compressed form.

[MartinK 383]

Could you please double check HTTP proxy configuration on clients and also verify proxy is running correctly? In case it is Apache HTTP proxy installed with ESMC, could you restart it to be sure it is in correct state?

As you mentioned that activation on client takes long time, it might be result of not responding or inaccessible HTTP proxy. It is possible that local activation is able to use also system HTTP proxy and that is why it is successful.

Also could you verify that ESMC itself can synchronize licenses?

[Xi2 0]

On 5/1/2019 at 12:24 AM, MartinK said:

Could you please double check HTTP proxy configuration on clients and also verify proxy is running correctly? In case it is Apache HTTP proxy installed with ESMC, could you restart it to be sure it is in correct state?

We are using Kerio Winroute with it's own proxy. Cache on proxy was flushed, but it didn't help. Also i was trying to activate with proxy on and off, both was unsuccessful.

On 5/1/2019 at 12:24 AM, MartinK said:

Also could you verify that ESMC itself can synchronize licenses?

Yes, it's getting licenses and sync well.

PS. servers don't use proxy, they have straight access to internet.

Edited May 2, 2019 by Xi2

[Xi2 0]

2019-05-02 03:29:18 Error: NetworkModule [Thread 7fd60d7fa700]: Protocol failure for session id 17696, error:Receive: NodSslWriteEncryptedData: Internal error in the underlying implementations.
2019-05-02 03:29:27 Error: AutomationModule [Thread 7fd59f7e6700]: ManagementProcessor: Failed to create client task of type ProductActivation. Error: ActivationAwareClientTaskConfigValidationBase: The task configuration is not acceptable, because there is no deployment token for the chosen license [LicenseUuid=3a9120c2-83e2-4032-818d-5fc3bc5af0cb].
2019-05-02 03:29:27 Error: AutomationModule [Thread 7fd59f7e6700]: ActivationAwareClientTaskConfigValidationBase: The task configuration is not acceptable, because there is no deployment token for the chosen license [LicenseUuid=3a9120c2-83e2-4032-818d-5fc3bc5af0cb].
2019-05-02 03:29:27 Error: ConsoleApiModule [Thread 7fd5897ba700]: 17685 Error while processing CreateClientTask request: ActivationAwareClientTaskConfigValidationBase: The task configuration is not acceptable, because there is no deployment token for the chosen license [LicenseUuid=3a9120c2-83e2-4032-818d-5fc3bc5af0cb].
2019-05-02 03:29:28 Error: NetworkModule [Thread 7fd60dffb700]: Receive: NodSslWriteEncryptedData: Internal error in the underlying implementations., ResolvedIpAddress:10.0.9.7, ResolvedHostname:mail.garant.local, ResolvedPort:2306
2019-05-02 03:29:28 Error: NetworkModule [Thread 7fd60dffb700]: Protocol failure for session id 17697, error:Receive: NodSslWriteEncryptedData: Internal error in the underlying implementations.
2019-05-02 03:29:29 Error: LicenseModule [Thread 7fd5967d4700]: LicenseModuleHelper: RetrieveAndPersistDeploymentTokens: Failed to get deployment token for license [Uuid=3a9120c2-83e2-4032-818d-5fc3bc5af0cb; SeatId=43bb3879-71e5-4e9d-9b12-6936a3a63e08; PoolId=bd2513a6-134c-4e27-adac-da23ded9830e; LicensePublicID=3AE-DCA-H9N; ProductCode=320]. Error: CEcpCommunicator: ECPRequestMessageGetDeploymentToken request failed, error=0x2051c003.
2019-05-02 03:29:29 Error: LicenseModule [Thread 7fd5967d4700]: LicenseModuleHelper: SyncPools: Finished with errors [DeploymentTokenRetrievalFailuresCount=1].
2019-05-02 03:29:30 Error: AutomationModule [Thread 7fd59efe5700]: LicensePoolSyncTrigger: Trigger [UUID=00000000-0000-0000-7011-000000000003, TYPE=LICENSE_SYNCHRONIZATION] detected failed license synchronization. Retry counter exceeded, no rescheduling will be made.
2019-05-02 03:29:43 Error: NetworkModule [Thread 7fd60d7fa700]: Receive: NodSslWriteEncryptedData: Internal error in the underlying implementations., ResolvedIpAddress:10.0.64.101, ResolvedHostname:10.0.64.101, ResolvedPort:48372

i'm getting this messages in /var/log/eset/RemoteAdministrator/Server/trace.log

[Marcos 5,259]

The problem seems to be with the deployment token. I'll request syncing the license which should fix it:

ECPRequestMessageGetDeploymentToken request failed

[Xi2 0]

Now i'm trying to migrate license from ELA to EBA, but immediately after entering license key and password it shows "Cannot bind license" , and after that i'm getting mail with token, which after open says "token expired"

 

ps i've deactivated all activated PC's in ELA, removed all security admins and deleted it's account, but still get error "Cannot bind license" in EBA

but there is a good one thing, i've readded license key to ESMC and could make an activation task.

Edited May 2, 2019 by Xi2

[Xi2 0]

up