Link to home
Start Free TrialLog in
Avatar of bentleyforbes
bentleyforbesFlag for United States of America

asked on

Virus scan warning in Exchange 2007application event viewer

We recently installed Exchange 2007 SP1 and are trying to work out all the warnings/errors before we go ahead with setting up an additional exchange 2007 server. In the application log, we get this message:
Source: MSExchangeIS
Category: Virus Scanning
Event ID: 9874
Unexpected error 0x80040109 occurred in "EcProcessVirusScanQueueItem" during virus scanning.
Mailbox Database: /o=Company /ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=BFMAIL/cn=Microsoft Private MDB
Folder ID: e-65F3
Message ID: 1-F9A60F6B
We are running TrendMicro 7.6.1095
I was unable to find anything on this event ID so any help would be appreciated.
Avatar of Zanemwest
Zanemwest
Flag of South Africa image

there may be a scanmail version compatibility issue
you should be running scanmail 8.0 for exchange 2007 at least.

upgrade
Avatar of bentleyforbes

ASKER

We are already running TrendMicro ScanMail 8.0 - which I have been told is the latest version.
ASKER CERTIFIED SOLUTION
Avatar of MarketingDrive
MarketingDrive

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I as well am running Exchange 2007 SP1 with Trend Micro Scan Mail 8.0.  I too have started to receive the exact message once upgrading to SP1.  
Avatar of fdatateknik
fdatateknik

We are getting the same errors with F-Secure Antivirus for Exchange 7.10 on Exchange 2007 SP1. Does anyone have more info on this?
We are also getting the same thing using McAfee Groupshield 7.0.
Also getting the error using Symantec Mail Security 6.0.5...
Is there any solution other than Microsoft having a problem with their vsapi?  Are they releasing a fix for this or have they?
Same problem here with Eset - Nod32
Same problem. Using ForeFront Security
Probably, in the mail database in Microsoft Exchange Server, there are violations of logical structure.
Try to stops the bases and use
ISINTEG-s ServerName-fix-test alltests

Also check the article http://www.microsoft.com/downloads/details.aspx?FamilyID=99da32e0-d9e3-4156-aabf-8369bf96e3e7&DisplayLang=en
This has been solved in Exchange Server 2007 Update Rollup 7:

http://support.microsoft.com/kb/952778/