MSExchange OWA 41

 

上一次修改主题: 2011-03-19

本文对特定 Exchange 事件进行了说明并提供了可能的解决方案。如果您在此处未找到所需内容,请尝试在 Exchange 2010 帮助中进行搜索。

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 了解代理和重定向.

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.

  • 与 Microsoft 支持专业人员联系,解决此问题。若要与 Microsoft 支持专业人员联系,请访问 Exchange Server 解决方案中心。在导航窗格中,单击“辅助支持选项”,并使用下列辅助支持选项之一来与 Microsoft 支持专业人员联系。由于您的组织可能已有直接与 Microsoft 产品支持服务联系的特定流程,因此,请您务必先查看您组织的准则。

For information about authentication methods that you can use with Outlook Web App, see 管理 Outlook Web App 安全性.

For information about how to configure Integrated Windows authentication for Outlook Web App, see 配置集成 Windows 身份验证.

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

如果您尚未执行此操作,请考虑运行 Exchange 工具,已创建这些工具以帮助您分析 Exchange 环境并对其进行疑难解答。这些工具可帮助确保您的配置与 Microsoft 最佳实践保持一致。它们还可以帮助您识别和解决性能问题,并改进邮件流。若要运行这些工具,请转到 Exchange 管理控制台的“工具箱”节点。若要了解有关这些工具的详细信息,请参阅管理工具箱中的工具