We help IT Professionals succeed at work.

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

racinesk
racinesk asked
on
13,576 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.
Comment
Watch Question

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.
Also read here.
http://social.technet.microsoft.com/Forums/en-US/forefrontexchange/thread/73113a9a-d32c-4615-8a73-6119e5185210

Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
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.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.