Solved

Forefront detecting all emails as virus, "Exceeded Realtime Timeout"

Posted on 2009-04-05
4
12,973 Views
Last Modified: 2013-11-22
Hi All

All our internal emails that are being sent are coming up with the following Quarantine Message:

File Quarantined

The original contents of this file has been replaced with this message because of its characteristics.
File name: "Body of Message"
Virus name: 'Exceeded Realtime Timeout"

Even if emails do not have any attachments, ie. just plain text the above error is sent to the recipient of the message.

Our Exchange 2007 mailbox store also has MS Forefront installed on that box

I've checked for the following things:

-Disabling each of the 5 default Scan engines
-Restarted Forefront Services
-Increased Max Container Scan Time parameter to 4 - 10 mins
-Rebooted server

all which had no effect on stopping internal messages from being quarantined.

For the interim I've changed in (Forefront's General Settings) the Realtime Scan Timeout Action parameter and have set it to Skip: detect only to at least allow for mail to flow.
I'm a bit uncomfortable with leaving this setting on.

Has anyone experienced this before? I'm not too sure on how to resolve this issue, any advice would be greatly appreciated.
0
Comment
Question by:racinesk
  • 2
  • 2
4 Comments
 
LVL 5

Expert Comment

by:Mechanic_Kharkov
ID: 24075090
It seems that You change wrong parameter. Try to change the maximum time limit to scan a message (default is 5 minutes).
And "Max Container Scan Time" is for compressed content only.
0
 
LVL 5

Expert Comment

by:Mechanic_Kharkov
ID: 24075592
0
 

Accepted Solution

by:
racinesk earned 0 total points
ID: 24083933
Just letting you know that this article helped us out http://support.microsoft.com/kb/939411
It turns out that Norman scan engine updates have caused these issues

This is what we did to fix it:

1. Open the Forefront engines folder C:\Program Files (x86)\Microsoft Forefront Security\Exchange Server\Data     \Engines\x86
2. Rename the Norman folder to Norman.old (so that Forefront will not load the corrupted Norman engine)
3. Open Registry Editor
4. Locate the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\Exchange Server
5. Create a new DWORD value EngineDownloadTimeout under this key
6. Change its value data to 1200 (decimal)
7. Restart Forefront services
8. Update Norman engine

This resolved our issue, but I found that the server's memory usage was abnormally high so I disabled the Norman engine and used another one instead.

0
 

Author Comment

by:racinesk
ID: 24094386
Just letting you know that this article helped us out http://support.microsoft.com/kb/939411
It turns out that Norman scan engine updates have caused these issues

This is what we did to fix it:

1. Open the Forefront engines folder C:\Program Files (x86)\Microsoft Forefront Security\Exchange Server\Data     \Engines\x86
2. Rename the Norman folder to Norman.old (so that Forefront will not load the corrupted Norman engine)
3. Open Registry Editor
4. Locate the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Forefront Server Security\Exchange Server
5. Create a new DWORD value EngineDownloadTimeout under this key
6. Change its value data to 1200 (decimal)
7. Restart Forefront services
8. Update Norman engine

This resolved our issue, but I found that the server's memory usage was abnormally high so I disabled the Norman engine and used another one instead.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question