locked
432 4.3.2 STOREDRV.Deliver; dynamic mailbox database throttling limit exceeded RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Team,

    We have successfully implemented cross forest migration from between our old and new forest. In old forest we had Exchange 2010 & 2013 environment and wherein our new forest has Exchange 2016 environment. New forest consists of 5 Exchange servers and we are using KEMP as load balancer.

    Our major concern in the mail flow in the Exchange 2016 environment, we are frequently receiving the following error message '432 4.3.2 STOREDRV.Deliver; dynamic mailbox database throttling limit exceeded'. Due to which mails are going in retry mode most of the times.

    I would like to know if there is any value which needs to be increased to clear this error message.

    Request you all to help me out in this regard.

    Thanks & Regards,

    Sirish Oggu

    Monday, December 5, 2016 8:37 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sirish,

    We need to add the keys between the <appSettings> and </appsttings>.

    It's recommended to restart the MSExhcange information store service after you added the keys.

    Hope it's helpful for you.

    Regards,

    Jason Chao

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Tuesday, December 6, 2016 8:04 AM
    • Proposed as answer by Jason.Chao Monday, December 12, 2016 3:08 AM
    • Marked as answer by Sirish Oggu Thursday, February 23, 2017 6:08 AM
    Tuesday, December 6, 2016 7:57 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems recipient in question is receiving heavy traffic & the Exchange by design throttles the volume of messages received by a single recipient.


    Add the two keys below to

    <add key="RecipientThreadLimit" value="2" />
    <add key="MaxMailboxDeliveryPerMdbConnections" value="3" />


    MSExchangedelivery.exe.config located under ".........\Program Files\Microsoft\Exchange server\V15\Bin"
    Restart Transport services

    (We used to add these to EdgeTransport.exe.config in Exchange 2010 in case of similar error)

    Regards,
    Fazal
    Monday, December 5, 2016 11:31 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Fazal,

    Thank you for your response.

    Could you please let me know where to add the two keys, I have attached the screenshot for the reference.

    Regards,

    Sirish Oggu

    Tuesday, December 6, 2016 5:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Please see the below links for a description of the problem, might helps you to resolve this issue:

    http://enterpriseit.co/microsoft-exchange/2010/submission-queue-mailbox-database-thread-limit-exceeded/

    http://blogs.technet.com/b/exchange/archive/2011/04/11/store-driver-fault-isolation-improvements-in-exchange-2010-sp1.aspx

    Hope this helps!

    Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange

    Tuesday, December 6, 2016 5:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sirish,

    We need to add the keys between the <appSettings> and </appsttings>.

    It's recommended to restart the MSExhcange information store service after you added the keys.

    Hope it's helpful for you.

    Regards,

    Jason Chao

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Edited by Jason.Chao Tuesday, December 6, 2016 8:04 AM
    • Proposed as answer by Jason.Chao Monday, December 12, 2016 3:08 AM
    • Marked as answer by Sirish Oggu Thursday, February 23, 2017 6:08 AM
    Tuesday, December 6, 2016 7:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for help, Jason.

    Will check and revert back.

    Regards,

    Sirish Oggu

    Tuesday, December 6, 2016 9:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you manage to solve this? and if yes, how?

    I'm experiencing same issue Exchange 2016 CU12, i have added the two keys and change the numbers to as high as 7 and 8, rebooted servers, but still having this error, users complain of slowness accessing their mailbox.

    Friday, April 12, 2019 12:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Fazal,

    My Exchange get same issue with mailbox database throttling limit exceeded

    But I need to know before run this solution, what is means about value "2" and "3" of the key config?

    Thanks.

    Monday, December 16, 2019 12:24 PM