How to fix OAB Generator error

Catherine Jaszewski 716 Reputation points
2021-06-04T15:18:13.197+00:00

I am getting a MSExchangeIS Event 1002 followed by a MSExchangeIS Event 1013 which causes mailbox database to go offline. Fortunately, the DAG kicks in and the passive copy of the database activates. These two events are triggered by the OAB Generator process. I can duplicate the issue by using the cmdlet "Update-OfflineAddressBook" after re-creating the new OAB. Oddly, the two events do not happen all the time. For instance when the automatic process happens at 1:15AM (per the 8 hour OAB Generator schedule) it is successful (no errors). But then the next automatic process happens at 9:15AM, Event 1002 and Event 1013 occur causing the mailbox database to crash and passive copy mounts.

I've recreated the Offline Address Box - this did not solve the issue.
I've created a new Arbitration mailbox and set a new OAB to use the new Arbitration mailbox. This did not solve the issue.

The MSExchangeIS Event 1002 (which I think is the culprit) starts with "Unhandled exception (System.InvalidOperationException: Nullable object must have a value."

Has anyone else experienced this frustrating issue? If so, were you able to resolve it? And how?

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,346 questions
0 comments No comments
{count} votes

Accepted answer
  1. Andy David - MVP 141.5K Reputation points MVP
    2021-06-05T14:57:21.613+00:00

    Hey there, are you on the latest CU?
    Any anti-malware or other 3rd party software installed on the Exch Server?

    I havent seen this but I would open a ticket with Microsoft Support if you can easily reproduce this. They should be able to get some diags and traces.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
  1. Xzsssss 8,861 Reputation points Microsoft Vendor
    2021-06-07T02:27:44.58+00:00

    Hi @Catherine Jaszewski ,

    Please also refer to this article and see if it helps: Event ID 1002 when the store worker process crashes in Exchange Server 2019 and 2016
    And please also check if there are any useful messages in Event 1013.

    I think you could try recovering the server if the above methods don't help.

    Best regards,
    Lou


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. pramodss 1 Reputation point
    2021-06-18T21:14:28.47+00:00

    This discussion helped the same issue I was having on a single Exchange 2019 server with a single database. OAB generation was crashing the database. Found a related link on this issue. Hope it helps. Appears to be a bug in Exchange 2019 Server.
    https://www.azure365pro.com/mailboxes-into-quarantine-after-migrating-to-exchange-2019/

    Regards

    0 comments No comments