The Outlook Web App proxy failed because no Outlook Web App virtual directory configured for Kerberos authentication could be found in the site.

 

Applies to: Operations Manager Management Pack for Exchange 2010

Topic Last Modified: 2011-08-02

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, 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 logged events that meet the criteria of this Operations Manager alert.

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

41

Event Source

MSExchange OWA

Alert Type

Error

Rule Path

Microsoft Exchange Server/Exchange 2010/Client Access/Outlook Web Access

Rule Name

The Outlook Web App proxy failed because no Outlook Web App virtual directory configured for Kerberos authentication could be found in the site.

Explanation

This Error event indicates that the computer that is running the Client Access server role could not determine whether the Microsoft Office Outlook Web App request should be processed by the local Client Access server, or if it should be redirected to another Client Access server that is located in a different Active Directory site. Therefore, the user who owns the mailbox specified in the event description cannot access their mailbox through Outlook Web App. This event may occur if the settings for the Outlook Web App virtual directory are configured incorrectly.

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:

  • Make sure that the msExchInternalHostName (Internal URL) attribute of the Outlook Web App virtual directory exists and it matches the fully qualified domain name (FQDN) of the Client Access server.

  • Make sure that the Client Access server that receives the proxy request has Integrated Windows authentication enabled on the Outlook Web App virtual directory.

  • Contact a Microsoft Support professional to resolve this issue. To contact a Microsoft Support professional, visit the Exchange Server Solutions Center. In the navigation pane, click Assisted Support Options and use one of the 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 information about authentication methods that you can use with Outlook Web App, see Managing Outlook Web App Security.

For information about how to configure Integrated Windows authentication for Outlook Web App, see Configure Integrated Windows Authentication.

For information about how to modify the properties of Outlook Web App virtual directories using the Set-OwaVirtualDirectory cmdlet, see Set-OwaVirtualDirectory.

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.