Chanklish 1 Posted June 5, 2023 Share Posted June 5, 2023 i have eset protect on prem server and 10s of windows computers they are around 15 computers refusing to be activated with the product activation task , connected , pingable , accessable , etc but not getting activated license still have enough seats and expiry is in 2024 what to check ?! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 5, 2023 Administrators Share Posted June 5, 2023 Please carry on as follows: Enable advanced logging under Help and support -> Technical support Attempt to activate the product Stop logging Collect logs with ESET Log Collector and upload the generated archive here. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 5, 2023 Author Share Posted June 5, 2023 the advanced logging has changed since previous versions , now they are more granulated here you go ELC_logs.zip Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 5, 2023 Author Share Posted June 5, 2023 any idea ?! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 5, 2023 Administrators Share Posted June 5, 2023 The logs were taken from a machine without ESET installed. Please provide ELC logs from a machine where ESET is installed but activation is failing. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 5, 2023 Author Share Posted June 5, 2023 31 minutes ago, Marcos said: The logs were taken from a machine without ESET installed. Please provide ESET Log Collector logs from a machine where ESET is installed but activation is failing. the logs were taken from the protect server ..do you want the logs from tbe endpoint? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 5, 2023 Administrators Share Posted June 5, 2023 Yes, the logs were supposed to be taken from an Endpoint with ESET installed where activation was failing. Please provide such logs. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 13 hours ago, Marcos said: Yes, the logs were supposed to be taken from an Endpoint with ESET installed where activation was failing. Please provide such logs. here you go ees_logs.zip Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 6, 2023 Administrators Share Posted June 6, 2023 Unfortunately a SysInspector log which is selected by default was not selected and therefore was missing in the generated zip file. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 2 minutes ago, Marcos said: Unfortunately a SysInspector log which is selected by default was not selected and therefore was missing in the generated zip file. there is no sysinspector installed on the endpoints i opened a ticket , this is taking too much time Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 6, 2023 Administrators Share Posted June 6, 2023 There's obviously a problem establishing SSL communication with ESET's servers. Please check if you have applied this workaround in the past and undo the changes if an update addressing the security vulnerability is installed: https://learn.microsoft.com/en-us/security-updates/SecurityBulletins/2015/ms15-031?redirectedfrom=MSDN#ID0EUNAE How to undo the workaround. Follow these steps to disable the SSL Cipher Suite Order policy setting: At a command prompt, type gpedit.msc and press Enter to start the Group Policy Object Editor. Expand Computer Configuration, Administrative Templates, Network, and then click SSL Configuration Settings. Under SSL Configuration Settings, double-click SSL Cipher Suite Order. In the SSL Cipher Suite Order window, click Disabled and then click OK. Close the Group Policy Object Editor and then restart your system. If that's not the case, provide a Wireshark pcap log from an unsuccessful activation attempt. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 with sysinspector ees_logs.zip Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 7 minutes ago, Marcos said: There's obviously a problem establishing SSL communication with ESET's servers. Please check if you have applied this workaround in the past and undo the changes if an update addressing the security vulnerability is installed: https://learn.microsoft.com/en-us/security-updates/SecurityBulletins/2015/ms15-031?redirectedfrom=MSDN#ID0EUNAE How to undo the workaround. Follow these steps to disable the SSL Cipher Suite Order policy setting: At a command prompt, type gpedit.msc and press Enter to start the Group Policy Object Editor. Expand Computer Configuration, Administrative Templates, Network, and then click SSL Configuration Settings. Under SSL Configuration Settings, double-click SSL Cipher Suite Order. In the SSL Cipher Suite Order window, click Disabled and then click OK. Close the Group Policy Object Editor and then restart your system. If that's not the case, provide a Wireshark pcap log from an unsuccessful activation attempt. nothing like this was done Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 6, 2023 Administrators Share Posted June 6, 2023 5 minutes ago, Chanklish said: nothing like this was done Please provide a Wireshark pcap log from an activation attempt then. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 i will wait for the eset support team Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 6, 2023 Administrators Share Posted June 6, 2023 Ok but you can prepare the pcap logs cause technical support will request them. Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 4 minutes ago, Marcos said: Ok but you can prepare the pcap logs cause technical support will request them. they can do them themselves - i will not lose time over a broken software Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 6, 2023 Administrators Share Posted June 6, 2023 There's likely a problem with the OS itself and the underlying SSL implementation may not work properly, otherwise there would be no problem to establish SSL communication. Let's wait and see what technical support will find out from the pcap log. In the logs I've seen frequent issues recently: Also more than 40 certificate errors like this on May 31: Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 i think even your support contact has issue i received this after filling a support request online <support@esetme.com>: host mail.midisglobaluae.com[94.200.27.254] said: 550 5.7.0 Local Policy Violation (in reply to end of DATA command) Link to comment Share on other sites More sharing options...
Administrators Marcos 5,044 Posted June 6, 2023 Administrators Share Posted June 6, 2023 Did you fill in the support form at https://www.eset.com/me/support/contact-support/ ? Link to comment Share on other sites More sharing options...
Chanklish 1 Posted June 6, 2023 Author Share Posted June 6, 2023 yes and i received this error in my mail Link to comment Share on other sites More sharing options...
Recommended Posts