Nod32 not updating server Free dirty anonymous sex chat room free on mobile
The server hasn't been updating its virus signature database in the last few days, and upon trying to do a manual update, I get the following error message: "Base file missing".
Here is a screenshot of the error: I've tried to find a solution for this problem on the ESET website, as well as on Google, but this hasn't been successful. I still couldn't find out what was causing this problem, but upon advice from ESET support, I re-installed ESET NOD32 and cleared the Update Cache.
I’m running ESET Remote Administrator (ERA) 3.0.105 as an update mirror on a Win2003 R2 server. Clicking on Update Now only changes the time; the version is still 4522. I opened the client that is installed on the server and tried the manual update twice, once with diagnostic logging.
There are six NOD32 3.0.684.0 clients that connect to that server (including one client on the server itself). During the first manual update attempt, I saw it download about 20MB of update files.
I tried updating them through the Printer Preferences page (Devices and Printers) and picking the Windows Update source from the New Driver option.
This does seem to download a bunch of files from Windows Update, but doesn't solve the warning about older drivers.
Why is this happening and what can I do to prevent it?
This article applies to version 5.x and earlier ESET business products.
The story: numerous ESET NOD32 V4.x Antivirus product customers reported severe problems after install of Service Pack 2 Windows Vista and Windows Server 2008.
First reports showed up begin of May 2009, and at the moment I write this post these reports still continue.
I have taken over the administration of a Windows Server 2008 64bit installation.
The server has ESET NOD32 Antivirus Business Edition v4.2 installed.