Share via

msexchangemailboxassistants service is being restarted

AndreyDataFort 11 Reputation points
2021-03-15T05:53:38.2+00:00

We have the single server Exchange 2019 CU 8. There is clean installing, isn't migration. Auto-acceptance of resource groups is not work. The msexchangemailboxassistants service starts and stops immediately. Errors 4999 in logs Watson report about to be sent for process id: 16676, with parameters: E1211S, c-RTL-AMD64, 15.02.0792.010, MSExchangeMailboxAssistants, M.Exchange.Assistants, M.E.A.AssistantsRpcServer.RegisterAssistant, SystemArgumentException, 503a-dumptidset, 15.02.0792.010. ErrorReportingEnabled: False And error 7031 The Microsoft Exchange Mailbox Assistant service terminated unexpectedly. This happened once. The next corrective action will be taken after 5000 msec: Restart the service. We need some advices about this problem. Thx.

Exchange | Exchange Server | Management
0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AndreyDataFort 11 Reputation points
    2021-03-19T06:29:40.827+00:00

    Yes, the exploit detected in the Exchange server made me stay awake for several nights, over the past 2 weeks I've installed KB5000871 on many servers.

    1 person found this answer helpful.
    0 comments
  2. AndreyDataFort 11 Reputation points
    2021-04-09T07:07:07.63+00:00

    Hi! I made a second server. Made DAG, replicated bases, deformed DAG. Removed the first server. Now there are no problems.

    1 person found this answer helpful.
  3. Anonymous
    2021-03-16T02:55:32.163+00:00

    Hi @AndreyDataFort ,

    When this happens, will it cause the high CPU or RAM occupancy? Please check it first.

    MSExchangeMailboxAssistants service crashes when memory usage exceeds 2 GB
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    And also please try this cmdlet to stop the MFA service and check if the Mailbox Assistant stops crashing. 

    Stop-ManagedFolderAssistant

    If this could work, you can change the MFA workcycle by 

    New-SettingOverride -Name "MFA WorkCycle Override" -Component TimeBasedAssistants -Section ELCAssistant -Parameters @("WorkCycle=7.00:00:00") -Reason "Process mailboxes every 7 days"

    Then apply this setting to Exchange servers. 

    Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh

    You can find all the processes here: Configure and run the Managed Folder Assistant in Exchange Server

    Otherwise, you could try to move the arbitration mailboxes to another database.
    Move arbitration mailboxes in Exchange Server
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    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 comments
  4. AndreyDataFort 11 Reputation points
    2021-03-16T06:16:06.893+00:00

    Hello Lou!
    The service msexchangemailboxassistants does not have time to use 2GB because it restarts.
    I've already tried changing MFA cycles and moving the arbitration box, but it didn't help.

  5. AndreyDataFort 11 Reputation points
    2021-03-18T05:32:52.283+00:00

    Hi Lou!
    When I enter the command Stop-ManagedFolderAssistant, I see a message that the mailbox service is not running on the server. Error from RPC 1753.
    I have full control to the V15 folder.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.