MSExchange OWA 41
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 |
41 |
Category |
Proxy |
Symbolic Name |
ProxyErrorCouldNotFindCAS |
Message Text |
The Client Access server "%1" attempted to proxy Outlook Web App traffic for mailbox "%2". This failed because no Client Access server with an Outlook Web App virtual directory configured for Kerberos authentication could be found in the Active Directory site of the mailbox. The simplest way to configure an Outlook Web App virtual directory for Kerberos authentication is to set it to use Integrated Windows authentication by using the Set-OwaVirtualDirectory cmdlet in the Exchange Management Shell, or by using the Exchange Management Console. If you already have a Client Access server deployed in the target Active Directory site with an Outlook Web App virtual directory configured for Kerberos authentication, the proxying Client Access server may not be finding that target Client Access server because it does not have an internalUrl parameter configured. You can configure the internalUrl parameter for the Outlook Web App virtual directory on the Client Access server in the target Active Directory site by using the Set-OwaVirtualDirectory cmdlet. |
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.