Network wide errors on latest update

Discussion in 'ESET NOD32 Antivirus' started by jst3751, Jan 28, 2010.

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

    jst3751 Registered Member

    Joined:
    Dec 11, 2009
    Posts:
    21
    Location:
    USA
    For about the last 2 hours, as computers on the network begin recieving the latests signature update, all of them are reporting errors such as this:

    1/28/2010 5:02:33 AM - During execution of Update on the computer SRV2,
    the following warning occurred:

    The virus signature showing is 4812 and is showing out of date. It appears to be error on trying to update to 4813.
     
  2. Kevin Latour

    Kevin Latour Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    1
    Had same issue. A few client updated to 4813, most of them failed to update.

    I tried to clear all caches (server and client) without success.

    It's not link to a client version as issue occured for 4.0.417 to 4.0.474 (ESET Nod32 business edition)
     
  3. jst3751

    jst3751 Registered Member

    Joined:
    Dec 11, 2009
    Posts:
    21
    Location:
    USA
    It is happening on both 4.x clients and 3.x clients, so it is not client specific, it is a bad signature file.
     
  4. Jocke

    Jocke Registered Member

    Joined:
    Jun 25, 2007
    Posts:
    2
    Location:
    V?ster?s, Sweden
    We are experience the same thing on our server.
    It´s when the update 4813 is going out to the clients.

    Date Received 2010-01-28 14:30:06
    Date Occurred 2010-01-28 14:26:05
    Level Critical Warning
    Plugin Update module
    Event Error downloading file from update server
    User NT INSTANS\SYSTEM
     
  5. MadMaxToronto

    MadMaxToronto Registered Member

    Joined:
    Sep 17, 2008
    Posts:
    5
    Yes... I noticed this too.
    Since 6:30 AM EST we've been getting Crital Warning messages for the Update Module plugin... some have a blank Event in the ESET Console and some say "Error downloading file from update server". Most of our servers seem to have no trouble updating from 4812 to 4813 but desktop clients are getting errors on the update.

    Max
     
  6. EmpereurZorg

    EmpereurZorg Registered Member

    Joined:
    Jan 12, 2010
    Posts:
    12
    4813 signature problem ?

    On NOD32 (EAVBE), most of our PC are not updating their database to 4813 (actually the last version is 4812...). ERA seems to be ok, I cleared cache to force a new download, without success.
    So, I'm waiting for a 4814 o_O
     
  7. csedgbeer

    csedgbeer Registered Member

    Joined:
    May 15, 2007
    Posts:
    16
    Re: 4813 signature problem ?

    same here with 197 clients on RA server, none of them would update to 4813 for a while, now they are ok but there's still something going on

    our update server has reported a "not_compatible_module" error last time it tired to get what i assume is 4814, and a local client updating from 4813 over the internet to nod's servers keeps timing out
     
  8. ethos

    ethos Registered Member

    Joined:
    Aug 26, 2008
    Posts:
    30
    Re: 4813 signature problem ?

    Same here, no clients where updating- so I cleared the files out and now ERA is stuck on "preparing update..." and if I point my client to NOD32s server instead of my local mirror it just times out.
     
  9. EmpereurZorg

    EmpereurZorg Registered Member

    Joined:
    Jan 12, 2010
    Posts:
    12
    Re: 4813 signature problem ?

    For now, ERA is failling with :
    [2010-01-28 14:44:47.377] V1 [4b616f1a0000] [00000718] <UPDATER_ERROR> Creating mirror failed, code: 0x2104, description: SERVER_ERROR
    [2010-01-28 14:55:26.715] V1 [4b616f1a0000] [00000718] <UPDATER_ERROR> Creating NOD32 v2 mirror failed, (code: 4, description: Server error, code: 9)
     
  10. Jocke

    Jocke Registered Member

    Joined:
    Jun 25, 2007
    Posts:
    2
    Location:
    V?ster?s, Sweden
  11. kahansen

    kahansen Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    1
    So.. I am definitely not alone in this problem then..
     
  12. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    57,721
    Location:
    Texas
    Threads have been merged.
     
  13. elmolincoln

    elmolincoln Registered Member

    Joined:
    Sep 14, 2009
    Posts:
    16
    Same problem here.....started about 4:30am CST.
     
  14. Ned32

    Ned32 Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    2
    Same problem here.
    It appears to be happened after an update of the program modules. After that it was not possible anymore to download new signature updates.

    It can be solved by un-installation and re-installation of the clients, but hopefully this will not be the only solution...
     
  15. Bepo

    Bepo Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    1
    Same problem here.
     
  16. Mister Natural

    Mister Natural Registered Member

    Joined:
    May 10, 2007
    Posts:
    225
    Location:
    3rd density St. Louis
    Me too, I cleared the update cache on the server, rebooted it and now I am clearing the cache on problematic clients which hopefully will fix the problem. Looks like a problem with the computers that received the 4812 signature.
     
    Last edited: Jan 28, 2010
  17. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    This is because of a compatibility check for new modules. The check is going to be suspended temporarily so that everybody who has updated the program modules will receive further updates.
     
  18. chvss

    chvss Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    8
    Does this mean that updates will automatically start working again, or do we need to do something on our end?
     
  19. Ned32

    Ned32 Registered Member

    Joined:
    Jan 28, 2010
    Posts:
    2
    I can confirm that clients that were stuck on 4812 are now updating to 4814.
    But the clients that were on 4813 cannot yet update to 4814.
    Is this as expected?

    Update:
    No, only a few clients with 4812 were able to update to 4814. Most of them are still unable to update, as are the clients with 4813.

    Update 2:
    It appears that clients with 4813 can now update to 4814.
     
    Last edited: Jan 28, 2010
  20. SalC

    SalC Registered Member

    Joined:
    Jun 30, 2008
    Posts:
    31
    On a W2K8 server w/ 4.0.474:
    I'm stuck on 4812 and can't get to 4814.. It's trying though..
     
  21. mop_se

    mop_se Registered Member

    Joined:
    Jan 16, 2006
    Posts:
    2
    I have 17 clients with 4814, 44 clients with 4813, about 800 clients stuck on 4812 (and about 200 older - not online).
     
  22. Mister Natural

    Mister Natural Registered Member

    Joined:
    May 10, 2007
    Posts:
    225
    Location:
    3rd density St. Louis
    Clearing the cache on clients is not fixing the problem. They are stuck on 4812.

    Actually users with 4813 are stuck too. My pc is stuck at 4813, I went into the program settings, cleared the cache and then tried a manual update but it failed.
     
    Last edited: Jan 28, 2010
  23. JesusV

    JesusV Former ESET Support Rep

    Joined:
    Jan 21, 2010
    Posts:
    93
    3 new modules were released today which are Antistealth module version 1015 Self-Defense module version 1011 and sysinspector module version 1214. These modules contain various changes and optimizations as well as fixes for some compatibility issues. These modules were tested on the pre-release servers for several weeks without an issue.

    If you're encountering the following error "Error downloading file from update servers." This error message is caused by the fact that the users have different (newer) modules then those currently residing on our update servers. This issue is currently being addressed and will be solved in our next virus signature update within a few hours.

    Update: Issue has been resolved. Clear your update cache and all should be well.
     
  24. csedgbeer

    csedgbeer Registered Member

    Joined:
    May 15, 2007
    Posts:
    16
    same here, altho on a smaller scale, most of my clients now gone to 4814 but still a load stuck on 4812 and failing to update
     
  25. elmolincoln

    elmolincoln Registered Member

    Joined:
    Sep 14, 2009
    Posts:
    16
    My system is starting to recover now, systems are gradually updating.....Thanks!
     
Thread Status:
Not open for further replies.