Microsoft Exchange Client Access server “%1” attempted to proxy Outlook Web Access traffic to Client Access server “%2”. This failed because “%2” did not respond. Outlook Web Access will attempt to proxy this traffic to Client Access server “%3” in the same Active Directory site.Additional information: %4.

Details
Product: Exchange
Event ID: 39
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ProxyErrorCASFailoverTryNextOne
Message: Microsoft Exchange Client Access server “%1” attempted to proxy Outlook Web Access traffic to Client Access server “%2”. This failed because “%2” did not respond. Outlook Web Access will attempt to proxy this traffic to Client Access server “%3” in the same Active Directory site.Additional information: %4.
   
Explanation

This Error event indicates that Microsoft Office Outlook Web Access could not proxy a request from a computer that is running the Client Access server role to a Client Access server that is located in a different Active Directory directory service site. To try to resolve this issue, Microsoft Exchange has proxied the request to an alternative Client Access server in the same Active Directory site as the Client Access server that failed. This error may be caused by the network connectivity issues between this Client Access server and the remote Client Access server.

For more information about Outlook Web Access proxying and redirection, see Understanding Proxying and Redirection.

   
User Action

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

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

  • Review the Application and System event logs for network-card-related events or connectivity-related events.

  • Check to see whether other computers that use the same default gateway and are plugged into the same hub or switch have also experienced connectivity problems. If the other computers connected to the same default gateway have not experienced network connectivity problems, the problem may be caused by a network adapter issue on a single computer. If this is the case, try to resolve this issue by following one or more of these steps:

    • Replace the network adapter with a network adapter that has been tested and proven reliable.

    • Update the driver for the network adapter driver to the latest version.

    • Replace the network cable between the system that failed and the hub or switch.

  • Check the settings on the network adapter and uplink hardware. The uplink hardware is the hub or switch that is used by the computer that has the Unified Messaging server role installed. Make sure that all network hardware is configured correctly by following these steps:

    • Make sure that the speed and duplex-level settings are the same on all network hardware.

    • If the media type is set to autosense, autosensing, autodetect, or Auto Select, make sure that all components autosense correctly.

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