locked
EWS with Impersonation - Active Directory operation did not succeed. Try again layer RRS feed

  • Question

  • Our client has recently upgrade to Exchange 2013 and our software uses EWS to create appointments using impersonation.

    There are 12 combination role servers, 10 servicing EWS calls. For now they've mapped a specific machine in our servers hosts file to bypass the load balancer so we are hitting a single CAS server. Our service accesses a subset of approx. 150 users spread across these servers.

    When making requests/calls to EWS with impersonation we keep getting "Active Directory operation did not succeed. Try again layer". The issue exists whether we go through the load balancer or not.

    It is sporadic in that it works some days and other days we get constant failures and haven't been able to narrow down the issue. Should we be concentrating on the AD servers or exchange servers to isolate the problem..

    The following throttling policies applied to our system account is as follows:

    EwsMaxConcurrency                         : Unlimited

    EwsMaxBurst                               : Unlimited

    EwsRechargeRate                           : Unlimited

    EwsCutoffBalance                          : Unlimited

    EwsMaxSubscriptions                       : Unlimited


     
    Wednesday, April 9, 2014 4:27 PM

All replies

  • Hello,

    Did you try to see what`s happening in the logs.

    On the CAS Server open the following log with some CSV Parser (for example Excel):

    "%exchangeinstalldir%\Logging\HttpProxy\Ews\<HttpProxy_..........log>" and identify your request that is failing, maybe by "RequestID".

    Write down the "RequestID"

    Write down the Mailbox Server where the request is proxyied, you can find it in the TargetServer field.

    Go to the Server where the request is redirected, and open the following log:

    "%exchangeinstalldir%\Logging\Ews\<Ews_...........LOG>"

    Use the Request ID to find the corresponding entry in the log. You should be able to get more detailed errorinfo from the "GenericError" field.



    Wednesday, April 9, 2014 5:10 PM
  • There seem to be a large number of "Unauthenticated EWS request"  messages appearing when it attempts to proxy.

    (Removed identifying server information)
    2014-04-09T20:05:48.593Z,1bb507b2-ed93-4f36-be8c-c6f0db159567,15,0,775,22,,Ews,<*****domain removed>,/EWS/Exchange.asmx,,Negotiate,True,*******\USERNAME,,Sid~S-1-5-21-414670182-1717447316-1905203885-274226,ExchangeServicesClient/15.00.0516.014,162.131.154.102,MACHINE0006,500,500,,POST,Proxy,*******.domain.removed.com,15.00.0775.000,IntraForest,WindowsIdentity,,,,1292,651,1,,5,29,,0,,0,,0,0,46.8028,0,1,1,0,18,0,0,0,50,0,18,30,31,36,55,,,BeginRequest=2014-04-09T20:05:48.546Z;BeginGetRequestStream=2014-04-09T20:05:48.577Z;OnRequestStreamReady=2014-04-09T20:05:48.577Z;BeginGetResponse=2014-04-09T20:05:48.577Z;OnResponseReady=2014-04-09T20:05:48.593Z;EndGetResponse=2014-04-09T20:05:48.593Z;S:ServiceCommonMetadata.Cookie=245bbf09517945dab05803967db31d00,WebExceptionStatus=ProtocolError;ResponseStatusCode=500;

    2014-04-09T20:05:48.733Z,ca1ccf5c-298e-489d-abcb-9b652abc0493,15,0,775,22,,Ews,domain.removed,/EWS/exchange.asmx/EWS/exchange.asmx,,NTLM,False,,,,Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.1008),162.131.154.102,MACHINE0006,401,,,,,,,,,,,,0,,,,,,,,,,,,,0,,,,,,,,,,,,0,,0,0,,,BeginRequest=2014-04-09T20:05:48.733Z;,

    2014-04-09T20:05:48.858Z,21368de3-d0e2-472c-bc56-eaaa446f30de,15,0,775,22,,Ews,domain.removed.com,/EWS/Exchange.asmx,,,False,,,,ExchangeServicesClient/15.00.0516.014,162.131.154.102,MACHINE0006,401,,,,,,,,,,,,1292,,,OAuthHttpModule:0/0;,0,,,,,,,,,15.6006,,,,,,,,,,,,0,,0,0,,,BeginRequest=2014-04-09T20:05:48.843Z;S:ServiceLatencyMetadata.AuthModuleLatency=0,ProxyRequestHandler_Run_Exception=System.Web.HttpException (0x80004005): Unauthenticated EWS request.    at Microsoft.Exchange.HttpProxy.EwsProxyRequestHandler.OnInitializingHandler()    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass8.<Run>b__7();


    Thursday, April 10, 2014 9:18 PM
  • Anyone find an answer to this issue.  I am seeing the same thing.

    Thanks

    Saturday, April 12, 2014 6:42 PM