Exchange crashes after 4.8.1049 program update

[patyi]

Dear pals,

Same happened over here. Tried the followings, without any positive result:
- checked Disable avast self defense module in troubleshooting
- checked skip checking of digital signature of infected files in troubleshooting
- unchecked enable push iAVS at update(basic)/details

Every time after I restarted the exchange store service, the errors came back within an hour.

At last I disabled transport level in exchange scanning settings. This seems to be working. The email flows by eighty minutes now.

Anyways who knows what exactly does the disable of the transport level scanning...

Since this is a really-really frustrating error (hey, guys at avast! this is really it!>) now I'm thinking about moving back to a prev. avast version. A working one.

[ToddU]

I've tried unchecking the box >> didn't work.

I've tried (about a week ago) terminating the smtp scan >> didn't work.

I'm going to apply the MS fix and see if that works and report back.

[sangwen]

I'm having the exact same issue. It's been going on for about 5 days now. I receive the follow error over and over.

Event Type:   Error
Event Source:   MSExchangeTransport
Event Category:   Exchange Store Driver
Event ID:   348
Date:      12/16/2008
Time:      2:13:49 AM
User:      N/A
Computer:   SRVSBS01
Description:
A message could not be virus scanned - this operation will be retried later. Internet Message ID  <320804502.1085292.1229411625063.JavaMail.app@ech3-cdn09.prod>, Error Code 0x0.

Usually, it is also preceeded by:

Event Type:   Information
Event Source:   MSExchangeTransport
Event Category:   SMTP Protocol
Event ID:   7513
Date:      12/14/2008
Time:      3:00:45 AM
User:      N/A
Computer:   SRVSBS01
Description:
Microsoft Exchange Intelligent Message Filter was refreshed. Microsoft Exchange Intelligent Message Filter is now enabled. A refresh occurs when the SMTP service is  restarted or Microsoft Exchange Intelligent Message Filter is updated.

As someone else suggested earlier in the thread, I can temporarly resolve it by restarting the Exchange Information store. Then I have to force the connection on any messages pending submission.

I have a few hours to troubleshoot this right now, any ideas?

Edit: This is on a SBS 2003 SP2 server

[ToddU]

ms patch didn't work.  version of exchange is already above that of the patch.  so...

[alfonz]

Try this

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

and disable transport level in Avast task->Resident protection ->Exchange2000/2003 Scanning settings.

...maybe

- checked Disable avast self defense module in troubleshooting
- checked enable push iAVS at update(basic)/details
- unchecked Scan at transport level (Exchange 2003 only)
- restart/reload all stuffs

Its working to me momently - no errors... i put one beer to early celebrate 
(SBS 2003 SP2 + Postfix MailGateway)

[Meneerik]

OK, one more thing to try:

1. disable the MS SMTP 2000/2003 provider in avast ("Terminate" it); keep the Exchange 2000/2003 provider enabled
2. use iisreset to restart the inetinfo.exe process (which hosts the SMTP service).


Thanks
Vlk

This seems to work. 

(SBS 2003 SP2 + GFI MailEssentials )

[patyi]

Only disabling transport level scanning is enough. It is working for me since 4pm yesterday.
Don't bother with disabling avast self defense module or disabling push iAVS at update(basic)/details. Only uncheck transport level checkbox in exchange scanning settings.

Anyway, who knows what this option exactly mean?

[alfonz]

Anyway, who knows what this option exactly mean?

"New for Exchange 2003 is the ability to operate at the transport level - meaning that all items will be properly scanned even if deployed on a gateway/border server that just passes the mails through, without saving them to the information store."

By the way, i newer put out MS servers (like exchange) directly to the net, so i using mail gateway with spam and virus filtering.  If you using exchange/IMF directly, turn off transport level is not too safe.

[OLT Support]

Hi all
i am having this same problem since the update was released.
i have tried the method stated below, but am still having the issue.

"Disable transport level in Avast task->Resident protection ->Exchange2000/2003 Scanning settings."

any news when this problem will be resolved?

Dale

[tandee]

Hello all,
unfortunately I have the same problem   :'(  :'( with several customers running exchange 2003, reading through the posts the only thing that would probably work is the previous version of avast but then you'll probably receive the " your product requires update" msg.
also with reference to an earlier post (if i've understood) its not really a good thing to stop scanning at transport level afterall you ideally want to stop the 'bad stuff' before it hits your database 'edb'. If you get a lot of mail this could probably cause performance and user related issues...Any thoughts?? any news on a fix??

[Meneerik]

Hmmz the problem is back again......

nothing changed here.. and sudden there was no incomming mail annymore... 

[ToddU]

I finally had to uninstall and go back to version 4.7.  It works just fine.  I have it set to only update the virus definitions.  At this point there was not another solution.  After two weeks of email issues this was the only viable alternative.  I'll turn on the program update feature as soon as this is fixed.

[Vlk]

ToddU, did you get my email (that I sent to you about 6 hours ago)?


Thanks
Vlk

[ToddU]

Sorry no I hadn't checked email yet.  I've responded to your email.  I'll give it a shot.

[kwg]

Vlk,

Please check your e-mail. The solution you proposed is working very well indeed!

kwg