Jump to content


  • Content Count

  • Joined

  • Last visited

Profile Information

  • Location
  1. Perfect. I will start the installation/configuration of the 7.2 VA. The existing server is currently used for another purpose at least for a few more months so I can't get rid of that just yet or this would have been much easier. Thanks!
  2. Our ERA 6.5 is running on Server 2008R2 and I want to replace it with the ESMC Virtual Appliance as I can't upgrade that server to ESMC 7.2 (SQL Server 2017 doesn't appear to install on 2008R2). What would be the procedure to installing a fresh ESMC 7.2 Virtual Appliance and just forcing the existing clients to connect to it? There are less than 100 clients which are: ESET Remote Administrator Agent 6.5.522.0 ESET Endpoint Antivirus 6.6.2095.1 I can find KB articles about upgrading 6.x to 7.x on the same server or moving between servers with identical versions but nothing tha
  3. We started getting this error on a regular basis on January 9th. Clients seem to be updating but instead of seeing this error maybe once every few months I'm seeing it multiple times a day now. ESET Remote Administrator (Server), Version 6.5 (6.5.522.0) ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0) Update module1072 (20180813) Translation support module1721 (20181211) Configuration module1663.13 (20180709) SysInspector module1274 (20180918) Server 2008, Windows 7 clients. Using the Apache proxy.
  4. I just tried to make a manual installation package. It sits on the "Downloading installers from repository and preparing all-in-one installer" window for about a minute or so then fails with "Internal Server Error". Clients are updating definitions just fine, the machine I'm typing this on has definitions from about an hour ago. Nothing on the ERA server has changed in months. Any ideas? If I attempt to manually download hxxp://repository.eset.com:80/v1/com/eset/apps/business/eea/windows/v6/6.6.2078.5/eea_nt64_enu.msi it times out immediately or starts downloading at about
  5. Trying to install ESET Endpoint Antivirus 6.6.2078.5 on a Windows 7 client. The agent installed ok (via GPO) and I've sent countless tasks through the ERA. Each one says Runnign for a while, then says Failed. I can send a wake up call and the "last connected" time updates. I cleared the cache on the server "C:\programdata\Apache HTTP Proxy\cache" in the hopes it would spark something to redownload but the actual installation files never actually get cached anyway so I'm not sure why I did that! Are there any logs? How do I go about troubleshooting this? I really dislike when I
  6. Of the five or so activation issues I initially saw all were solved with a safe mode uninstall then manually running the install task from the RA console. I decided to just go ahead and push it out company-wide and deal with the consequences. A dozen further machines failed activation and I was able to fix them in a similar fashion. No further issues so far and no messing with the ELA license website (futzing with the ELA activation didn't fix anything for me). I'm lucky in that aside from the hassle it's no big deal for me to do this, I know not everyone has an environment as forgiving or
  7. FYI, this is not just a problem that affects upgrades from earlier 6.6 versions. I had it happen to a bunch of computers that were upgraded from 6.5.
  8. Uninstalled it from safe mode and reinstalled from a manual install task. Looks fine now. Can you confirm that the problem is fixed now? I'm hesitant to upgrade the bulk of our clients if this is going to happen again.
  9. I see the former: "Module update failed. Your license file does not contain a username and password. You can update only from an update mirror" There are no Username or Password entries in that registry key, no.
  10. I tried a bunch this morning but to be certain I just rebooted it again and get the same "ESET Endpoint requires your attention" bubble after login. Protection Status: ESET Livegrid is not accessible. Modules Update failed: Your license file does not contain a username or password. I've tried to activate it manually a few times and have also deactivated the license from the ELA site but nothing has worked yet. Is there anything else I can try?
  11. I can check on https://ela.eset.com/ and it's listed with an activation date of today with a green checkmark "Everything is OK". However, the client has the same errors described earlier in the thread: Modules update failed, live grid not accessible etc..
  12. Nope, it had v5, then upgraded to 6.5 then yesterday upgraded to 6.6 all through the remote console in exactly the same way all the other machines were. Some worked fine and some had this error. Some were upgraded from 6.5.2094, some from 6.6.2046 but all with the same remote console task.
  13. This morning before reading this thread I deactivated another client on the ELA site then attempted to activate the license manually. ELA was immediately updated with the date of this new activation, the "activation from ERA" for that client was gone and the "status" was listed with a green tick "Everything is OK". The client shows a window with a progress bar saying "Verifying License Key, This may take a few moments" which doesn't go away. I can close it, reboot and the client is still not activated. Is there anything we should be doing to prepare for the fix that's coming?
  14. I just upgraded some computers to 6.6.2068 and have this same problem with a bunch of them. It has been less than 24 hours since upgrading but after a couple reboots they still have issues. This page: https://support.eset.com/kb6636/ mentions a server-side update but doesn't give a link to download the update - any idea how to get it? On one of the affected machines I deactivated the license via https://ela.eset.com, rebooted the machine, then sent an activation task. The task was listed as Planned:Yes, Status: Finished for about 30 minutes but now has changed to Planned:No, Sta
  • Create New...