The Microsoft Exchange Client Access server “%1” attempted to proxy or redirect Outlook Web Access traffic for mailbox “%2”. This failed because one of the service discovery entries returned for the Client Access server to use for this mailbox is malformed. The service discovery URLs should be in the format “http[s]://hostname[:port]/owa”. The malformed entry is stored as “%3”.

Details
Product: Exchange
Event ID: 38
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ProxyErrorWrongUriFormat
Message: The Microsoft Exchange Client Access server “%1” attempted to proxy or redirect Outlook Web Access traffic for mailbox “%2”. This failed because one of the service discovery entries returned for the Client Access server to use for this mailbox is malformed. The service discovery URLs should be in the format “http[s]://hostname[:port]/owa”. The malformed entry is stored as “%3”.
   
Explanation

This Error event indicates that Microsoft Office Outlook Web Access did not proxy or redirect requests from a computer that is running the Client Access server role to a Client Access server that is located in a different Active Directory site. A symptom of this failure is that the user referenced in the event description could not log on to their mailbox using Outlook Web Access through the Client Access server in a different site. This event may occur when the service discovery process returns a malformed URL address of the remote Client Access server.

   
User Action

To resolve this error, make sure that the msExchInternalHostName (Internal URL) and msExchExternalHostName (External URL) attributes of Outlook Web Access virtual directory of the remote Client Access server are formatted correctly.

You correct these values by using a tool such as Active Directory Service Interfaces (ADSI) Edit, the LDP (ldp.exe) tool, or any other Lightweight Directory Access Protocol (LDAP) version 3 client.

Your URLs should be in the following formats:

  • If Secure Sockets Layer (SSL) is used to proxy the request, use the format: msExchInternalHostName: https://InternalFulllyQualifiedDomainName/owa

  • If HTTP is used to proxy the request, use the format: msExchInternalHostName: http://InternalFulllyQualifiedDomainName/owa

  • If SSL is used to redirect the request, use the format: msExchExternalHostName: https://ExternalFulllyQualifiedDomainName/owa

  • If HTTP is used to redirect the request, use the format: msExchExternalHostName: http://ExternalFulllyQualifiedDomainName/owa

    Note   By default, msExchExternalHostName is blank. This external URL attribute is only needed if the Client Access server is Internet-Facing. If the Client Access server is Internet-Facing, this URL is only needed to enable the incoming Outlook Web Access request from another Client Access server to be redirected to the specified external URL address.

    Caution   If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP tool, or another LDAP version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003, or both. Modify Active Directory object attributes at your own risk.

To correct an internal or external URL:

  1. Open an Active Directory editor such as ADSI Edit.

  2. Expand Configuration <DomainName>, expand CN=Services, and then expand CN=Microsoft Exchange.

  3. Expand CN=<ExchangeOrganizationName>, expand CN=Administrative Groups, and then expand CN=<AdministrativeGroupName>.

  4. Expand CN=Servers, expand CN=<ServerName>, expand CN=Protocols, and then expand CN=HTTP.

  5. Under CN=HTTP, right-click CN=owa (Default Web Site), and then click Properties.

  6. In the Attribute Editor, click the msExchExternalHostName or msExchExternalHostName, and then click Edit.

  7. In the Edit Attribute box, set the value to the appropriate format.

  8. Click Apply, and then click OK.

  9. Close ADSI Edit.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply