Undocumented serious error?

Discussion in 'ESET NOD32 Antivirus' started by Togg, May 18, 2011.

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

    Togg Registered Member

    Joined:
    Jun 24, 2003
    Posts:
    177
    Definitions update (6133) just failed with the following error message;

    'Undocumented serious error (0x101a)'

    6132 installed earlier without any problem so this is a recent development. Everything else seems to working OK. Any ideas?
     
  2. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Please follow the instructions to address this issue here

    Thank you.
     
  3. Togg

    Togg Registered Member

    Joined:
    Jun 24, 2003
    Posts:
    177
    Thank you for your prompt response. I should obviously have done my own search before bothering the forum! As it happens, I did actually do a restart before I read your post and the update proceeded successfully at my next attempt.

    I have had a few update failures before and resetting the parameters has fixed things. I see from my event log that there were three 'normal' failures 'an error occurred while downloading update files' on 12th May (busy servers?), but this is the first time I have seen the 'serious error' message, hence the panicky post.

    Thanks again!
     
  4. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    You are most welcome, if there are additional issues or errors regarding this, please post them back to this thread.

    Thanks !
     
  5. duijv023

    duijv023 Registered Member

    Joined:
    Feb 16, 2006
    Posts:
    230
    Location:
    Rijnsburg, Netherlands
    Hi,

    In the meantime we're in August, but still i see these errors occuring.
    And what is worse: I'm seeing it on servers too. My customers are not very happy with my message that their server needs a reboot. Why is this issue occuring so often?? What is the cause? And more important: What is ESET doing to prevent this issue to occuro_O

    This should have been fixed a long time ago in my opinion o_O
     
Thread Status:
Not open for further replies.