locked
532 5.3.2 STOREDRV.Deliver; Missing or bad mailbox Database property RRS feed

  • Question

  • We have a distribution group.
    When users send email to this distribution group, they receive from the server on some mailboxes: The recipient's email system isn't accepting messages now.

    Delivery report (on these recipients) says: [{LRT=8/4/2016 6:10:42 AM};{LED=532 5.3.2 STOREDRV.Deliver; Missing or bad mailbox Database property};{FQDN=srv-exch-02...};{IP=172.16...}]




    • Edited by Pavel Belyj Thursday, August 4, 2016 10:13 AM
    Thursday, August 4, 2016 10:13 AM

Answers

  • Hi,
    Please send a test email to the group from OWA to narrow down the issue.
    Also follow above suggestion to send test messages to these recipients in the group to check whether the issue persists. If the issue doesn’t happen when directly sending to the problematic recipients but only occurs when sending to the group, please re-create this distribution group to have a try.
    If the issue persists when sending test messages to single recipient, please create a new user mailbox in Exchange then check the properties between the new mailbox and problematic mailbox in ADUC:
    Right-click the mailbox, select Properties. In the Attribute Editor tab, compare Value for all Attributes.
    Regards,



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

    David Wang_
    TechNet Community Support

    • Proposed as answer by David Wang_ Monday, August 8, 2016 6:49 AM
    • Marked as answer by Pavel Belyj Tuesday, September 20, 2016 8:32 AM
    Friday, August 5, 2016 6:54 AM

All replies

  • I think this is a knows issue fixed in this update and you can also do the workaround mentioned in this artical.

    https://support.microsoft.com/en-in/kb/2983207

    Thursday, August 4, 2016 10:20 AM
  • This article is about of problem Exchange 2013.
    We have Exchange 2016 CU1.
    • Edited by Pavel Belyj Thursday, August 4, 2016 10:25 AM
    Thursday, August 4, 2016 10:24 AM
  • Can you please try the workaround mentioned in this artical?

    To work around this issue, unhide the recipient from the GAL, or disable the Address Book Policy Routing agent.

    Thursday, August 4, 2016 10:26 AM
  • We read the workaround at this articul.
    Recipients for which we have this error don't hidden in the GAL.

    • Edited by Pavel Belyj Thursday, August 4, 2016 10:36 AM
    Thursday, August 4, 2016 10:29 AM
  • Can we directly send the email to recipient added into the group? if yes - i ll recommend to recreate the group.

    If no- Can you try to move the mailboxes to some other database added into this group and try to send the email again as it could be some Db property which is missing and not accepting email.


    Thursday, August 4, 2016 10:43 AM
  • Thanks.
    We thought about moving mailboxes.We will do it.
    It is necessary to determine the cause of the problem.
    Thursday, August 4, 2016 10:55 AM
  • Hi,
    Please send a test email to the group from OWA to narrow down the issue.
    Also follow above suggestion to send test messages to these recipients in the group to check whether the issue persists. If the issue doesn’t happen when directly sending to the problematic recipients but only occurs when sending to the group, please re-create this distribution group to have a try.
    If the issue persists when sending test messages to single recipient, please create a new user mailbox in Exchange then check the properties between the new mailbox and problematic mailbox in ADUC:
    Right-click the mailbox, select Properties. In the Attribute Editor tab, compare Value for all Attributes.
    Regards,



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

    David Wang_
    TechNet Community Support

    • Proposed as answer by David Wang_ Monday, August 8, 2016 6:49 AM
    • Marked as answer by Pavel Belyj Tuesday, September 20, 2016 8:32 AM
    Friday, August 5, 2016 6:54 AM
  • Thanks.

    This problem does not occur, when directly sending to the problematic recipients.

    I'll let you know the result of your decision.


    Friday, August 5, 2016 7:08 AM
  • Have you tried to move the mailbox to other database and then try to send the email.

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help

    • Proposed as answer by David Wang_ Thursday, August 11, 2016 9:16 AM
    Friday, August 5, 2016 9:58 AM