Eset Security Server
Emelia Lute
If you had been using ESET on Windows Server 2003 at the time when the ESET security product supporting the said OS reached EOL, you should be eligible for paid extended support that would enable you to update the engine and a couple of other essential modules until Dec 2024. Please contact your local ESET partner for more information about the extended support program.
As said we were able to update ESET on Windows server 2003 and it stopped since past 1-2 weeks only. Last year, we did the renewal of the ESET license for the full quantity just like we do every year. Is there anything required to specifically request renewal for extended support program ?
Please contact your ESET distributor for more information about the paid extended support program. Note that it supports only updates of a very few essential modules and after Dec 2024 there will be no further updates.
Am also seeing this across every Server 2012 R2 ESET Server security install, been on hold for USA Business support for 10 minutes trying to check with them about this. I don't think I've seen it on newer server versions but as far as I'm aware 2012R2 should still be supported by ESET for another year?
I'm not entirely sure it's 100% non-functional as it still blocks an eicar on both the rollback and non-rollback server but I'd like to know when a new module is available to force an update and know if we need to reboot all the servers tonight to clear the errors or if it'll clear all the red in the console without that
Edit: Also support hasn't picked up the call for almost an hour now, would be nice if they had a way to update the voice IVRs to let people know it's a known issue rather than park what's likely hundreds of calls on hold.
This should not be necessary, as MarcFL wrote, clicking Dismiss in the warning should suffice and the protection status will be green. The eicar test file is detected then so protection seems to work fine. We'll make some further tests to make sure. So far it appears to be a glitch with the notification during modules reload after update.
while the status appears green on the server...my eset protect console shows all 7 of my 2012 servers as critical status...how do we clear eset protect critical error showing on eset protect console...
just going to update my post that we found a reboot on a system affected with this error/bad module would then be unprotected, so I would recommend deploying a module rollback task for 12 or 24 hours, depending on your availability to check on things after the rollback expires to give ESET time to fix the modules on their end.
Picked one of the systems with the error, the system seemed protected while showing the warning. Performed only a reboot of a system showing that error without doing a rollback or any other changes, and when it came up it was green and said protected but on the update tab show all modules detail window it was blank. Could tell it wasn't scanning files, was able to download Eicar and a common blocked PUP utility without issue and scan them manually without them being flagged as well. This was fixed with a 24h rollback.
I can't say that would be the case on your systems but would recommend either further testing (like a reboot) or the rollback, though if they are not rebooted and a new module is released and it updates, this should also be OK.
Thanks for the report. We're not in a position to restart our server yet. But I think we'll wait for Eset guidance as right now it's protected.
I just noticed this red box update above: "To fix the issue, please reboot the server. Do not click Dismiss as it will merely hide the warning. If you want to make sure that everything works, you should be able to open the advanced setup with advanced settings. If the window is blank, reboot the machine. You can also make an additional detection test by downloading the Eicar test file from We continue to analyze the issue in the mean time. While updates are suspended, ESET will continue to download the so-called pico updates that are issued every few minutes. Also ESET LiveGrid and ESET LiveGuard will continue to protect your machine."
We have not rebooted and advanced settings is not blank and Eset blocks Eicar...
If eicar is not detected, the advanced setup window will be likely blank as well. In such case a reboot should resolve the issue and modules should load alright then according to our tests. We continue working on finding out the root cause.
Temporarily disabling protected service in the HIPS setup and rebooting the machine resolves the issue. However, within 1-2 hours there will be a newer update that will address the issue. Protected service is an important protection feature and re-enabling it would require another reboot.
1. In Eset Protect Cloud i get a critical warning about that machine saying that the protecton services could not be started (all in red), whereas on the machine itself seems ESET is working fine (green lights).
What you have pinned in the forums is the wrong advice! Servers that haven't rebooted still have the real time protection working. If you reboot you lose malware protection. Rolling back updates does not work.
Hi!
Please allow me to say sorry first, my English is not good, so the following message is translated using Google, there may be some grammatical problems.
The original computer is equipped with EAV (11.x) and COMODO firewall, both can work normally
But since upgrading to EAV (13.x), I will encounter the "server not found" problem every time I boot up, and I can only use the repair function of EAV to fix it every time
, As long as the repair is completed, EAV can be updated normally before the next boot.
.
To try the following fix
1. Remove COMODO -> still unable to update
2. Refill EAV (using default installation) -> This boot is valid, but the next boot still shows that it cannot be updated
3.ping eset.com and update.eset.com, both of which can get IP
ESET has it's own firewall , You can switch to Internet Security and benefit from ESET firewall or you could use Windows Firewall along ESET , but I wonder if that was only a firewall , I wonder why it's conflicting with ESET , but could be Comodo is blocking ESET attempts to connect to Livegrid and Update servers.
I have never used Comodo , but if it was to blame it should have somewhere logged the blocked attempts and then maybe you can open the blocked ports , but it's weird since it's working for other PCs and for this one isn't.
Since you uninstalled Comodo and the EAV issue in regards to connection to its LiveGrid servers still exists, the problem lies somewhere in your network connection processing to Eset's LiveGrid servers. There is no difference in how this done in ver. 13 than in earlier Eset versions that I am aware of.
You might want to try uninstalling Eset using its stand-alone uninstaller: -uninstall-eset-manually-using-the-eset-uninstaller-tool in Win Safe mode. Then download and install the latest NOD32 version and see if this resolves the issue.
I have used the official removal tool in safe mode to remove all ESET software, and installed the latest version after restarting. The update can be normal after this boot, but the server cannot be found when the system is restarted
Not sure if I'm right or not but I believe I read in another topic in the forum that the Proxy cannot be used for authentication against ESET Protect.
Anyway, I wasn't able to make Apache Proxy work (agent hasn't been detected by the Server)
As far as I know it is not possible to verify the agent certificate on the proxy, but you can set up the proxy with an authentication, set it up in the agent's policy so the agents will connect to the on-prem server via it.
4a15465005