AAVM - scanning error: ClientRqDispatchThread

[JeroenBos]

Hello,

We've installed Avast (Managed) on our Exchange 2007 server (W2K3 64bits), after some problems with the store not starting (deployed again with the exchange 2007 ticked in the management console) everything seems to work normally but in the eventlog we have a huge buildup of the following events:

source: Avast! Eventid: 90

AAVM - scanning error: ClientRqDispatchThread: SessionID not found - global map corrupted??, 00004099. 

The error appears about 30 times every second and results in a 30% load of the CPU's, anyone an idea?

regards, Jeroen Bos

[nomis]

Hi, I'm Having the same problam. is there any answer for this issue?

[ToM ™]

Hello, do you have single exchange or cluster, thanks.

[williamXP]

Hello, do you have single exchange or cluster, thanks.

I am having the same problem.  I am running a single exchange on windows 2003 64bit.
Any ideas?

[ToM ™]

Delete the error log and adjust your log-settings to "Critical error" it should helps.

[williamXP]

Delete the error log and adjust your log-settings to "Critical error" it should helps.

This is quite a disappointing answer.  Ignoring the message does not mean the problem is fixed....

[Vlk]

In this case, it does.
This particular entry is (unfortunately) logged by mistake (due to a subtle bug in the Exchange 2007 provider).
It has no effect on the functionality of the product.

Apologies for the inconvenience.


Thanks
Vlk

[williamXP]

In this case, it does.
This particular entry is (unfortunately) logged by mistake (due to a subtle bug in the Exchange 2007 provider).
It has no effect on the functionality of the product.

Apologies for the inconvenience.


Thanks
Vlk

Thanks for the explanation.  It is nice to know that error message does not mean a error.....

[jim Bray]

Can you tell me how to do this, I cant find how to alter the error log settings.

Jim