NOD scheduled scan tasks not performing

Discussion in 'ESET NOD32 Antivirus' started by vtol, Oct 19, 2010.

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

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    W7 64bit / NOD 4.264.12

    Virus signature database: 5541 (2010101:cool:
    Update module: 1031 (20091029)
    Antivirus and antispyware scanner module: 1288 (20101016)
    Advanced heuristics module: 1114 (20100827)
    Archive support module: 1122 (20100826)
    Cleaner module: 1048 (20091123)
    Anti-Stealth support module: 1022 (20100812)
    SysInspector module: 1217 (20100907)
    Self-defense support module : 1018 (20100812)
    Real-time file system protection module: 1004 (20100727)

    since 16th October 2010 the scan scheduled for daily execution is not being performed so anymore, just it seems every second day only. not sure what this failure would coincide with other than the update to the new scanner module 1288

    19-10-2010 11-44-10.png
     
  2. toxinon12345

    toxinon12345 Registered Member

    Joined:
    Sep 8, 2010
    Posts:
    1,200
    Location:
    Managua, Nicaragua
    Are you using a laptop computer?
     
  3. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    does it matter, if so how? for the battery option? it has been on AC throughout, no scan on 17th and 19th
     
  4. Thankful

    Thankful Savings Monitor

    Joined:
    Feb 28, 2005
    Posts:
    3,731
    Location:
    New York City
  5. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    I mainly reported this here as feedback for Eset to look into it. meantime the module got updated to 1290, will see over the next 96 hrs whether it is reoccurring.
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Actually we haven't been reported such an issue yet. However, reproducing this issue may take a while as it is a daily task and I'd prefer not to experiment with the date in BIOS to reproduce this issue.
     
  7. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    Antivirus and antispyware scanner module: 1290 (2010101:cool:

    no scan 19.10
    scan 20.10
    no scan 21.10

    the pattern seems established, scan missed every second day
     
  8. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    what Eset's take on this, cause it is still happening, i.e. missing the scan every other day?
     
  9. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    We were unable to reproduce it on Windows 7 x64. Do you have Self-defense enabled or disabled? If enabled, try disabling it just to see if it makes a difference. Also try scheduling another task run on a daily basis that will run another application (e.g. the calculator) and see if it's run every other day as well. One more thing - I assume you're logged in as an administrator and have UAC disabled?
     
    Last edited: Oct 26, 2010
  10. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    correct
    there are various others tasks scheduled to perform on daily basis. just checked the logs and those are reported to have executed according to schedule, thus only NOD not performing as scheduled.
    why would I do that - the self-defense module did not get updated and the daily scanning task was performed well prior to the 1288 Antivirus and antispyware scanner module. It seems though that once a manual scan of single file invoked prior to the scheduled scan the latter would trigger even on date where expected to miss - see on October 23rd

    26-10-2010 09-44-14.png

    there were a few occurrences in the past where Eset could not reproduce issues in the lab although happening for users in real world environment
     
  11. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    NOD missed a scheduled scan again last night (or failed to log it)

    W7 64bit / NOD 4.2.64.12 with dev exe/dll

    Virus signature database: 5606 (20101110)
    Update module: 1032 (20101025)
    Antivirus and antispyware scanner module: 1293 (20101110)
    Advanced heuristics module: 1114 (20100827)
    Archive support module: 1123 (2010110:cool:
    Cleaner module: 1049 (20100604)
    Anti-Stealth support module: 1022 (20100812)
    SysInspector module: 1217 (20100907)
    Self-defense support module : 1018 (20100812)
    Real-time file system protection module: 1004 (20100727)
     
  12. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Theoretically that could be because of the scan crashing. Should another scan be missed, try scheduling scans by running ecls.exe as an external application instead of the standard scan task and use the "--log-file=log.txt" parameter which will enable logging to a file. In such case, you should get an incomplete log if the scan crashes so this would confirm or deny my theory.
     
  13. vtol

    vtol Registered Member

    Joined:
    Apr 8, 2010
    Posts:
    774
    Location:
    just around the next corner
    why would scan crashes not be logged/dumped anymore, neither by WIN nor by NOD as both did until recently?
     
Thread Status:
Not open for further replies.