These errors popped up for the first time in the error log today:
2008-11-23 09:39:57 **** 924 AAVM - scanning error: OpenEventsAndMapping: OpenEvent failed!, 00000002.
2008-11-23 09:39:57 **** 924 AAVM - scanning error: ClientRqDispatchThread: OpenEventsAndMapping failed - client probably died, 00000008.
Does anybody have a list of error codes and suggested actions?
XP pro SP2++
Well file system error 8 = Not enough storage is available to process this command.
File system error 2 = The system cannot find the file specified.
Hi David. Thanks a lot.
You mean like memory (more than 1.5G free) or disk (more than 40G free in system partition)?
I’m sure that the file cannot be found. I can’t find it either, because there is no file name. 
I’d like to learn some more.
I’m not sure if it means memory or not, but I suspect not as these are file system errors. Why this might be given the available free space is beyond my limited knowledge.
The problem is that the file isn’t named in the error I would think, now all of these errors mention OpenEventsAndMapping: now my understanding of mapping is again limited but doesn’t that differ from conventional hdd partitions, perhaps this is the true problem (whatever that might be).
Are there any errors actually displayed to the screen or are you getting these just from the avast log viewer ?
If there isn’t any hard error displayed to the screen I tend to keep out of the log viewer as the errors aren’t very user friendly and more use to a tech for debugging.
Also if from the log viewer, what section are they in, Error, Warning, Notice, Info, where ?
Perhaps you have tweaked the logging level and these really are low level issues.
As I said, they are in the error log, and they also appear in the Windows “Antivirus” event log created by Avast, but apart from that no other messages or symptoms.
Those same event viewer entries come from the avast files, so they would appear in the avast log viewer and the lower the section the less of an issue they are.
As I said if there are no hard errors displayed on the screen I don’t go looking for trouble, as you find things like this which are rather unhelpful rather than helpful.
Most of what’s going on in Avast seems to be carefully planned and designed. Maybe a few unhelpful events got through QA. Let’s ask the developers to only generate helpful events. 
It’s not easy.