Error ESS beta 2 Virus Signatures database could not be updated

Discussion in 'ESET Smart Security v3 Beta Forum' started by PnP, Sep 11, 2007.

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

    PnP Registered Member

    Joined:
    Jun 12, 2003
    Posts:
    194
    Location:
    Italy
    My sistem is Vista x64 ultimate ESS beta 2 recieve this error..

    Virus Signatures database could not be updated

    Incompatible modules
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Have you tried running a manual update twice?
     
  3. MenosOcho

    MenosOcho Registered Member

    Joined:
    Aug 27, 2007
    Posts:
    8
    Hey, i've got the same error.
    I tried do it manually but all attempts were unsuccessful.

    Bellow the error:
    11-09-2007 7:35:36 PM Update Incompatible modules NT AUTHORITY\SYSTEM

    11-09-2007 8:34:00 PM Update Updater: retval = 0x1105, failures: 5 NT AUTHORITY\SYSTEM

    Martin
    --------
    Vista Ultimate x64
    ESS Beta 2
     
  4. Qualze

    Qualze Registered Member

    Joined:
    Nov 20, 2006
    Posts:
    13
    :doubt: I get the same error as well:

    2007-09-12 04:39:31 Update Updater: retval = 0x1105, failures: 16 NT AUTHORITY\SYSTEM
    2007-09-12 04:39:29 Update Updater: retval = 0x1105, failures: 15 NT AUTHORITY\SYSTEM
    2007-09-12 04:39:26 Update Updater: retval = 0x1105, failures: 14 NT AUTHORITY\SYSTEM
    2007-09-12 04:38:47 Update Updater: retval = 0x1105, failures: 13 NT AUTHORITY\SYSTEM
     
  5. Qualze

    Qualze Registered Member

    Joined:
    Nov 20, 2006
    Posts:
    13
    Got signature 2523 ok now. But after that i get the same error.

    I.e. it seems ESS indicates an error has occurred when no new signature exists.
    Before it just said no new signatures exists:

    2007-09-12 05:28:05 Update Updater: retval = 0x1105, failures: 1 NT AUTHORITY\SYSTEM
    2007-09-12 05:23:54 Update Updater: retval = 0x1105, failures: 0 NT AUTHORITY\SYSTEM
    2007-09-12 05:21:06 Kernel Virus signature database successfully updated to version 2523 (20070912). %BUILD="1578"%VERSIONID="2523"%DATE="131533068"%TIME="0"%VERSION="2523 (20070912)"
     
  6. scirious

    scirious Registered Member

    Joined:
    Apr 12, 2007
    Posts:
    110
    I'm also getting this one with a fresh downloaded and installed copy of ESS.
     
  7. PnP

    PnP Registered Member

    Joined:
    Jun 12, 2003
    Posts:
    194
    Location:
    Italy
    Today seems to work ... thanks to all
     
  8. MenosOcho

    MenosOcho Registered Member

    Joined:
    Aug 27, 2007
    Posts:
    8
    you're right when the ESS update itself to 2524.
    But now, few moment ago, it fail again:

    12-09-2007 11:54:08 AM Update Incompatible modules NT AUTHORITY\SYSTEM
    12-09-2007 11:54:08 AM Update Updater: retval = 0x1105, failures: 2 NT AUTHORITY\SYSTEM
    12-09-2007 11:51:06 AM Update Updater: retval = 0x1105, failures: 1 NT AUTHORITY\SYSTEM
    12-09-2007 11:09:46 AM Update Updater: retval = 0x1105, failures: 0 NT AUTHORITY\SYSTEM
    12-09-2007 10:11:28 AM Kernel Virus signature database successfully updated to version 2524 (20070912). %BUILD="1580"%VERSIONID="2524"%DATE="131533068"%TIME="0"%VERSION="2524 (20070912)"
     
  9. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    According to your signature it seems you are running Win x64. Have you already applied the patch for x64 systems that mentioned here? https://www.wilderssecurity.com/showpost.php?p=1072899&postcount=35
     
  10. MenosOcho

    MenosOcho Registered Member

    Joined:
    Aug 27, 2007
    Posts:
    8
    Yes, i did the last week.

    The new simptom is:
    The ESS was update to 2525 and i did anything, but the update module fail again. I applied the patch again to check if it can help to fix the problem, but nothing happen.
    Below the log:

    12-09-2007 12:53:04 PM Update Updater: retval = 0x1105, failures: 3 NT AUTHORITY\SYSTEM
    12-09-2007 12:52:57 PM Update Incompatible modules NT AUTHORITY\SYSTEM
    12-09-2007 12:52:57 PM Update Updater: retval = 0x1105, failures: 2 NT AUTHORITY\SYSTEM
    12-09-2007 12:49:30 PM Update Updater: retval = 0x1105, failures: 1 NT AUTHORITY\SYSTEM
    12-09-2007 12:49:16 PM Update Updater: retval = 0x1105, failures: 0 NT AUTHORITY\SYSTEM
    12-09-2007 12:09:55 PM Kernel Virus signature database successfully updated to version 2525 (20070912). %BUILD="1582"%VERSIONID="2525"%DATE="131533068"%TIME="0"%VERSION="2525 (20070912)"
    12-09-2007 12:09:54 PM Update Updater: retval = 0x0000, failures: 3 NT AUTHORITY\SYSTEM
    12-09-2007 11:54:08 AM Update Incompatible modules NT AUTHORITY\SYSTEM
    12-09-2007 11:54:08 AM Update Updater: retval = 0x1105, failures: 2 NT AUTHORITY\SYSTEM
    12-09-2007 11:51:06 AM Update Updater: retval = 0x1105, failures: 1 NT AUTHORITY\SYSTEM
    12-09-2007 11:09:46 AM Update Updater: retval = 0x1105, failures: 0 NT AUTHORITY\SYSTEM
    12-09-2007 10:11:28 AM Kernel Virus signature database successfully updated to version 2524 (20070912). %BUILD="1580"%VERSIONID="2524"%DATE="131533068"%TIME="0"%VERSION="2524 (20070912)"
     
  11. Degine

    Degine Registered Member

    Joined:
    Sep 12, 2007
    Posts:
    18
    Same problem here XP SP2 32 bit.

    Incompatible modules.

    I've tried updating like 20 times without succes, I do have database 2525 from 12-9-2007 17:10:06.

    So my update does appear to be very recent (17:47 here now) but still I get this:

    Now I get the message "Maximum protection is not ensured" With the yellow/orange I and tray icon.

    "Eset Smart Security has not been able to connect to the update server recently to check for the latest virus signature updates. Please check your netwerok connectivity and then try to update the virus signature database again."

    But I'm on an high-speed ADSL line with no other connection problems.

    Even Windows is now complaining my Virusscanner is outdated. :ouch:
    (it's only half an hour old....)


    Add this to the start up problem I have, which is discussed here:

    https://www.wilderssecurity.com/showthread.php?t=183755

    and I thinking about going back to NOD32 since I have a subscription for a full year anyway...

    But I'll just wait a few days, some good might come of this and I've enjoyed ESS untill this release.:)
     
    Last edited: Sep 13, 2007
  12. Tantawi

    Tantawi Registered Member

    Joined:
    Sep 8, 2007
    Posts:
    4
    Same exact problem, Vista x64, AntiVirus 3.0 Beta 2
     
  13. Degine

    Degine Registered Member

    Joined:
    Sep 12, 2007
    Posts:
    18
    I've noticed the auto update function does work, if you really need a new definition database quick try rebooting, though this might take a bit long due to the startup bug in this version.

    Ow and don't try to update manually to many times, if it fails to often (7~10 times) Windows will start whining about ESS being outdated, even when you've had an automatic update within the last 5 minuts. (at least on my system, Dutch XP Professional SP2 32bit)
     
  14. cupez80

    cupez80 Registered Member

    Joined:
    Jun 28, 2005
    Posts:
    605
    Location:
    Surabaya Indonesia
    i got update error but the messages is "download interupted" . everytime i try click on update button NOD32 only download update.ver then error
    nod32 upd err.JPG
     
  15. scirious

    scirious Registered Member

    Joined:
    Apr 12, 2007
    Posts:
    110
    Well, the problem of incompatible Modules had been gone till yesterday, but right now it is back. I have the virus signature database version 2531 and the update can't update with incompatible modules error again.

    Scirious.
     
  16. FMKaiba

    FMKaiba Registered Member

    Joined:
    Sep 9, 2007
    Posts:
    2
    Same problem here
    Vista Ultimate x64
    Antivirus Beta 2
    Def: 2531
     
  17. Teddy Rogers

    Teddy Rogers Registered Member

    Joined:
    Sep 16, 2007
    Posts:
    2
    Location:
    Australia
    Operating System: Vista x64
    Module: Antivirus
    Version: 3.0.290.0
    Description: Same problem as people have posted above with regard to the database updating. Here is a screenshot:

    nod32.png

    Ted.
     
  18. Venthura_EB

    Venthura_EB Registered Member

    Joined:
    Sep 14, 2007
    Posts:
    3
    Location:
    Fortaleza, CE. Brazil
    Hi!

    No Problems here with Vista 32 Ultimate and ESS beta 2 3.0.290.0 auto-updated to VSD: 2532 (20070916).

    Goof Luck!
     
  19. the_redders

    the_redders Registered Member

    Joined:
    Sep 15, 2007
    Posts:
    3
    Now showing Base File missing, def 2478. :(
     
  20. Stormboy

    Stormboy Registered Member

    Joined:
    Sep 2, 2007
    Posts:
    19
    Location:
    Australia
    I installed ESS this afternoon and first update did not work, I then clicked it maunally and it worked.
     

    Attached Files:

  21. woody72

    woody72 Registered Member

    Joined:
    Jun 26, 2007
    Posts:
    5
    when u pdated manually was it a case of simply clicking the 'update now' button or did u have to install the actual files yourself if so where did u get them tia!
     
  22. dansx6

    dansx6 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    9
    Has there been any progress on fixing the "Incompatible modules" error? This only seems to happen when NOD checks for an update and there isn't a new one. Is it correct to assume that the AV is working properly and the error message is only a nuisance?
     
  23. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    If you have Windows x64, have you already applied the hotfix I mentioned in one of my previous posts? 32-bit versions were not affected by this issue; in such case I'd suggest that you uninstall ESS, delete the ""C:\Documents and Settings\All Users\Application Data\Eset" folder and install ESS from scratch.
     
  24. dansx6

    dansx6 Registered Member

    Joined:
    Sep 6, 2007
    Posts:
    9
    Thanks Marcos, I'll give that a try. I am running Vista Ultimate x64 and I did apply the patch to fix the "base file missing" error. This one popped up a few days later. As I mentioned, I do update when there is a new update but in between I get the "Incompatible modules" error. I'll let you know what happens with a new install.
     
  25. schnaggels

    schnaggels Registered Member

    Joined:
    Sep 18, 2007
    Posts:
    1
    delete the folder C:\ProgramData\Eset\ESET NOD32 Antivirus\updfiles
    then apply the hotfix again! (copy the patch to C:\Program Files\Eset\ESET NOD32 Antivirus'; run the hotfix in admin mode)
    worked for me on Windows Vista Business x64, no errsors anymore, i can update manually or automatically without error messages :)
     
Thread Status:
Not open for further replies.