Topic Last Modified: 2010-06-21

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	4005
Event Source	MSExchange Availability
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Client Access/Availability Service
Rule Name	Missing Availability Service Configuration Information for the Current Forest

Explanation

This Error event indicates that the MSExchange Availability service could not obtain configuration information about the current Active Directory directory service forest. The Exchange Autodiscover service that runs on a front-end server that is running Exchange Server 2007 or Exchange Server 2010 (also known as Exchange Client Access Server) is a Web service that locates a mailbox. The Exchange Availability service is also a Web service that retrieves the Schedule+ Free Busy and Out-of-Office (OOF) data for that specific mailbox.

User Action

To resolve this problem, do one or more of the following:

Make sure that the Active Directory site or forest that contains the user mailbox has at least one local Exchange 2007 or Exchange 2010 server that runs the Exchange Availability service.
Use the Ping or PathPing command-line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.
Increase the diagnostic logging level of the MSExchange Autodiscover service. To do this, follow the steps shown here:

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.
1. Start Registry Editor (regedit.exe).
2. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Autodiscover\Diagnostics
3. In the results pane, change the Value data of all keys (except Default) to 5.
4. Exit Registry Editor.
Review other related Warning events and Error events in the Application log and in the System log. These related events may help you find the root cause of this event.

If you cannot resolve this problem by using the options recommended here, contact Microsoft Product Support Services. For more information, visit the Microsoft He l p and Support Web site.

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.