Topic Last Modified: 2010-02-05

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	304
Event Source	MSExchange Antispam
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Agents/Common
Rule Name	The Content Filter agent couldn't be initialized. There may be corrupted files.

Explanation

This Error event indicates that the Content Filter agent could not start because there may be corrupted files found on the system. The exception specified in the event description may provide more information about this problem.

User Action

To resolve this error, follow one or more of these steps:

Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.
Reset the anti-spam update process as follows:

Important If you run the following script, you will reset the anti-spam baseline to that set during initial installation.
- Open the Exchange Management Shell on the server that is running Exchange and run the script named Reset-AntispamUpdates.ps1. The script is located in the %ExchangeInstallPath%\Scripts directory on the Windows server where Microsoft Exchange Server 2010 was installed. For information about how to run scripts, see Scripting with the Exchange Management Shell.
Restart the Microsoft Exchange Transport service. To restart the service:
1. On the Start menu, click Run, type services.msc, and then click OK.
2. In the Results pane, find the Microsoft Exchange Transport service.
3. Right-click the service, and then click Restart.
Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and others. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to review your organization's guidelines first.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.