Outlook Web Access proxy or redirection failed because one of the service discovery entries is not valid
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:
From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.
From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.
To learn more about this alert, if you are using System Center Operations Manager 2007, 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 events that have been logged that meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
38 |
Event Source |
MSExchange OWA |
Alert Type |
Critical Error |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Client Access/Outlook Web Access |
MOM Rule Name |
Outlook Web Access proxy or redirection failed because one of the service discovery entries is not valid. For more information, see MSExchangeOWA event 38. |
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:
Open an Active Directory editor such as ADSI Edit.
Expand Configuration <DomainName>, expand CN=Services, and then expand CN=Microsoft Exchange.
Expand CN=<ExchangeOrganizationName>, expand CN=Administrative Groups, and then expand CN=<AdministrativeGroupName>.
Expand CN=Servers, expand CN=<ServerName>, expand CN=Protocols, and then expand CN=HTTP.
Under CN=HTTP, right-click CN=owa (Default Web Site), and then click Properties.
In the Attribute Editor, click the msExchExternalHostName or msExchExternalHostName, and then click Edit.
In the Edit Attribute box, set the value to the appropriate format.
Click Apply, and then click OK.
Close ADSI Edit.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
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.