Hi guys

I have since the update to 6.0.2.551 the following Problem:

the realtime and scriptprotection crashd sometime with this message:

Severity level: Critical
Event time: 18.08.2008 11:03:08
User name:
Computer name:
Description: An internal error has occurred. Error code: 0x00D1. Subsystem code: 0x4. To find more details go to technical support site: http://support.kaspersky.com/error_prod?key=B4X209X.

And that at a machine with 2x 1.86GHz Intel Xeon with 4GB Ram with Win2k3 x64

What is here the problem? Also is the server since the update really slow with activated realtime protection. But the realtime protection is only set on high speed.

thx for any help

Hi

i'm not sure that is ralate with the Limitations of KAV EE 6.0.2.551 here:
http://support.kaspersky.com/faq/?qid=208279871

Good luck

I see no limitations that my problem explain

Hello.
Please look here: http://www.kaspersky.com/anti-virus_window...rver_enterprise. There are system requirements described. Unfortunately, WSEE has no support for 64bit version of MS Windows 2000.

As i write in the first post i have Microsoft Windows Server 2003 x64 Standard Edition as OS

I'm sorry. Missed digit 3 in 'Win2k3'.

Please tell me, how often you registered such situation? When it happens? Can you describe in common words role of your server?
If you can easily repeat the situation, could you please create and send us trace files? You can read how to enable application trace here: http://support.kaspersky.com/win_serv_ee/error?qid=208279533. We need trace for all subsystems and level of detail 'Debug'. Please set application settings as described, then start RTP task, wait for its failure, then disable tracing and gather created files.

no Problem

i have discovered the problem several times. With KAV EE MP1 and MP2 on different Servers (Win2k3 or Win2k8). It can happen when the server starts or just when he is running. The Server is our central Fileserv with arround 550 open files (different files from 200 users) that are more or less permanently open. The Datas are on a FibreChannel Raid.

Ok i have set now the traces and wait for the crash. I hope il will come and it was not just a monday failure

Thank you very much. We are very interested about this issue, especially because of the fact that we have fixed in MP2 some problems that caused situations like yours to appear.
I should only warn you that enabling traces for the whole WSEE can decrease performance of your server. Unfortunately, there is no other way for us to discover this hidden problem.

it goes maybe a little bit longer. at the moment the antivirus is stable. And the next restart is at next Patchday. I will write here as soon as i have this failure again

It comes no longer It looks like the the problem is fixed.