We currently have Exchange 2010 SP3 CU4 co-existence with Exchange 2013 CU8
We did the cut-over of autodiscover.domain.com and webmail.domain.com from Exchange 2010 to Exchange 2013
Autodiscover, OWA, ECP all work with user on Exchange 2010 and also on Exchange 2013

Now we experience some behavior i cannot explain and don't know how to troubleshoot.
When i have a mailbox on Exchange 2010 and go to https://webmail.rdgg.nl/ews/Exchange.asmx i automatically get on the page https://webmail.rdgg.int:/EWS/Services.wsdl showing a XML

When i have a mailbox on Exchange 2013 and go to https://webmail.rdgg.nl/ews/Exchange.asmx i get a page with "you have created a service" with a link to https://internalfqdn.domain.com:444/EWS/Services.wsdl

Clicking on this link opens the https://internalfqdn.domain.com:444/EWS/Services.wsdl url with a XML but this site has a certificate error , this because this is the BackEnd website of Exchange with a self signed Exchange certificate

1)Is there something different/changed in EWS on Exchange 2013 ?
2)Is this expected behavior that in 2013 we not directly get the XML but instead 'you created a service' ?
3)which log file should i check to see that goes wrong ?
4)what is a good test to verify ews works as should ?

Running "Service Account Access (Developers)" on testexchangeconnectivity.com shows GREEN and all test succesfull

We use EWS to receive mail in a mailbox, get mail from this mailbox and forward this.
We use EWS to synchronize calendar of a roommailbox to a 3rd party application.

Currently both functions dont work anymore and looking for a solution, troubleshoot tips, determine if this is really an Exchange 2013 problem.

Regards,

• Edited by dirkverhagen123 Thursday, June 18, 2015 5:40 PM

Although it can be done, the EWS URLs aren't really made to be accessed with a browser like that. So I wouldn't be too surprised that you see a difference. There is nothing in what you describe to suggest that anything is wrong, though.

The easiest way to test it is to get hold of the EWS Editor utility, and run that.  You should be able to connect to your mailbox with very little effort.

Hi Lee,

Thanks for your repsonse

I found the EWS Editor @ https://ewseditor.codeplex.com/
I did some tests and followed the guide @ http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unity-version-80/116223-configure-ews-00.html

I did an impersonation with credentials to another mailbox and got an error about impersonation.
I then added the account to the ApplicationImpersonation Role in Exchange 2013 and then i can succesfully open the mailbox and see the folders.

So I think it is safe to presume EWS is working OK and that the cullprit must be in the code of the application that does the EWS call ?

Yes, it sounds like your EWS is working. I didn't know you were having problems with a particular application - I can't see it mentioned in your post. But you might have a look in your IIS log file, which you can open in Notepad. Try to use the application, note the time, and then look for requests for /EWS at the same time. But note that IIS doesn't write the entries immediately - it flushes them to the file every few minutes.

If you can find the relevant lines, post them here.

Does the application produce an informative error message?  Or does it just not do anything at all?

Hi,

Whats your configuration of the Exchange Web Service in your coexistence environment? Please run the following command for Exchange 2010 and Exchange 2013, collect the results here:

Get-WebServicesVirtualDirectory | FL Identity,*AUTH*,*url*

Generally, in the coexistence environment, the Exchange 2013 can proxy the external services requests to the Exchange 2010. For detailed information about the Client Connectivity in an Exchange 2013 Coexistence Environment, please refer to:

http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx

Regards,