Exchange 2010 uses two different types of throttling to help manage the performance of your Exchange server: client and message throttling.  Client throttling tracks the bandwidth each Exchange user consumes and enforces restrictions as necessary. Message throttling are the restrictions put on the number of messages and the number of connections that can be processed by the computer that is running Exchange.  In Exchange 2010 SP1, all client throttling policies are enabled by default.

Throttling is not a new feature in Exchange 2010; however, it could have a negative impact on the accounts used to help administer your Exchange server.  For instance, if you are using any of Sherpa Software’s products to manage, archive or search your mailboxes and throttling is enabled for the account you are running these applications under, you may see the following errors:

  • WARNING: Unable to connect to mailbox ‘Joe Cool’ on ‘Test’
    DETAILS: (@10173009) MAPI_E_NETWORK_ERROR (80040115)
  • ERROR: Unexpected error in ProcessMsgImports: sherpaSoftware.MAPI.mapiException: (@10318B01) MAPI_E_TOO_BIG (80040305)

This is also true for any other application or service you are using to help administer Exchange, such as the BlackBerry® Enterprise Server.

As a result, it is recommended that you disable client throttling for any application or service account needed to help you administer Exchange.  To do that, you will need to create a new Exchange 2010 throttling policy and assign these application or service accounts to that client throttling policy.  The following will do so for the Administrator account in the Sherpa domain:

  1. On a computer that hosts the Exchange 2010 server, open the Microsoft Exchange Management Shell
  2. Type the following to create the new policy, which we are calling SherpaPolicy:
    New-ThrottlingPolicy SherpaPolicy
  3. Type the following to set the parameters of the new policy:
    Set-ThrottlingPolicy SherpaPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null -EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null -EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null
  4. Type the following to add the application or service account to the new policy:
    Set-Mailbox Sherpa/Administrator -ThrottlingPolicy SherpaPolicy

Once you have disabled throttling for the account you are running these applications/services under, you should no longer see the errors caused by Exchange throttling.

For more information on this and other industry related topics, contact Sherpa support.