question

CatherineJaszewski-5685 avatar image
0 Votes"
CatherineJaszewski-5685 asked ShiroZeta-7308 commented

How to fix OAB Generator error

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?

office-exchange-server-administration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndyDavid avatar image
1 Vote"
AndyDavid answered ShiroZeta-7308 commented

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.

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Andy,

Thank you for your answer. I am still struggling with this issue but have since figured some things out.
today I created a new OAB and used the update-OfflineAddressBook. It immediately caused my active database to go offline and the passive copy to take over. But oddly, i also notice it puts the OAB mailbox in quarantine which could be the reason why I am getting the MSExchangeIS 1002 event...Because it can't find the OAB because its in quarantine.
I just found an article that suggest I may have to set my transportconfig configuration from 'unlimited" to some random limit (this person used 35MB) for maxreceivesize and maxsendsize. I am going to explore this option a little closer and will let you know if it resolves my OAB mailbox issue.
Just keeping you in the loop...thank you for all your help

1 Vote 1 ·
AndyDavid avatar image AndyDavid CatherineJaszewski-5685 ·

Yes, absolutely make that change and test.

1 Vote 1 ·

Good Morning Andy,

Setting the TransportConfig's MaxReceiveSize and MaxSendSize from 'Unlimited' to 36MB and 10MB (values we had set for the Receive and Send connectors) seems to have taken care of the issue. I am no longer getting MSDIagnostic Event 1006 (which was putting the OAB mailbox in quarantine), or the MSExchangeIS Event 1002 (which was stating OAB Generator failed because the process was getting Null value), or MSExchangeIS Event 1013 (which was dismounting my active mailbox database.)

As always, your input and guidance is always welcome!

1 Vote 1 ·
ShiroZeta-7308 avatar image ShiroZeta-7308 CatherineJaszewski-5685 ·

Thanks to you both. Changing the MaxReceiveSize and MaxSendSize and taking the OAB out of quarantine fixed it for me. However in my situation the OAB mailbox wasn't showing in quarantine when running the Exchange shell command to check so couldn't change the flag that way. However when I looked in the registry I could find the GUID for it under the following key.

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<ServerName>\Private-{dbguid}\QuarantinedMailboxes{mailbox guid}

I deleted the key for that mailbox GUID and after that I could run the update-OfflineAddressBook command without it crashing the database.

0 Votes 0 ·
ZhengqiLou-MSFT avatar image
0 Votes"
ZhengqiLou-MSFT answered ZhengqiLou-MSFT commented

Hi @CatherineJaszewski-5685 ,

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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @CatherineJaszewski-5685 ,

Do the suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

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.

0 Votes 0 ·
pramodss-2642 avatar image
0 Votes"
pramodss-2642 answered

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.