NOD32 no longer updating properly

Discussion in 'ESET NOD32 Antivirus' started by BurtieLad, Jul 26, 2008.

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

    betsla Registered Member

    Joined:
    Aug 23, 2008
    Posts:
    2
    Now, all of a sudden I've got ver 3382. Something happened over night, when my computer was off...


     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,448
    What happened when you updated manually before? Did you get the error 0x101a? We'd need to investigate the problem right at the moment when the error occurs as it'd mean that ekrn.exe is unable to write into the temp folder. The best would be if you could run Filemon or Process monitor from Microsoft, filter out all processes but ekrn.exe and run a manual update that should end up with the error. Please let me know when you happen to make such a log.
     
  3. JohnWin

    JohnWin Registered Member

    Joined:
    Aug 22, 2008
    Posts:
    3
    I'll make sure to do it next time
     
  4. FileCity

    FileCity Registered Member

    Joined:
    Jun 23, 2008
    Posts:
    10
    This problem also happened to me yesterday, cannot do any update even manual. What I did to solve this:

    Killed EGUI
    Killed EKRN
    Deleted all em*32.dat files manually. You may need to try killing EKRN few times until all files as been deleted successfully.
    Launch EGUI again.

    At this time you need to do a manual update. This forces NOD32 to download the entire definition files. After the successfull update, reboot. This worked for me and now all is fine.

    Hope this helps.
     
  5. Rapid Dr3am

    Rapid Dr3am Registered Member

    Joined:
    Jun 14, 2008
    Posts:
    60
    I just wiped a laptop and then I thought why not see if NOD32 works now. What do you know, it does. I can now update. Norton was starting to irritate me.
     
  6. sanchehl

    sanchehl Registered Member

    Joined:
    May 17, 2006
    Posts:
    9
    I was able to get around this problem today. All you have to do is figure out which file Ekrn.exe has locked. For me, it was em002_32.dat located in the program files folder for Eset. You can use Procmon.exe (windows sysinternals) to figure out which file is locked. Just filter the ekrn.exe process and perform and update, you should get a sharing violation error on the file that is causing the problem. Next use Procexp.exe (windows sysinternals), find ekrn.exe in the list, highlight it, make sure you are showing the lower pane, find the emm002_32.dat file or what ever file it is, right click and select close handle.

    You can now update.
    This has saved me from having to reboot my servers every day because they fail to update.
    Hope Eset fixes this soon.
     
  7. Demente1982

    Demente1982 Registered Member

    Joined:
    Aug 22, 2008
    Posts:
    7
    I have no problems with clients v3.x but clients in v2.x some of them doesn't update. Some of them update to 3382 and the next day back to 3304. I have 700 clients (approx.) with 100 clients (approx.) with troubles for update.

    I delete the content of updfiles and update manually 2 or 3 times for update succeful.

    Any Solutions here.
     

    Attached Files:

  8. fariz

    fariz Registered Member

    Joined:
    Aug 26, 2008
    Posts:
    16
    We experience lot of troubles with NOD32 migration from 2.7 to 3.0. About every 7th installation we get update problem. I can't even see clear pattern on this. It happens both when we set it over 2.7 and when we first uninstall 2.7 and set 3.0. Sometimes clients never contact server, and not seen on console. Sometimes they contact server once, get last version, then stop updating both automatically or manual.

    Can you help us with a problem pls.? We have 900 license purchased for our bank.
     
  9. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,448
    What exactly happens when you try to run a manual update? Do you get an error?
     
  10. fariz

    fariz Registered Member

    Joined:
    Aug 26, 2008
    Posts:
    16
    We get this. Not any specific error code or something.

    2.7 on the same computers worked perfectly fine.

    http://www.warriormage.com/dl/nod32.jpg
     
  11. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,448
    Do you always get this error when you run a manual update or it works after several attempts?
     
  12. fariz

    fariz Registered Member

    Joined:
    Aug 26, 2008
    Posts:
    16
    No, it does not work. I also can't set that client to update from serverside. It stays in task with "waiting".

    It also 21 hours since it connected server. So it connected once after setup, and then it can't connect to the server. I have this problem with part of computers. Others do not connect at all after installation.

    I would think it is problem with setup, but considering it connected once and 2.7 from same computer also worked fine, it shall be something else.
     
  13. Demente1982

    Demente1982 Registered Member

    Joined:
    Aug 22, 2008
    Posts:
    7
    fariz....do you use http server o shared folder..o_O
     
  14. fariz

    fariz Registered Member

    Joined:
    Aug 26, 2008
    Posts:
    16
    We use HTTP server.
     
  15. kaisernc

    kaisernc Registered Member

    Joined:
    Feb 6, 2007
    Posts:
    4

    I followed these steps and it allowed me to perform a manual update on the server having update issues. Windows Server 2003 x64, NOD32 3.0.621.0.
     
  16. bwhorton

    bwhorton Registered Member

    Joined:
    Apr 20, 2007
    Posts:
    4
    Thanks Sanchehl! Your post led me to delete the cache as well as the .dat files under C:\Program Files\Eset\ESET NOD32 Antivirus. After deleting, it updated without issue. I too, hope they get this fixed soon. Seeing it more and more.

    Thanks again!

    Ben
     
  17. ffemtreed

    ffemtreed Registered Member

    Joined:
    Apr 10, 2008
    Posts:
    6
    I am having this problem as well. Overnight all my clients turned orange and refuse to update. using 3.0.657 with LAN updates.

    Going to each everyone of my PC's and manually deleting files is NOT an option as it would take days for me to do this.

    This not updating problem is getting old real quick, I shouldn't have to spend time worrying if my Virus scan updates are working and the provider is sending good updates.
     
  18. Demente1982

    Demente1982 Registered Member

    Joined:
    Aug 22, 2008
    Posts:
    7
  19. airshark

    airshark Registered Member

    Joined:
    Sep 2, 2008
    Posts:
    1
    THANK YOU SO MUCH for providing me info that my PAID virus protection provider has failed to provide.

    I followed your directions and I also had em002_32.dat locked. Followed your steps and my NOD32 is now properly updated. Thanks again.
     
  20. Proteos

    Proteos Registered Member

    Joined:
    Aug 16, 2008
    Posts:
    8
    Does this work on a local system? Mine continues to do the same thing.
     
  21. martindijk

    martindijk Registered Member

    Joined:
    Jun 13, 2003
    Posts:
    537
    Location:
    Gorredijk - the Netherlands
    Weird, i got my wife a new laptop (Vista 32 bit home edition), installed Nod Antivirus 3.0.669 and again Nod is nagging me about "username and password".

    I cleared the cache and all went well, but spoke too soon, after about an hour i got my first email from Nod Antivirus saying "wrong username and password" and could not update while on my laptop (Xp Sp2) everything is going well, so what is going on here, iam getting tired of updating manually and looking after my AV.

    Still no solution from Eset's end o_O
     
  22. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,448
    If you are able to download the commercial version of EAV using your username and password, couldn't it be that you have fiddled around update task settings (e.g. created a new profile by copying settings from the default one, changed the update interval, etc.)? Just in case, try uninstalling 3.0.669 and installing 3.0.672.
     
  23. martindijk

    martindijk Registered Member

    Joined:
    Jun 13, 2003
    Posts:
    537
    Location:
    Gorredijk - the Netherlands
    Hi Marcos, i changed all that by deleting all the objects and put them back from scratch, so everything is back to normal now.
     
  24. martindijk

    martindijk Registered Member

    Joined:
    Jun 13, 2003
    Posts:
    537
    Location:
    Gorredijk - the Netherlands
    Say Marcos, why implement all these extra settings in the first place when it shouldn't be fiddled with??

    Just curious :rolleyes:
     
  25. oldhead

    oldhead Registered Member

    Joined:
    Feb 6, 2006
    Posts:
    8
    Location:
    Jersey
    Unfortunately, "me too" with this error message....using 3.0.657.0, stuck on 3446 last update, XP Pro (32-bit) SP3.

    Never
    had a problem until yesterday afternoon.

    Can a "wiser" person than I teach an oldhead how to use Filemon or Process monitor to get ESET the info necessary to fix this?

    THANKS in advance!
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.