Log File Issue

Discussion in 'ESET NOD32 Antivirus' started by johnpd, Sep 3, 2010.

Thread Status:
Not open for further replies.
  1. johnpd

    johnpd Registered Member

    Joined:
    May 23, 2004
    Posts:
    80
    I checked my Events Log File and noticed that it did not show the latest update in the list. What it did show was two V-sig updates to v5417, one at 1:51am and a second at 2:52am. This is legitimate since I updated from NOD32 v4.2.40 to v4.2.64.12 in between. I shut down the computer a few hours later and when I rebooted the computer this afternoon just before 4pm, another update (v5419) was downloaded, but it does not show up in the log. However, the Update screen indicates that I am current with v5419. Has anyone seen this before?
     
  2. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    While I do not know if this has occurred previously, it is likely many are not seeing update 5419 as a logged definitions file update.

    Please refer to this thread for more information.
     
  3. johnpd

    johnpd Registered Member

    Joined:
    May 23, 2004
    Posts:
    80
    I did not experience any error as others did who posted in that thread. Apparently shutting down after the 5417 update and restarting after 5419 was released got me around the major issues. I have another computer which was off for a few days and shows no log problem when I started it today. However, I guess it is possible the update caused the log file issue. There is a mention of a fix utility that could be run to resolve some of the issues caused by 5417. Would you suggest I try that utility?
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    The utility is intended for those who updated to v. 4517/4518 and subsequently to 5419 but couldn't afford a computer restart. If you didn't install any of the two problematic updates there's no reason to run it. Let us know if the problem with update logging persists after next updates.
     
  5. johnpd

    johnpd Registered Member

    Joined:
    May 23, 2004
    Posts:
    80
    The next update that I got after booting up late Friday evening showed up in the log ok.

    9/3/2010 11:23:29 PM Kernel Statistical information was sent to ESET.
    9/3/2010 11:23:28 PM Kernel Statistical information was sent to ESET.
    9/3/2010 11:23:27 PM Kernel Statistical information was sent to ESET.
    9/3/2010 11:23:26 PM Kernel Statistical information was sent to ESET.
    9/3/2010 11:23:25 PM Kernel Virus signature database successfully updated to version 5421 (20100903).

    <-- 5419 update at about 3:50pm on 9/2/2010 was missing -->

    9/2/2010 2:52:30 AM Kernel Statistical information was sent to ESET.
    9/2/2010 2:52:29 AM Kernel Virus signature database successfully updated to version 5417 (20100902).
    9/2/2010 1:41:49 AM Kernel Statistical information was sent to ESET.
    9/2/2010 1:41:47 AM Kernel Virus signature database successfully updated to version 5417 (20100902).
     
Thread Status:
Not open for further replies.