Issue
The Archive Shuttle Office 365 Module module may log the “Exchange service is busy.” error, and you would like to determine from which Exchange Online Server they are coming, to be able to ask Microsoft to change the throttling limits for it, or investigate further.
Solution
The following should help with identifying the server, which is sending the “Exchange service is busy” responses.
 
We will need to change the Log level for the Office 365 module:

  1. Navigate to “AS Modules” screen
  2. Select the Office 365 module, click on the “Set Log Level” change the “Module Level” to Debug
  3. Review the Office 365 log files:
  • If you are using Archive Shuttle on-premise, the log files are stored on the machine where is core installed, and on the machine where is the module installed (C:\Program Files\QUADROtech\Logs)
  • If you are using Archive Shuttle cloud, the core log files are stored in our datacenter, and the module log files are stored on the machine where is the module installed (C:\Program Files\QUADROtech\Logs)

After those changes are applied, you should see logged information about the server which is sending the busy responses, like the one below.

2015-08-15 15:03:51Z|9568|172| INFO|                                        LogBackoff|[test.user@domain.com]: Exchange service is busy. Sleeping thread until [8/15/2015 3:04:43 PM]
2015-08-15 15:03:52Z|9568|172|DEBUG|                                     TraceResponse|request-id: d952d6f6-b978-4386-9d0b-7bb1ee37e427
2015-08-15 15:03:52Z|9568|172|DEBUG|                                     TraceResponse|X-CalculatedBETarget: XYZXYTYTY.prod.exchangelabs.com
2015-08-15 15:03:52Z|9568|172|DEBUG|                                    TraceResponse|X-DiagInfo: XYZXYTYTY
2015-08-15 15:03:52Z|9568|172|DEBUG|                                     TraceResponse|X-BEServer: XYZXYTYTY 
2015-08-15 15:03:52Z|9568|172|DEBUG|                                    TraceResponse|X-FEServer: XYZXYZZZZ
2015-08-15 15:03:52Z|9568|172|DEBUG|                       GetIngestItemResponseStream|Web exception response content: [<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body>
    <s:Fault>
      <faultcode xmlns:a="http://schemas.microsoft.com/exchange/services/2006/types">a:ErrorServerBusy              </faultcode>
      <faultstring xml:lang="en-US">The server cannot service this request right now. Try again later.</faultstring>
      <detail>
        <e:ResponseCode xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">ErrorServerBusy</e:ResponseCode>
        <e:Message xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">The server cannot service this request right now. Try again later.</e:Message>
        <t:MessageXml xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
          <t:Value Name="BackOffMilliseconds">280092</t:Value>
        </t:MessageXml>
      </detail>
    </s:Fault>
  </s:Body>
</s:Envelope>].

As you know the server name, you can open a case with Microsoft to change the “throttling limits“, or to investigate why you are getting the busy responses.
 

Print Friendly, PDF & Email