The Availability service could not successfully send a proxy Web request to another instance of the Exchange Availability service that is running in a different Active Directory site or forest
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:
From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.
From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.
To learn more about this alert, if you are using System Center Operations Manager 2007, 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 events that have been logged that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
4002 |
Event Source |
MSExchange Availability |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Client Access/Information Worker |
MOM Rule Name |
The Availability service could not successfully send a proxy Web request to another instance of the Exchange Availability service that is running in a different Active Directory site or forest. |
Explanation
This Error event indicates that the Microsoft Exchange Availability service could not successfully send a proxy Web request to another instance of the Exchange Availability service that is running in a different Active Directory directory service site or a different Active Directory forest. The Exchange Availability service retrieves the Schedule+ Free Busy and Out-of-Office (OOF) data for a set of mailboxes that resides on a computer that is running Exchange 2007 Server. This event may occur when an Exchange 2007 Client Access server and user mailbox are in different Active Directory sites or forests. Because the Exchange Availability service cannot directly connect to a mailbox that resides in a remote Active Directory forest, it sends a proxy Web request to another instance of the Exchange Availability service that is running in the remote Active Directory forest. The Exchange Availability service that is running in the remote Active Directory forest retrieves the requested information locally and passes the information back to the Exchange Availability service that requested the information.
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.
There are insufficient permissions to request data from the remote Active Directory forest.
User Action
To resolve this error, 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 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 Availability 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.
Start Registry Editor (regedit).
Locate the following registry key: HKEY_LOCAL_MACHINE\CurrentControlSet\Services\MSExchange Availability\Diagnostics
In the results pane, change the Value data of all keys (except Default) to 5.
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.
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 Availability 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.
Start Registry Editor (regedit).
Locate the following registry key: HKEY_LOCAL_MACHINE\CurrentControlSet\Services\MSExchange Availability\Diagnostics
In the results pane, change the Value data of all keys (except Default) to 5.
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.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
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.