DBX - internal error (5001)

Discussion in 'ESET NOD32 Antivirus' started by FanJ, Mar 21, 2010.

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

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,564
    NOD32 EAV 4.2.35.0 (English), XP-home SP3 (Dutch), IE6, Outlook Express.

    What does the warning from the scan-log "DBX - internal error (5001)" mean?
    And why do I get?

    Example:
    C:\Documents and Settings\(user)\Local Settings\Application Data\Identities\{lots of numbers and characters}\Microsoft\Outlook Express\(name).dbx » DBX - internal error (5001)

    Note:
    In the above example I have replaced private info.

    The warning(s) is not constistent. With that I mean that I am not getting it on the same OE sub-folders .dbx each time, and even I don't get the warning sometimes at all.
     
  2. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Is this related to a dbx back-up, Jan, or within OE ?

    Greetz,
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    In order to examine the cause of the error, we'd need to get that dbx file for perusal. I understand that this may not be possible as it most likely contains private correspondence. What you can do is ignore the error or disable scanning of email files. Even if a threat was found in it, you'd need to look it up and remove manually in your mail client. However, with integration into OE enabled emails are scanned on read which means that any possible infected attachment would be removed as soon as you open such email.
     
  4. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,564

    Thanks Randy and Marcos,

    It is happening when I do a full system scan with EAV.
    It is not a back-up of my emails (I make back-ups of my emails with Express Assist and store them on CD).

    I guess that I might ignore the warning.
    When it happens on an .dbx folder, I see that warning line for that particular .dbx folder tens of times mentioned in the scanlog, as if the scanning was trying it over and over again.
    As for the question of such a .dbx folder is infected, the answer is no. For example: I saw it happening on a .dbx folder that contains two emails and both (old) emails were coming from the Wilders board with IM's; so they cannot be infected I would think ;)
    As I said, it is not happening every time on the same .dbx folder(s).
    BTW, I often manually compress my .dbx folders in Outlook Express.

    Maybe indeed better to ignore these warnings...
     
  5. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    If it was possible to provide us a reasonably small dbx on which the error occurs, we'd appreciate it ;)
     
  6. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,564
    Hi Marcos,

    Please be assured that I want to help if possible, but for the moment I am a little bit reluctant due to privacy issues (not only my own privacy but also that of others). I have to think about it. I'm sure you understand.
     
  7. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Just throwing a wild one out, Jan. Perhaps the error was due to the large volume of stored *.dbx files ? You do compact OE from time-to-time, I'm sure.

    Perhaps excluding certain files and folders from real-time scanning ?

    Greetz,
     
  8. FanJ

    FanJ Updates Team

    Joined:
    Feb 9, 2002
    Posts:
    2,564
    That could very well be the reason, Randy, but I don't know.
    Yes, I do often compact (or compress; I don't know the right English word) manually.
    Anyhow, for now I'm back to 2.70.39.
    Due to private circumstances I cannot tell now if and when I'll try again.
     
  9. siljaline

    siljaline Former Poster

    Joined:
    Jun 29, 2003
    Posts:
    6,619
    Understood, Jan ! All the best.

    For your future reference OE *.dbx compacting
     
    Last edited: Mar 25, 2010
Thread Status:
Not open for further replies.