?
Solved

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

Posted on 2009-04-05
4
Medium Priority
?
13,107 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
 

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

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

If you thought ransomware was bad, think again! Doxware has the potential to be even more damaging.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
To show how to generate a certificate request 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 Servers >> Certificates…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

777 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