Forum Discussion
Exchange 2019 Event ID 9042 - File Extraction Time Based Assistant skipps mailbox
Hello everyone!
We only have 3 mailboxes left in our Exchange Server 2019 on-premises, the rest was already migrated to Exchange Online (we have a hybrid environment). We cannot move the other mailboxes at the moment.
Since a couple of days however we receive the following warning message in the event log of our Exchange Server:
Event-ID: 9042 (MSExchange Assistants)
"Service MSExchangeMailboxAssistants. File Extraction Time Based Assistant for database <dbname> (<db id>) is exiting a work cycle. No mailboxes were successfully processed. 1 mailboxes were skipped due to errors. 0 mailboxes were skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed."
Unfortunately, that's all the error messages we receive and I have no clue how to find out which mailbox is skipped. Or why...
How can we find out which mailbox is causing the problem? How can we then solve it?
Many thanks!
Best regards,
Markus
Hello,
soooooo.... The problem seems to be resolved. After the restart there are no more Event ID 9042 messages on the Exchange server.
I still wonder why we can't figure out which mailbox was skipped and why. Why isn't this logged somewhere on the exchange server..?
Has no one any idea?
Move the mailbox to another database,
Then see if the issue persists. You can also look at logs present in:
%Exchangeinstallpath%Logging\Assistants
To see if the reported assistant has registration events.
If it does, on the server that hosts the mailbox, perform the following to see if more logs add context:
Set-EventLogLevel "MSExchangeIS\General" -Level Expert
Set-EventLogLevel "MSExchangeMailboxAssistants\Service" -Level Expert
Set-EventLogLevel "MSExchangeMailboxAssistants\Discovery" -Level Expert
See if mailbox/ related assistant related errors start to occur.
Thank you very much for your reply!
We do not have another database, only one. But if I would move a mailbox, how do I know which one is causing the error? Which one should I move?
I looked at the logs in the folder you mentioned. Unfortunately, I have no idea what I should be searching for. The MSExchangeMailboxAssistants log looks like this at the time the error occurred:
Thanks for clarifying!
In the meantime I will set the log levels to expert as suggested by you. I will do this this evening and have a look at the logs tomorrow (afterwards I will set the level back to lowest).
Thanks again!
Hello TAE_YOUN_ANN ,
I changed the logging level as suggested. Unfortunately, I can't see anything helpful in the logs, there are no new errors, warnings or info that tell me where the problem is. Or what error the assistant has.
The log in the Exchange installation folder looks the same as yesterday. And there's nothing obvious in the event viewer as well.
I will change the logging level back to the standard. Anything else I can try?
Thank you very much.
Hello TAE_YOUN_ANN
thanks again for the reply.
I would like to avoid creating a new database just for three mailboxes. Unfortunately, we also cannot move them to EXO at the moment...
This evening we will be updating the Exchange on premises server. It is my hope that the following restart could solve the issue. I will report back tomorrow.
Hello @MarkusQ_oh22
Thanks for updating the progress. Also, I hope you have good results after updating Exchange Server.
Hello,
soooooo.... The problem seems to be resolved. After the restart there are no more Event ID 9042 messages on the Exchange server.
I still wonder why we can't figure out which mailbox was skipped and why. Why isn't this logged somewhere on the exchange server..?
Hello, MarkusQ_oh22
It’s good to hear the Event ID 9042 issue is resolved after the restart. Event ID 9042 usually indicates that a mailbox was skipped during processing, typically because it encountered an error or timed out. However, Exchange doesn’t always log specific details about which mailbox was skipped in the event logs, which can make troubleshooting difficult.
Yes, I noticed that Exchange does indeed not log the details of the mailboxes skipped. I personally think that this is a design flaw. Which mailbox is skipped is not a "detail", it is fundamentally important to solving the issue, in my opinion at least.
Well, anyway, it is resolved now. So thank you for your support.
