ESMC wake-up call

[czechoto 0]

Hi,

When I try to send wake-up call I got error: Failed to send Wake-up call.

In the logs:

2018-09-06 12:10:08 Error: CPushNotificationsModule [Thread a7c]: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}
2018-09-06 12:10:08 Error: ConsoleApiModule [Thread 2e84]: 2 Error while processing SendWakeUpCall request: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}
2018-09-06 12:10:08 Error: ConsoleApiModule [Thread 2e84]: Untranslatable CInterModuleException: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}

On our ERA server the send wake-up call is working fine.

 

[Kieran Barry 11]

28 minutes ago, czechoto said:

Hi,

When I try to send wake-up call I got error: Failed to send Wake-up call.

In the logs:

2018-09-06 12:10:08 Error: CPushNotificationsModule [Thread a7c]: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}
2018-09-06 12:10:08 Error: ConsoleApiModule [Thread 2e84]: 2 Error while processing SendWakeUpCall request: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}
2018-09-06 12:10:08 Error: ConsoleApiModule [Thread 2e84]: Untranslatable CInterModuleException: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}

On our ERA server the send wake-up call is working fine.

 

Hi @czechoto,

Can you specify what software you are using? Is it Endpoint Security, Endpoint Antivirus? and what version?

Can I also point you in the direction of this thread that has been created recently, detailing the same issue: here.

 

 

Thanks,

Kieran Barrry

[czechoto 0]

ESET File Security 7.0.12014.0, and agent 7.0.553.0

[MartinK 378]

3 hours ago, czechoto said:

2018-09-06 12:10:08 Error: CPushNotificationsModule [Thread a7c]: Failed to find EPNS Token for computer uuid {26594519-6350-4e9b-ba80-a7ec14f44aac}

This error means that ESMC server does not know AGENT's identifier to be used for push notification (wake up call). This might be caused by:

• Agent is not v7 (i.e. older AGENT is used)
• Agent is not able to register with EPNS service, i.e it is not able to communicate with epns.eset.com
• Agent was registered to EPNS recently, and there was no connection to ESMC since that, so ESMC does not known about it yet. This should resolve automatically after next AGENT's connection to ESMC

Please verify all mentioned conditions are met.

[opa-pro 2]

On 9/6/2018 at 6:46 PM, MartinK said:

Эта ошибка означает, что сервер ESMC не знает идентификатор AGENT, который будет использоваться для push-уведомления (звонок пробуждения). Это может быть вызвано:

• Агент не v7 (используется старый AGENT)
• Агент не может зарегистрироваться в службе EPNS, т. Е. Не может общаться с epns.eset.com
• Агент был зарегистрирован в EPNS недавно, и с тех пор не было никакой связи с ESMC , поэтому ESMC пока не знает об этом. Это должно автоматически разрешаться после следующего подключения AGENT к ESMC

Проверьте, соблюдены ли все указанные условия.

I have the same error with the following type of epns service - 

2018-10-24 09:19:21 Warning: CPushNotificationsModule [Thread 6c0]: Failed to configure EPNS resource (retrying in 21600 seconds): Error calling PNS API 'PnsRegisterClient' (return code = 19108) -

This is evident on windows xp machines.

Thanks for any help.

Edited October 24, 2018 by opa-pro

[Marcos 5,070]

The problem is that we have dropped support for weak ciphers RC4 and 3DES and Windows XP doesn't support modern and secure ones.

We plan to address this in future versions.