I was just looking through the Events in my NOD32 Log files and noticed that there are a whole load of update and failures before one was successfully downloaded. For instance below is just for today. 01/06/2008 19:57:01 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 18:57:02 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 17:57:01 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 16:57:02 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 15:57:06 Kernel Statistical information was sent to ESET. 01/06/2008 15:57:06 Kernel Virus signature database successfully updated to version 3150 (20080601). 01/06/2008 15:57:05 Update Updater: retval = 0x0000, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 14:57:01 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 13:57:01 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 12:57:01 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 11:56:56 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 01:00:51 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM 01/06/2008 00:00:51 Update Updater: retval = 0x5003, failures: 0 NT AUTHORITY\SYSTEM This is happening far more regularly over the last week or so. Is it a problem with ESETs' servers or is the problem at my end? Update Just realised it's probably NOD32 automatically checking for updates but none are available. Is that correct?
Could you , please , explain further why the OP has this in their log because I have never seen an entrie in the logs for successful checking but no updates available . Is this a special option ?
I wouldn't call it a "special option" but simply the results one recives if they select Diagnostic records for logging results. ________________________________________