Nod32 3.0.65 on a Server Crash

[threatac]

After being afraid to do that for a while i changed the av on one of my servers.
this servers carry the sql server\fs\Dc\Dfs. it was runnig a v2 and was ok and now i installed nod32 v3.0.65 x64 on it. it crashes two times since.


i added exclutions on sql server. i dont no what else to do.
still crash.
any idea?

[Marcos]

Have you installed v3.0.650 just recently? If it was more than a week ago it could be the problem with corrupted files in ThreatSense cache. In such case, updating the engine to v. 3121 or newer (the current version is 3145) and restarting the computer should help. Alternatively, you can either uninstall EAV and reinstall it, or delete the content of the "C:\Users\All Users\Application Data\ESET\ESET NOD32 Antivirus\Charon" folder in safe mode.

[threatac]

{QUOTE-> Have you installed v3.0.650 just recently? If it was more than a week ago it could be the problem with corrupted files in ThreatSense cache. <-QUOTE}
i installed 2 days ago.
now i'm at home and the whole network at work is not responsive.
what to do?:doubt:

[goran_larsson]

{QUOTE-> After being afraid to do that for a while i changed the av on one of my servers.
this servers carry the sql server\fs\Dc\Dfs. it was runnig a v2 and was ok and now i installed nod32 v3.0.65 x64 on it. it crashes two times since.


i added exclutions on sql server. i dont no what else to do.
still crash.
any idea? <-QUOTE}

It would probably be a good idea to exclude the sysvol directory aswell as the sql directories.

Regards Göran

[YeOldeStonecat]

Have you done the proper exclusions for servers? Including the "sysvol" directory mentioned above..but there are many more exclusions you should do for your AV product (whatever brand) on servers.

[threatac]

I'll check it.
thanks.:isay: