none
Same GetUserAvailability responses different results RRS feed

  • Question

  • Hello,

    with GetUserAvailability from Exchange web services, i tried to get a bunch of dates for a defined group of users for one date range. When i submit this request for a  couple of times i get the same result, but after  (i guess) more than 10 request i am getting lesser results (there could be no change on appointments, it is a test server).

    The xml- files are equal, but with the second request i got this errors in EWSResponse:The error response from ews is this.

    <ResponseMessage ResponseClass="Error">
                  <MessageText>Mailbox logon failed., inner exception: This operation exceeds the throttling budget for policy part 'RPC', budget type: 'EWS'.  Suggested backoff time 33506 ms.</MessageText>
                  <ResponseCode>ErrorMailboxLogonFailed</ResponseCode>
                  <DescriptiveLinkKey>0</DescriptiveLinkKey>
                  <MessageXml>
                    <ExceptionType xmlns="http://schemas.microsoft.com/exchange/services/2006/errors">Microsoft.Exchange.InfoWorker.Common.Availability.MailboxLogonFailedException</ExceptionType>
                    <ExceptionCode xmlns="http://schemas.microsoft.com/exchange/services/2006/errors">5008</ExceptionCode>
                    <ExceptionServerName xmlns="http://schemas.microsoft.com/exchange/services/2006/errors">CAS1</ExceptionServerName>
                  </MessageXml>
                </ResponseMessage>

    Can anyone explain that reason of this error to me, or notice such a behaviour and has an explanation to this. or has fixed such an error? 

    Best regards from Germany

    Hartwig Pudzich

    Friday, November 11, 2011 9:57 AM

All replies

  • What that error means in that the user submitting the request has exceeded their throttling budget read http://blogs.technet.com/b/exchange/archive/2010/08/27/3410837.aspx for more. Basically the default throttling budget is meant for a normal mailbox user so as an application that makes a large number of requests like your trying to submit in a certain timeframe means you can overrun the default thresholds. If its a test server you may just want to disable throttling for that user.

    Cheers
    Glen

    Monday, November 14, 2011 2:37 AM