Time:%1, Id:%2, Error Response with the ErrCode:”%3″, Message:”%4″, DebugData:”%5″ was generated for EMailAddress:”%6″, LegacyDN:”%7″ by “%8”.

Details
Product: Exchange
Event ID: 1201
Source: MSExchange Autodiscover
Version: 8.0
Symbolic Name: WarnProvErrorResponse
Message: Time:%1, Id:%2, Error Response with the ErrCode:”%3″, Message:”%4″, DebugData:”%5″ was generated for EMailAddress:”%6″, LegacyDN:”%7″ by “%8”.
   
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 the Active Directory® directory service.

  • 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.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply