NOD32 Vs SQL Server 2000 SP3

Discussion in 'NOD32 version 2 Forum' started by quicko, Jul 7, 2004.

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

    quicko Registered Member

    Joined:
    Jul 7, 2004
    Posts:
    32
    Hi to you all.
    Does anybody know about incompatibility between NOD32 and Microsoft SQL Server 2000 (with Service Pack 3)
    installed on a Windows 2000 Server (with Service Pack 4)?
    MD? files have been excluded from the AMON control but the problem (which is a crash of the server) is still alive.
    Thanks.
     
    quicko, Jul 7, 2004
    #1
  2. arrowsmithmidwest

    arrowsmithmidwest Registered Member

    Joined:
    May 12, 2004
    Posts:
    165
    Location:
    Midwest
    just simply update your SQL server as much as possible and that should solve your problem, also update your imon. Email nod support for it.
     
    arrowsmithmidwest, Jul 7, 2004
    #2
  3. DiGi

    DiGi Registered Member

    Joined:
    Jul 24, 2003
    Posts:
    114
    Location:
    in the middle of nowhere
    I haven't any troubles with MSSQL2000SP3 and AMON/IMON (on local machine, developer version)...
    Maybe you can try add MSSQL's DATA folder to AMON exclusions, IMON should work fine with MSSQL..
     
    DiGi, Jul 8, 2004
    #3
  4. quicko

    quicko Registered Member

    Joined:
    Jul 7, 2004
    Posts:
    32
    Thanks.
    Analyzing the SQL logs I saw that is IMON v 2.008 that causes the crash.
    Maybe an update to v 2.009 will resolve the problem: I will let you know.
    Just another question... why this component hasn't been updated by the "update modules" utility?
     
    quicko, Jul 8, 2004
    #4
  5. Mele20

    Mele20 Former Poster

    Joined:
    Apr 29, 2002
    Posts:
    2,495
    Location:
    Hilo, Hawaii
    2.000.9 was only for those having trouble with 2.000.8 not for everyone if I remember correctly. Some were having trouble with shutting down...hanging. I think that was the issue - so 2.000.9 was for them.
     
    Mele20, Jul 8, 2004
    #5
  6. quicko

    quicko Registered Member

    Joined:
    Jul 7, 2004
    Posts:
    32
    Thanks for the info Mele20.
    It seems that a non-installation of IMON is the only way to avoid the crash of MSSQL2000SP3 on that server.
    This sound very strange because on my own machine (in which I run MSSQL2000SP3 too) I don't have any kind of problem (as DiGi).
     
    quicko, Jul 12, 2004
    #6
  7. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Blackspear, Jul 12, 2004
    #7
  8. UNICRON

    UNICRON Technical Expert

    Joined:
    Feb 14, 2002
    Posts:
    1,935
    Location:
    Nanaimo BC Canada
    I run MS SQL Server 2000 sp3 on W2K sp4 using NDO32 with no problems.

    Unlike other AV companies, thanx to ESET for not charging us 5 times as much because I run a small server.

    That was the initial reason for coming to ESET.
     
    UNICRON, Jul 12, 2004
    #8
  9. bsilva

    bsilva Registered Member

    Joined:
    Mar 24, 2004
    Posts:
    238
    Location:
    MA, USA
    I second that, because I use to run a Win2k server at home for gaming, and I didn't feel that I should pay 5 times more for it. :D
     
    bsilva, Jul 13, 2004
    #9
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...