Problems with Remote Administration Server

Discussion in 'Other ESET Home Products' started by karolis, Oct 21, 2008.

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

    karolis Registered Member

    Joined:
    Oct 21, 2008
    Posts:
    3
    I've submitted this problem to Nod32 support last Friday and still haven't received any reply. So maybe here someone will guide me.

    I have installed Remote Administration Server on Windows 2000 server and successfully deployed over 60 clients. Couple of days later I've noticed that disk performance on that server dropped substantially. As there was no Nod32 Antivirus installed, I've decided to look for problem elsewhere. Took me a day to figure that it was Remote Administration Server service which was causing all the slow down. Here are graphs done by HDTune with service enabled and disabled:

    http://banginis.nomagic.com/shared/hdd_nod_enabled.png

    http://banginis.nomagic.com/shared/hdd_nod_disabled.png

    System runs on Windows 2000 Server with software RAID1. Have any idea how to fix this isssue? Repair didn't helped. Thanks!
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Does the server replicate to a master server or other lower servers replicate the data to this one? This could also happen if clients generate too much log records (ie. if they are set to log all scanned files or blocked connection attempts).
     
  3. karolis

    karolis Registered Member

    Joined:
    Oct 21, 2008
    Posts:
    3
    Problem persists even after disconnecting from network. After complete reinstall of ESET server and console, performance got worse.
     
  4. karolis

    karolis Registered Member

    Joined:
    Oct 21, 2008
    Posts:
    3
    The problem was caused by ODBC Tracing:
    http://support.microsoft.com/kb/268591

    More specifically it was bloated sql log (4gb) at c:\windows\temp\sql.log which caused slowdown. After stopping ODBC Tracing and removing this log everything went fine.

    Thanks to ESET support for their assistance in solving this non trivial issue.
     
Thread Status:
Not open for further replies.