Enterprise Vault (EV) Outlook Web Access (OWA) Resource Tool: “Check Virtual Directories Module – Exchange 2007/2010 Exchange Web Services (EWS) Test”

Article:TECH154553  |  Created: 2011-03-01  |  Updated: 2014-03-18  |  Article URL http://www.symantec.com/docs/TECH154553
Article Type
Technical Solution


Issue



The Enterprise Vault OWA Resource Tool (EVORT) analyzes Exchange Server environments to confirm that the OWA configuration is correct for integrating with Enterprise Vault.

The Check Virtual Directories module tests that Exchange virtual directories have the optimum settings.
 
The Exchange Web Services test verifies the settings of the Exchange Web Services virtual directories to ensure that the Enterprise Vault OWA extensions can connect and authenticate. 

Solution



There are many reasons the Check Virtual Directories Exchange Web Services test can fail, match the report error and the error below for the solution:

Error: The given host name cannot be resolved to an Exchange Server.
Solution:
  1. On the reported CAS Server, open the Web.Config file (Program Files->Microsoft->Exchange Server->ClientAccess->OWA) .
  2. Verify that the EWS setting “EnterpriseVault_ExchangeWebServicesURL” contains a valid reference to an Exchange Server. This can be specified as an alias, name or IP Address and include port numbers.
Example: <add key=EnterpriseVault_ExchangeWebServicesURL  Value=”https://localhost/ews/exchange.asmx”/> 
 
Error: The CAS Server cannot communicate with the EWS Server due to Web site binding configuration.
Solution: Check the Web site server bindings on the Exchange server referenced in the EnterpriseVault_ExchangeWebServicesURL 
 
Ensure that Web.Config settings are set correctly
  1. On the reported CAS Server, open the Web.Config file (Program Files->Microsoft->Exchange Server->ClientAccess->OWA) .
  2. Verify that the setting “EnterpriseVault_ExchangeWebServicesURL” contains a valid protocol. The setting should be set to HTTP if the environment needs to be configured using server bindings. If a secure binding is required for communication to the proxy server then the setting must be set to HTTPS.
Example :

https://localhost/ews/exchange.asmx

 
Error: The CAS Server cannot communicate with the EWS Server as the associated Web site does not have an EWS virtual directory.
Solution:  Check the associated Web site has an EWS virtual Directory.
  1. Run Exchange Management Shell command prompt command: Get-WebServicesVirtualDirectory
  2. If an EWS virtual directory does not exist then add one to the web site:
    1. Open Exchange Management Shell command prompt, enter the command: New-WebServicesVirtualDirectory –website ‘<website name>’ 
 
Error: The CAS Server cannot communicate with the EWS Server as the associated Web site requires SSL.
Solution:  Update the EWS Web.Config settings to use the HTTPS protocol in the address.
  1. On the reported CAS Server, open the Web.Config file (Program Files->Microsoft->Exchange Server->ClientAccess->OWA) .
  2. Verify that the EWS setting “EnterpriseVault_ExchangeWebServicesURL” uses the HTTPS protocol.
Example: https://localhost/ews/exchange.asmx

 

 

  1. Open the Server Manager and navigate to the Web site EVORT has identified as not having certificates installed.
  2. In the right had pane select the bindings link.
  3. Select the HTTPS binding type and click the edit button, under the SSL certificate select a valid certificate.
Error: The EnterpriseVault_ExchangeWebServicesUrl setting is not valid.
Solution: Check EnterpriseVault_ExchangeWebServicesURL setting in the Web.Config file
  1. On the reported CAS Server, open the Web.Config file (Program Files->Microsoft->Exchange Server->ClientAccess->OWA) .
  2. Verify that the setting “EnterpriseVault_ExchangeWebServicesURL” contains a valid URL to Exchange We Services.
  3. Run Exchange Management Shell command prompt command: Get-WebServicesVirtualDirectory

Example:

<add key=”EnterpriseVault_ExchangeWebServicesURL” Value=”https://localhost/ews/exchange.asmx”/>

 
Error: The authentication schemes to the OWA and EWS virtual directories are not compatible.
Solution: When Authentication fails between the OWA virtual directory and the EWS virtual directory, we look to the authentication scheme between the different virtual directories.
  1. If authentication for the OWA virtual directory is Windows authentication then the EWS virtual directory must be Windows authentication.
    1. Select the OWA virtual directory in the Web Site which contains the failure
    2. Verify that the authentication for the OWA virtual directory is lower than the EWS virtual directory.
 
Error: The specified virtual directory name is not valid.
Solution: Check the virtual directory name in the EnterpriseVault_ExchangeWebServicesURL setting in the Web.Config file, typically the virtual directory will be named “EWS”.
  1. To look up a valid EWS virtual directory use the Exchange Management Shell command prompt: -get WebServicesVirtualDirectory 
  2. On the reported CAS Server, open the Web.Config file (Program Files->Microsoft->Exchange Server->ClientAccess->OWA) .
  3. Verify that the EWS setting “EnterpriseVault_ExchangeWebServicesURL” contains a valid URL to Exchange Web Services.
Example:

<add key=”EnterpriseVault_ExchangeWebServicesURL” Value=”https://localhost/ews/exchange.asmx”/>

 
Error: The specified EWS service name is not valid
Solution: Check the service name in the EnterpriseVault_WebServicesURL setting in the Web.Config file, typically the service name will be “Exchange.asmx”.
  1. On the reported CAS Server, open the Web.Config file (Program Files->Microsoft->Exchange Server->ClientAccess->OWA) .
  2. Verify that the EWS setting “EnterpriseVault_ExchangeWebServicesURL” contains a valid URL to exchange web Services.
  3. To look up a valid EWS virtual directory use the Exchange Management Shell command prompt: -get WebServicesVirtualDirectory
Example:

<add key=”EnterpriseVault_ExchangeWebServicesURL” Value=”https://localhost/ews/exchange.asmx”/>

 

Error: The CAS Server cannot communicate with the EWS Server as the associated Web site does not have a certificate installed.

Solution:  Verify Web sites bindings on the Exchange server referenced in the EnterpriseVault_ExchangeWebServicesURL setting which require SSL has certificates installed and SSL settings are correctly applied.





Article URL http://www.symantec.com/docs/TECH154553


Terms of use for this information are found in Legal Notices