Nod32 "incorrect system date" error

Discussion in 'NOD32 version 2 Forum' started by krush0, Dec 17, 2004.

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

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    I am getting this error every time Nod starts or when starting
    a scan - after clicking ok it continues on as normal. reinstall fixes
    it for a short time but then the error comes back - BTW the date is fine.
     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi Krush0, welcome to Wilders.

    Do you have the correct country chosen for your system?

    Can you please post your Nod32 System Tools> Information here, as per screen shot.

    Cheers :D
     

    Attached Files:

  3. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    Location is correct

    info:
    NOD32 Antivirus System information
    Virus signature database version: 1.952 (2004121:cool:
    Dated: Saturday, December 18, 2004
    Virus signature database build: 5077

    Information on other scanner support parts
    Advanced heuristics module version: 1.011 (20041126)
    Advanced heuristics module build: 1067
    Internet filter version: 1.002 (2004070:cool:
    Internet filter build: 1013
    Archive support module version: 1.024 (20041125)
    Archive support module build version: 1104

    Information on installed components
    NOD32 For Windows NT/2000/XP/2003 - Base
    Version: 2.12.3
    NOD32 For Windows NT/2000/XP/2003 - Internet support
    Version: 2.12.3
    NOD32 for Windows NT/2000/XP/2003 - Standard component
    Version: 2.12.3

    Operating system information
    Platform: Windows XP
    Version: 5.1.2600 Service Pack 2
    Version of common control components: 5.82.2900
    RAM: 1024 MB
    Processor: AMD Athlon(tm) 64 Processor 3200+ (2309 MHz)
     
  4. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Are you using the Trial or Commercial version of Nod32?

    If the Commercial version, can you please do the following:

    Download a FRESH copy of Nod32 from www.nod32.com

    Uninstall your current version.

    Remove the Eset Folder from C Drive> Program Files.

    Install the FRESH copy of Nod32 that you downloaded above.

    Let us know how you go…

    Cheers :D
     
  5. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    Thanks
    I am using the commerical version - I will try another install.
     
  6. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    Still doing it after a cold boot ok when first installed - its really starting to bug me.
     
  7. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Please double-click the clock in the right-hand lower corner of your screen and post a screenshot of the system date settings here.
     
  8. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    I have checked it over and over - still nothing
     

    Attached Files:

    Last edited: Dec 18, 2004
  9. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Is your time zone correct in the same screen shot.

    Can you please post a screen shot of the error message, as well as a Nod32 Control Centre> Logs> Event log.

    And hangf in there, we will find a solution for you, given time... ;) :D

    Cheers :D
     
  10. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    Ok hear you go


    Time Module Event User
    17/12/04 17:05:53 PM NOD32 Incorrect system date. Check the Date set on your computer.

    17/12/04 17:00:10 PM Kernel The virus signature database has been updated successfully to version 1.952 (2004121:cool:.
     

    Attached Files:

  11. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Can you please try setting your time zone to another country, click apply. restart your system, and then reset it back to your country and repeat.

    Can you also double check in the Windows> Control Panel that your Regional and Language Options are correct in all locations.

    Cheers :D
     
  12. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Your screen shot is showing 17th of Dec and Nod32 is showing 18th of Dec. There is a time difference somewhere there.

    Cheers :D
     
  13. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    Yes you are right - I think I found the problem
    bios date was out by a day (17-12-04) for some odd reason
    I changed it and all is working - I hope that was it.
     
  14. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Good to see, let us know how you go after a day or so...

    Cheers :D
     
  15. sir_carew

    sir_carew Registered Member

    Joined:
    Sep 2, 2003
    Posts:
    884
    Location:
    Santiago, Chile
    Good to see that your issue was fixed.
    Note: When the time/date start to fail in BIOS, one of the main reason is that the battery of your PC has failed. The battery durations is relative: many years. This battery is used for keep the correct date/time when you shutdown the computer.



     
  16. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,640
    Location:
    Throughout the USA and Canada
    It's potentially worrying if things stop working on cmos battery failure...

    Was this just a warning from NOD32 - or do any features/functions within the NOD32 system cease to work when cmos batteries fail?
     
  17. sir_carew

    sir_carew Registered Member

    Joined:
    Sep 2, 2003
    Posts:
    884
    Location:
    Santiago, Chile
    Well, Windows/Linux or other OS can start to detect new hardware every time you start the PC even if the hardware is old and was recognized time ago.

     
  18. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Nod32 was continuing to update, it was however warning that there was a date inconsistency with the users computer.

    Cheers :D
     
  19. krush0

    krush0 Registered Member

    Joined:
    Dec 17, 2004
    Posts:
    8
    Thanks - the MoBo is only 2 weeks old - not sure why yet that the
    bios clock took a step back - NOD32 was the only thing that complained about it - and I am running quite a few programs - firewall didnt have an issue
    NOD worked ok but was constantly poping up the error message.
     
Thread Status:
Not open for further replies.