MSExchange OWA 57

  • Article

 

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

Details

Product Name

Exchange

Product Version

14.0

Event ID

57

Category

Proxy

Symbolic Name

ProxyErrorServiceDiscovery

Message Text

Outlook Web App isn't available for this mailbox. The Client Access server %1, running Exchange version %2, tried to find a Client Access server to proxy Outlook Web App traffic for mailbox %3. It couldn't find the Client Access server in the target Active Directory site.%n%nAdditional information: %4. If the problem continues, contact your helpdesk.

Explanation

This Warning event indicates that the computer that is running the Client Access (CAS) server role could not determine the Client Access server that should handle a Microsoft Office Outlook Web App request. Specifically, it could not determine whether the request should be processed by the local Client Access server, or if it should be proxied or redirected to a Client Access server in a different Active Directory site. Therefore, the mailbox specified in the event description could not be accessed through Outlook Web App. This event may be caused by one or more of the following:

  • The Client Access server cannot verify the location of servers that are running Microsoft Exchange in Active Directory sites.

  • The Client Access server cannot verify the links between the Active Directory sites.

  • The Client Access server cannot access required Exchange virtual directory configuration data from Active Directory.

  • The Client Access server that accepts Outlook Web App proxy or redirection requests is not in the same Active Directory site as the computer that is running the Mailbox server role.

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

User Action

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

  • If this occurs frequently, check network connectivity between the Client Access Server and domain controllers. 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.

  • Make sure that the InternalUrl of the Outlook Web App virtual directory exists and that it matches the fully qualified domain name (FQDN) of the local CAS server.

  • Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and other methods. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

For More Information

If you are not already doing so, consider running the Exchange tools, which have been 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 and improve mail flow. 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.