Hotfix Rollup 4 for Microsoft Forefront Protection for Exchange

Issues that are fixed in Hotfix Rollup 4 for Forefront Protection 2010 for Exchange

1. Email is sent to the Forefront Protection for Exchange UNDELIVERABLE folder instead of being delivered
2. UNC and proxy credentials are stored in clear text in the Forefront Protection for Exchange file system
3. The Forefront Protection for Exchange FSEMachinePrep.exe fails with a fatal error
4. The external sender does not receive the expected Forefront Protection for Exchange generated notification
5. Forefront Protection for Exchange generates a notification with a blank subject line
6. Forefront Protection for Exchange virus engine updates fail between the passive node and active node in CCR clusters
7. Forefront Protection for Exchange only accepts 7-digit License Agreement numbers
8. Email queues at startup on an Exchange server running Forefront Protection for Exchange

Details of the issues that are fixed in the hotfix rollup

1. Email is sent to the Forefront Protection for Exchange UNDELIVERABLE folder instead of being delivered
   
   

   Problem

   Mail is delivered to the Forefront Protection for Exchange UNDELIVERABLE folder instead of to the recipient. The following errors are seen in the application event log:
   
   
   "ERROR: An exception has occurred within ForefrontAgent's Scan method. Exception message = "Insufficient memory to continue the execution of the program."
   
   "INFORMATION: ArchiveMailMessage called to archive %Program Files (x86)%\Microsoft Forefront Protection for Exchange Server\Data\Archive\Undeliverable\[file name].eml"
   
   

   More Information

   This behavior has been known to occur on files that are 90 MB in size or greater.
   
2. UNC and proxy credentials are stored in clear text in the Forefront Protection for Exchange file system
   
   

   Problem

   If you have entered UNC and/or proxy credentials in Forefront Protection for Exchange, they are stored in clear text in a file called DebugSettings.xml. This file is found in the %Program Files (x86)% \Microsoft Forefront Protection for Exchange Server\Data directory.
   
   

   More Information

   From Hotfix Rollup 4 for Forefront Protection for Exchange, UNC and proxy credentials are no longer stored in DebugSettings.xml by default.
   
3. The Forefront Protection for Exchange FSEMachinePrep.exe fails with a fatal error
   
   

   Problem

   When you attempt to install Forefront Protection for Exchange, FSEMachinePrep.exe fails with the following error:
   
   
   “A fatal error occurred running "fsemachineprep". Please either check that you have Exchange Administrator rights (or equivalent) or ask your Enterprise Administrator to run the machine preparation tool. The exception message is: A constraint violation occurred. (Exception from HRESULT: 0x8007202F)"fsemachineprep" did not complete successfully. Please see the event log for details.”
4. The External Sender does not receive the expected Forefront Protection for Exchange generated notification
   
   

   Summary

   Prior to Forefront Protection for Exchange Hotfix Rollup 4, on new installations of Forefront Protection for Exchange, the default notification for “External Sender” is incorrectly set to send notifications to the “External Recipients” when a detection occurs. If you do a fresh install of Forefront Protection for Exchange Hotfix Rollup 4 then the default notification for “External Sender” will be set correctly.  
   
   

   Cause

   The Forefront configuration.xml does not provide a variable for the External Sender configuration.
   
   

   More Information

   If you perform an upgrade to Forefront Protection for Exchange Hotfix Rollup 4, the incorrect setting will still be stored in Forefront’s configuration.xml file and this issue will not be resolved.. 
   
   
5. Forefront Protection for Exchange generates a notification with a blank subject line
   
   

   Problem

   When Forefront Protection for Exchange sends an email notification to either an administrator or an internal sender, the subject line may be blank.
   
   

   Symptoms

   Forefront generated notifications contain a blank subject line
   
6. Forefront Protection for Exchange virus engine updates fail between the passive node and active node in CCR clusters
   
   

   Problem

   Forefront Protection for Exchange virus engine updates fail between the passive node and active node in CCR clusters when the following conditions are met:
   
   1.) UNC is enabled in Forefront Protection, and credentials have been entered into Forefront Protection
   2.) Redistribution Server is checked in the Forefront console (default on all CCR installs)
   
   

   Symptoms

   The engine(s) do not update on the passive node. The following errors are recorded in the Application Log:
   
   
   Source: GetEngineFiles
   Date: [Date/Time]
   Event ID: 6014
   Task Category: (6)
   Level: Error
   Keywords: Classic
   User: N/A
   Computer:   [Computer Name]
   Additional Information
   [Engine Name]
   file:///\\[Path]
   string_resource_107
   0x80070003
   The system cannot find the path specified.
   
   

   Cause

   During the replication process the UNC credentials cannot be written to the passive node. When this node becomes active, it does not contain valid UNC credentials and subsequently engine updates fail.
   
7. Forefront Protection for Exchange only accepts 7-digit License Agreement numbers
   
   

   Problem

   Forefront Protection for Exchange only accepts 7-digit License Agreement numbers, yet some customers may have an 8-digit License Agreement number. If you have an 8-digit License Agreement number, you cannot enter the full number into the product.
   
   

   More Information

   Hotfix Rollup 4 for Forefront Protection for Exchange allows up to 10 characters to be entered as the License Agreement number.
   
8. Email queues at startup on an Exchange server running Forefront Protection for Exchange
   
   ProblemWhen the Exchange server that is running Forefront Protection for Exchange is starting, a timing issue may occur if a virus scan engine update initiates simultaneously. This timing issue may culminate in the Forefront FSE Agent failing to initialize which will lead to mail queues.
   
   Symptoms1.) Email queues on the Exchange server.
   
   2.) The following error will be present in the Forefront trace log:
   
   
   An exception has occurred within Forefront Agent’s InitializeScanner method. Exception message = \"Retrieving the COM class factory for component with [CLSID]’failed due to the following error: 80080005.
   
   

Hotfix rollup information

Download information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

How to install the hotfix rollup

To install the hotfix rollup, follow these steps:

1. Run the installer. To do this, double-click the hotfix rollup executable file.
   
   Note When the installer is running, the Forefront services are stopped.
2. After the installation is complete, and the Forefront services are restarted, make sure that Forefront is working correctly.
   
   Notes
   • The Forefront services are restarted automatically during the installation.

Prerequisites

This hotfix rollup requires that Forefront Protection 2010 for Exchange is installed.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The English (United States) version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.