Hi everybody,

I have one AD site. Its client computers are 4 Exchange Servers located in different locations, e.g., USA, Germany, Australia and India. One mailbox is impersonator which is located in USA. I have to query the information of all mailboxes in every Exchange Server.

1) What should be the EWS URL when I configure my application? Should it be of the CAS where impersonator mailbox is located or should it be of the CAS where the mailbox is located whose information is to be queried?

2) I am trying to fetch the information of a journal mailbox which is located in Germany by using impersonator. This impersonator mailbox is located in USA. In the configuration of my application I am giving the EWS URL of the Exchange Server where impersonator is located, i.e., CAS located in USA. Is this right approach. Or I should give the EWS URL of the CAS located in Germany (as the mailbox whose information to be queried is located there)?

3) In the scenario in 2nd question, I am getting ErrorNoRespondingCASInDestinationSite always when I fetch all the data in the journal mailbox. It has about > 3 lakh items. What should be the solution so that I should not get this error?

Kindly help.

Thanks & regards,

Amit Jha

• Edited by jha.amit6666 Thursday, May 21, 2015 2:39 PM

Hi Amit,

Thank you for your question.

Issue 1

ADid you mean which EWS use for impersonator? If that, it will use EWS on Exchange server in USA, which is https://exchange-cas-name-usa.contoso.com/ews

Issue 2

A: You should give EWS which is in USA.

Issue 3

A: we could refer to the following steps to configure journal mailbox:

https://technet.microsoft.com/en-us/library/aa998649%28v=exchg.150%29.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hi jim-xu,

I was following the same solutions when I got ErrorNoRespondingCASInDestinationSite as error response, i.e., I was giving EWS URL of CAS located in USA. Here is the description of the error: ResponseCode. And EWS throttling occurs after a migration of Office 365 Dedicated/ITAR to Exchange Server 2013 also gives more information. "More information" section in the same link also gives additional information.

There is a EWS Editor tool where you can test whether your impersonator policy is working or not.

https://ewseditor.codeplex.com/

I've used it and it works fine.

Adnan

Hi jim-xu,

I was following the same solutions when I got ErrorNoRespondingCASInDestinationSite as error response, i.e., I was giving EWS URL of CAS located in USA. Here is the description of the error: ResponseCode. And EWS throttling occurs after a migration of Office 365 Dedicated/ITAR to Exchange Server 2013 also gives more information. "More information" section in the same link also gives additional information. And I know how journal mailbox is configured. I can't do any changes to it now. It has lot of important data.

• Edited by jha.amit6666 49 minutes ago

Impersonation policy is working fine.

Pointing the application to the EWS URL in the USA should work fine. The EWS should proxy cross-site to the CAS server in Germany. Have you verified that the CAS server in the US is able to connect to the internal URL set on the EWS Virtual Directory of the server in Germany? Based on the error you are receiving, it would seem that cross-site proxy connection is not functioning. You can also inspect the IIS logs on both sides to help narrow down the issue

then it does not matter where the other mailbox is.

I wouldn't have posted this question if impersonation wasn't working. Impersonation policy is working fine.

• Edited by jha.amit6666 48 minutes ago

Hi Sean,

The CAS in USA is able to connect to the internal URL set on the EWS Virtual Directory of the server in Germany. For some items, my application is working fine. After that it is giving problems.

I checked the EWS logs in %ExchangeInstallPath%/Logging/Ews. Not much help there.

If it does not matter, then why did Microsoft have written EWS throttling occurs after a migration of Office 365 Dedicated/ITAR to Exchange Server 2013. If you will read this thread from the beginning, you would see that I have posted it before.