Topic Last Modified: 2010-02-10

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	1009
Event Source	MSExchange Anti-spam Update
Alert Type	Error
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Agents/Common
Rule Name	The download of the Microsoft Exchange Anti-Spam Update failed with an error.

Explanation

This Error event indicates that an anti-spam update could not be downloaded because of the error specified in the event description. This event occurs when anti-spam updates are not loaded.

This may be caused if either of the following conditions is true:

There are Internet connectivity failures. Misconfigured domain name service (DNS) settings or firewall settings may prevent the downloading of anti-spam updates.
There is an HTTP proxy failure or misconfiguration. An incorrect proxy server address or a proxy server rule may prevent the downloading of anti-spam updates.

User Action

To resolve this error, follow these steps:

Verify Internet connectivity. Check to see if you can successfully access the Internet from the Windows server.
Verify the correct HTTP proxy settings. Verify that your proxy server is not blocking access to the Windows Update site.

Review the WindowsUpdate.log file for information that could indicate the cause of the problem. By default, WindowsUpdate.log is located in the C:\Windows directory on the Windows Server. If needed, you can configure the WindowsUpdate.log for extended logging by enabling verbose logging. To turn on verbose logging, add the following registry key with two values:

	Copy Code
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace Value name: Flags Value type: REG_DWORD Value data: 00000007 Value name: Level Value type: REG_DWORD Value data: 00000004

Copy Code

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace
Value name: Flags
Value type: REG_DWORD
Value data: 00000007

Value name: Level
Value type: REG_DWORD
Value data: 00000004

Note This registry key turns on an extended tracing to any attached debuggers.

Caution Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.

For more information about anti-spam updates, see the following topics:

Understanding Anti-Spam Updates
Configure Anti-Spam Automatic Updates

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.