SBS2003 EMSX4.2.10019.0 not updating after v5495 (20101001)

Discussion in 'Other ESET Home Products' started by duijv023, Oct 4, 2010.

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

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    Hello,
    I know October 1st 2010 is a special date that many people want to remember, but not in my EMSX :D

    the SBS server is configured to update from the internet and gives "undocumented serieous error (0x101a)"
    I cleared the updat cache, but after that only update.ver (3KB) is downloaded.

    Do I need to do the same after the buggy update 5418 (=clearing update cache and reboot?) Or can i fix this without reboot?)
    I hope so, because SBS reboots take quiet some time :(

    Status of ESMX:
    Virus signature database: 5495 (20101001)
    Update module: 1031 (20091029)
    Antivirus and antispyware scanner module: 1285 (20100820)
    Advanced heuristics module: 1114 (20100827)
    Archive support module: 1122 (20100826)
    Cleaner module: 1048 (20091123)
    Anti-Stealth support module: 1021 (20100811)
    Antispam module: 1014 (20100212)
    SysInspector module: 1217 (20100907)
    Self-defense support module : 1016 (20100404)
    Mail server protection module: 1005 (20100112)

    Server itself:
    32bit SBS 2003 v5.2.3790 SP2
    Intel XEON CPU, 4 GB memory

    Greetings from Holland
     
  2. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    update:
    Another colleague had very strange behaviour on another server (also SBS2003). Mailflow was partly interrupted.
    (most (not all) normal e-mail was delivered, but mail from distribution groups was NOT delivered to mailboxes, only to public folders and NOT readable)

    The eset service seemed to hang. After restarting the Eset service and the exchange services it was resolved.

    After checking the log:
    Last succesful update was on Oct 1st to v5495. as soon as the ESET service was restarted, it automatically updated to most recent. So it is not the same as the original posting, but seems related to it....

    "5495=unpredictable behaviour" o_Oo_Oo_Oo_O
     
  3. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    Same procedure as earlier did the trick:
    - clear update cache
    - reboot
    - update ESMX

    ..... hmmm very strange.......

    but the important part: case closed...
     
Thread Status:
Not open for further replies.