AV V4 Upgrade - Event Log Errors 6004 and 3019

Discussion in 'ESET NOD32 Antivirus' started by Hexaguano, Mar 3, 2009.

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

    Hexaguano Registered Member

    Joined:
    Jan 4, 2005
    Posts:
    100
    Upgraded AV from v3 build 684 to v4.
    XP SP3.

    Every access of a networked drive throws the following error:

    Event Type: Error
    Event Source: EventLog
    Event Category: None
    Event ID: 6004
    Date: 3/3/2009
    Time: 7:31:39 PM
    User: N/A
    Computer: OFFICE
    Description:
    A driver packet received from the I/O subsystem was invalid. The data is the packet.

    A few of these are in there as well:
    Event Type: Warning
    Event Source: MRxSmb
    Event Category: None
    Event ID: 3019
    Date: 3/3/2009
    Time: 7:26:44 PM
    User: N/A
    Computer: OFFICE
    Description:
    The redirector failed to determine the connection type.


    Back to version 3 and all is well again.
     
  2. xMarkx

    xMarkx Registered Member

    Joined:
    Dec 1, 2008
    Posts:
    447
    Hello,

    The final verions of ESET NOD32 Antivirus and ESET Smart Security version 4 just came out yesterday. Therefore, since they are brand new releases, there are still probably many bugs in them. If version 3 works for you, I'd recommend staying with v3 (I think I will) for a few weeks until a new build(s) is released to fix the bugs or more modules are updated to fix the bugs. Maybe someone who has experience with v4 already can better assist you in resolving your problem.

    However, you could try this:

    Completely remove v3 before installing v4:
    • Start>All Programs>ESET>ESET NOD32 Antivirus>Uninstall.
    • Delete the INFCACHE.1 file located in C:\WINDOWS\inf folder.
    • Restart your computer.
    • Delete the ESET folder in C:\Program Files, C:\Documents and Settings\All Users\Application Data\ESET, and
      C:\Documents and Settings\%USER%\Application Data\ESET
    ESET's Knowledgebase article on how to remove EAV/ESS

    Then download the ESET NOD32 Antivirus v4 Final installer again and try to install it. Make sure you don't have anything running in the background that could interfere with it.

    Please let me know if this resolved your issue or update me if it didn't.

    Regards,

    Mark
     
  3. goran_larsson

    goran_larsson Registered Member

    Joined:
    Jan 25, 2008
    Posts:
    51
    Location:
    Stockholm, Sweden
    This was first encountered with version 3, we have plenty of these in the eventlog of the clients from version 3.0.566 until 3.0.657 when they finally dissappeared, although there was still some 3019 events left we were spared by the 6004's

    However it's back in 4.0.314, I would expect the developers at ESET to have learned their lesson by now but obviously they haven't since its back again.

    Let's see how many versions goes by before they manage to fix it again :)

    /Goran
     
  4. weeksgroove

    weeksgroove Registered Member

    Joined:
    Sep 25, 2008
    Posts:
    3
    Exact same issue after upgrading to v4.

    Which was the exact same problem as early v3.

    And i completely agree with the comment above. How can you fix it in v3 and then re-break it in v4?
     
  5. funkydude

    funkydude Registered Member

    Joined:
    Apr 5, 2004
    Posts:
    6,853
    The network filtering completely changed in v4.
     
  6. jeremyf

    jeremyf Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    61
    and?

    :p
     
  7. funkydude

    funkydude Registered Member

    Joined:
    Apr 5, 2004
    Posts:
    6,853
    this:

     
  8. jeremyf

    jeremyf Registered Member

    Joined:
    Jul 14, 2008
    Posts:
    61
    LOL!

    The orginal statement of "How can you fix it in v3 and then re-break it in v4?" is totally accurate. By stating "The network filtering completely changed in v4", means nothing.

    You see, the "fix" is the "network filtering completely changed", and then the "re-break", is the exact problem that occurred before in an early version, occurs again. Maybe for different reasons internally (because the "network filtering changed"), but to the end user, the difference is moot.

    Do you understand?

    It is like someone asking "My 2009 Ford truck slips out of gear all the time! My 2008 Ford truck did that, but the dealership fixed it!" and you answering, "They totally re-did the transmission on the 2009"! To the end-user, all they care about is the same problem is back, and therefore the statement, "How can you fix it in 2008 and then re-break it in 2009?" is totally appropriate.

    funkydude, I am starting to see why you are a "very frequent poster".
     
    Last edited: Apr 7, 2009
  9. goran_larsson

    goran_larsson Registered Member

    Joined:
    Jan 25, 2008
    Posts:
    51
    Location:
    Stockholm, Sweden
    the 6004's have almost dissapeared again probably thru some mysterious module update but most of it seems to be gone.

    The 3019 shows about once a day or so.


    Cheers
     
Thread Status:
Not open for further replies.