j-gray 37 Posted August 22 Share Posted August 22 This just started happening with some of our Windows workstations, possibly specific to EA 11.1.2039.2 which we've slowly been moving towards. AV is activated, but EI Connector is not. Activation tasks run but fail with no details other than "Task failed". Nothing shows in the EI Connector log regarding the task. Client logs show, "Request to ESET Endpoint Security/Antivirus failed. Error PERSEUS_E_EI_NO_LICENSE (21801)" Typically with past activation issues we simply uninstall the EI Connector and reinstall it. This isn't working for these systems. We have ample licenses for Inspect, not expiring until 2025. Any clues on what might be the issue or where to look for more clues? Quote Link to comment Share on other sites More sharing options...
itman 1,756 Posted August 22 Share Posted August 22 Based on a similar Eset Inspect licensing issue here: https://forum.eset.com/topic/41409-eset-inspect-license-check-failed-randomly/ , looks like you're going to have to open a support request for further assistance. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,290 Posted August 23 Administrators Share Posted August 23 Is that an x86 or x64 Windows? Please enable advanced licensing logging in Endpoint (adv.setup -> Tools -> Diagnostics), retry EI Connector activation, turn off logging and provide ELC logs. Alternatively you can enable advanced logging under Help and support -> Technical support. Quote Link to comment Share on other sites More sharing options...
j-gray 37 Posted August 26 Author Share Posted August 26 On 8/23/2024 at 1:47 AM, Marcos said: Is that an x86 or x64 Windows? All are x64. We have no x86 OS's in our envrionment. Quote Link to comment Share on other sites More sharing options...
Solution j-gray 37 Posted September 24 Author Solution Share Posted September 24 In case anyone is following, we were using the ESET Bridge in our environment. The last update to the Bridge apparently broke it somehow. Support indicated this is a common occurrence with Bridge upgrades. Given that it's apparently unreliable and there are no indications when it's failing, we're removed it entirely from our environment. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,290 Posted September 25 Administrators Share Posted September 25 Please provide the ID of the ticket related to this issue so that we can check how it was dealt with by the US tech support team. Quote Link to comment Share on other sites More sharing options...
j-gray 37 Posted September 25 Author Share Posted September 25 @Marcos The case was #00812230. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.