Process %1: %2 failed. Exception returned is %3. This event may occur when Availability Service cannot discover an Availability Service in the remote forest.

Details
Product: Exchange
Event ID: 4001
Source: MSExchange Availability
Version: 8.0
Symbolic Name: AutoDiscoverFailed
Message: Process %1: %2 failed. Exception returned is %3. This event may occur when Availability Service cannot discover an Availability Service in the remote forest.
   
Explanation

This Error event indicates that the Microsoft® Exchange Autodiscover service could not discover the Exchange Availability service that is running in a remote Active Directory® directory service forest. The Exchange Autodiscover service that runs on a Front End server that is running Exchange Server 2007 (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. This event may occur when an Exchange 2007 Client Access server and user mailbox are in different Active Directory forests. Because the Exchange Autodiscover service cannot directly connect to a mailbox that resides in a remote Active Directory forest, it requests that the Exchange Availability service that is running in the remote Active Directory forest retrieve the requested information locally.

Note   This event does not occur if the user mailbox resides servers that are running Exchange 2000 or Exchange 2003.

This event may occur if one or more of the following conditions are true:

  • The Active Directory site or forest that contains the user mailbox does not have a local Exchange 2007 server that runs the Exchange Availability service.

  • The Exchange Availability service finds issues when it tries to connect to the remote Active Directory forest.

   
User Action

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

  • Make sure that the Active Directory site or forest that contains the user mailbox has at least one local Exchange 2007 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:

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

    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 and System log. These related events may help you find the root cause of this event.

If you cannot resolve this error using the options suggested here, contact Microsoft Product Support Services. For more information, visit the Microsoft Help and Support Web site.

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