Cisco Unity

EWS Interface Test on Microsoft Exchange with the EWS Editor tool

Document ID: 116223

Updated: Jun 21, 2013

Contributed by Cisco TAC Engineers.



This document describes the tasks to perform when the Unity Connection messages are not being delivered to Exchange. If a test is run on the User under Unfied Messaging Accounts, the user might notice that the Exchange Web Service (EWS) connection failed. EWS Editor (a third party tool) might be used to test EWS access to the mailbox. This tool shows whether the issue is strictly with Unity Connection or if the if issue is most likely with the service account or other issue on Exchange.


Collect this detailed information:

  • Exchange Server hostname to which the Unity Connection connects
  • The service account name and password set up for the Unified Messaging integration
  • The domain in which that service account resides
  • The SMTP address of a test account that uses the Unified Messaging integration

EWS Interface Test on Microsoft Exchange with the EWS Editor Tool

  1. Launch ewseditor.exe.

  2. Choose File > New Exchange Service.

  3. Choose an Exchange server.
    1. In order to choose a specific Exchange URL, uncheck the Use autodiscover to get the Exchange Web Services URL check box.
    2. In order to see an example of autodiscover address, go to https://mailservername/autodiscover/autodiscover.xml
    3. In order to see an example of specific address, go to http://mailservername/EWS/Exchange.asmx
  4. From the Requested Exchange Version drop-down list, choose Exchange 2010_SP1.
  5. Check the Use the following credentials instead of the default Windows credentials check box, and enter the service account information into the User Name, Password, and Domain fields.
  6. Check the Use impersonation to log on to another mailbox check box, and in the Id field, enter the SMTP address for a mailbox.

  7. Click OK to connect to the EWS service. If you used an https URL you might receive a security error.This occurs if the hostname in the service URL does not match with the client certificate, or when the root certificate from the Certificate Authority (CA) server that signed the client certificate is not present on the client machine.

    If successful, the main interface appears. Click Yes.

  8. In order to open the mailbox, open the tree in the left pane, right-click Allitems, and click Open Items.

    The mailbox items are now displayed.

  9. Open the Exchange logs from C:\inetpub\logs\LogFiles\W3SVC1. It might take a few minutes for the logs to populate. It should display the access from the EWS Editor.

Related Information

Updated: Jun 21, 2013
Document ID: 116223