Avast! Interfering with MS-Office file saving?

Avast Business Avast Distributed Network Manager
1

The users on my network have been receiving a pop-up that reads “Document Not Saved” when they save a .doc and .xml file onto the share folder on our computer’s server.

Here’s an example of the message that appeared in the Avast! log was the following:

AAVM - scanning error: x_AavmCheckFileDirectEx: avfilesScanReal of \192.168.0.254\share\Company Forms\Purchasing\E8AF0016.tmp failed, 0000001E.

When I looked on the server’s event logs, it had a concurrent error ocurring server-side with Microsoft Exchange, which would explain why I was able to save non-Office files, such as AutoCAD drawings, but it was only office files which were bringing about this error.

I went into each of the workstations (there are only 10 so it was not difficult to do this) and added an Exclusion on there for the .doc, .xls, and .tmp files, and now there are no more errors with saving files.

My problem now is, is Avast! going to still scan incoming files from e-mails and the like, or am I leaving a big security gap in my network? What other solutions can I utilize that will allow for these scans to take place, but that will not conflict with the Microsoft Exchange server?

2

The error is a read error. Weird too, never saw that happen.

Do the users have read access to the folders that they are saving to? Opposed to having write-only access or something screwy like that?

Are you even having the problem anymore (I know it’s an old post).

3

the problem is now that you left macro virussen a little bit opened, they usually settle in the office documents (if you get any)…

sounds you have set your temporary (office) directory on a/the share. Maybe you should put your temporary on the local computer.
avast is now scanning the original document but also the tmp document that you are writing/accessing which leads to another connection on the server.
you could also look into the share properties to see how many users can connect at the same time, im not sure if accessing the same share on 2 different files counts as 2 connections to that share, but you could look into that and raise the ammount of (concurrent) connections to the share(s)