Aug 22, 2012 at 2:11 PM
Edited Aug 22, 2012 at 2:14 PM
Please have a look at
this discussion here at Microsoft Managed Discussion Groups.
We cannot connect to Exchange Server 2010 using managed EWS under .NET 4.0. We always receive a "401" error.
EWSEditor, however, either receives a "403" error (at a call to
TestExchangeService()), or, using one of the three accounts I'm testing with, successfully connects to the account's mailbox.
While EWSEditor communicates with Exchange Server for the one account that's working, it takes approx. 30 Seconds for each call to Exchange Server to return. So it's performing extraordinarily slow.
What does EWSEditor do to be able to connect to Exchange Server 2010 if not by using plain EWS? What's the fall-back mechanism it's using?
Your help is appreciated.