Topic Last Modified: 2010-01-28

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	1201
Event Source	MSExchange Autodiscover
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Client Access/Auto Discovery
Rule Name	An unexpected error occurred while retrieving data from the Autodiscover service.

Explanation

This Warning event indicates that the client request received could not be successfully processed by the Microsoft Exchange Autodiscover service. The event can occur when any one of the following conditions is true:

An invalid XML request is received from the client
A critical failure occurs with the Outlook provider For example, Autodiscover cannot connect to Active Directory.
The Outlook provider encounters an error for any of the following reasons:
- The e-mail address was not found.
- The e-mail address had an incorrect format.
- The e-mail address is not a recognized user or a contact in a group or public folder.
- The contact could not be forwarded to a Simple Mail Transfer Protocol (SMTP) address.

User Action

To resolve this warning, take one or more of the following steps:

See the Application event log for a detailed event description.
If an invalid XML request is received from the client, validate the XML request by using the OutlookRequestSchema2006.xsd template. This template can be used to validate gross errors in the client XML request.
Make sure that there is connectivity from the Exchange server to the domain controller if a critical failure occurs with the Outlook provider, for example, if Autodiscover cannot connect to Active Directory. For more information about how to test connectivity by using NetDiag.exe, see Netdiag Overview.
If the Outlook provider encounters an error that occurs with the e-mail address, check the format and spelling of the e-mail address.
If the Outlook provider encounters an error because the e-mail address is not recognized as a user or a contact, the client can resubmit the request by specifying a user or a contact that exists in the directory.
If the Outlook provider encounters an error because the contact could not be forwarded to an SMTP address, make sure that the contact target address is set to a valid SMTP address.

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.