Microsoft Exchange Client Access server "%1" attempted to proxy Outlook Web Access traffic to Client Access server "%2". This failed because one of these configuration problems was encountered: 1. "%2" has been set to use "http://" (not using SSL) instead of "https://" (using SSL). You can modify this by setting the InternalUrl parameter of the Outlook Web Access virtual directory this proxy traffic is going to. You can set that parameter using the Set-OwaVirtualDirectory cmdlet in the Exchange Management Shell. 2. The destination virtual directory returned an HTTP 403 error code. This usually means it is not configured to accept SSL access. You can change this configuration by using Internet Services Manager on the Client Access server "%2". If you do not want this proxy connection to use SSL, you need to set the registry key "AllowProxyingWithoutSSL" on this Client Access server and set the InternalUrl and SSL settings for the Outlook Web Access virtual directory this proxy traffic is going to accordingly.
Microsoft Exchange Client Access server "%1" attempted to proxy Outlook Web Access traffic to Client Access server "%2". ...
Microsoft Exchange Client Access server "%1" attempted to proxy Outlook Web Access traffic to Client Access server "%2". ...
Microsoft Exchange Client Access server "%1" attempted to proxy Outlook Web Access traffic to Client Access server "%2". ...
Microsoft Exchange Client Access server "%1" attempted to proxy Outlook Web Access traffic to Client Access server "%2". ...
Microsoft Exchange Client Access server "%1" attempted to proxy Outlook Web Access traffic to Client Access server "%2". ...
Microsoft Exchange Client Access server %1 attempted to proxy Outlook Web Access traffic to Client Access server %2. This ...
Microsoft Exchange couldn't apply the address list '%1' to the object '%2' because the filter rule (PurportedSearch) is invalid. ...
Microsoft Exchange couldn't complete the opt-in process for Microsoft Update %1. Please see http://update.microsoft.com and ...
Microsoft Exchange couldn't connect to %1 using credentials %2/%3. This may be because of an expired bootstrap account. Please ...