We have implemented two Exchange 2013 CU3 servers in a DAG covering 2 AD sites in the same domain. Each server has implemented online archiving for users. One of the sites has replicated the archive database in the DAG.

However, the archive mailboxes are growing slowly, if at all. If we manually start the managed assistant for a mailbox, it runs for a few minutes and then stops. 

In the event log, a few events are generated:

MSExchangeAssistants 9028:

Service MSExchangeMailboxAssistants. Managed Folder Mailbox Assistant caused the process to terminate 1 times while processing mailbox (unknown) on database Live (c8decfb1-1e25-4a02-bf83-976e378b2ca3). The following exception caused the failure: Microsoft.Exchange.Data.Directory.ResourceHealth.ResourceUnhealthyException: Resource 'MdbReplication(Live)' is unhealthy and shouldn't be accessed.

   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCHealthMonitor.InternalThrottleStoreCall(List`1 archiveResourceDependencies)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcSubAssistant.ThrottleStoreCallAndCheckForShutdown(ExchangePrincipal mailboxOwner, List`1 archiveResourceDependencies)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.CalendarLogExpirationEnforcer.ProcessFolderContents(Folder folder, ItemQueryType itemQueryType)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.CalendarLogExpirationEnforcer.CollectItemsToExpire()
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.SysCleanupEnforcerBase.CollectItemsWithGuard()
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.SysCleanupEnforcerBase.InvokeInternal()
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.SysCleanupEnforcerBase.Invoke()
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.SysCleanupEnforcerManager.Invoke(MailboxDataForTags mailboxDataForTags, ElcParameters parameters)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.SysCleanupSubAssistant.Invoke(MailboxSession mailboxSession, MailboxDataForTags mailboxDataForTags, ElcParameters parameters)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeCore(MailboxSession mailboxSession, StatisticsLogEntry logEntry, ElcParameters parameters)
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeInternalAssistant(MailboxSession mailboxSession, InvokeArgs invokeArgs, List`1 customDataToLog, Int32 totalAttempts)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.DoWork(AssistantTaskContext context)
   at Microsoft.Exchange.Assistants.TimeBasedDatabaseJob.ProcessMailboxUnderPoisonControl(AssistantTaskContext context, EmergencyKit kit)
   at Microsoft.Exchange.Assistants.TimeBasedDatabaseJob.<>c__DisplayClass9.<ProcessStoreMailbox>b__8()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)

We also get error 9022:

Service MSExchangeMailboxAssistants. Managed Folder Mailbox Assistant for database Live (c8decfb1-1e25-4a02-bf83-976e378b2ca3) has finished an on-demand request. 0 out of 1 mailboxes were successfully processed.  0 mailboxes were skipped due to errors.

Finally, we get MSExchange Common 4999:

Watson report about to be sent for process id: 17872, with parameters: E12, c-RTL-AMD64, 15.00.0775.038, MSExchangeMailboxAssistants, MSExchangeMailboxAssistants, M.E.M.A.E.ELCHealthMonitor.InternalThrottleStoreCall, M.E.Assistants.TransientMailboxException, a898, 15.00.0775.031.
ErrorReportingEnabled: True

Can anyone give any pointers as to how to resolve this?

Hi,

Please check whether the mailbox is too large that Item counts are too high to process and the Managed Folder Assistant is getting throttled. Or the volume of mail to move exceeds the recoverable items quota of the database.

Please try the following changes:

1. Change the quota to a value that you believe can hold all the mail:

Set-mailboxdatabase <identity of the database> -recoverableitemswarningquota 300gb -recoverableitemsquota 350gb

2. Give more time to work:

Set-MailboxServer <servername> -ManagedFolderWorkCycle 3.00:00:00 -ManagedFolderWorkCycleCheckpoint  3.00:00:00

3. Restart Microsoft Exchange Mailbox Assistants service.

Thanks,

Hi,

I ran the PS commands you gave, restarted the service and started the assistant on a mailbox. It behaved as before, it worked for a few minutes and then stopped. The error in the event log looked similar to before, but now seems to reference the Archive database:

Service MSExchangeMailboxAssistants. Managed Folder Mailbox Assistant caused the process to terminate 1 times while processing mailbox (unknown) on database Live (c8decfb1-1e25-4a02-bf83-976e378b2ca3). The following exception caused the failure: Microsoft.Exchange.Data.Directory.ResourceHealth.ResourceUnhealthyException: Resource 'MdbReplication(Archives)' is unhealthy and shouldn't be accessed.
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCHealthMonitor.InternalThrottleStoreCall(List`1 archiveResourceDependencies)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.LocalArchiveProcessor.ExpireInBatches(List`1 listToSend, Folder sourceFolder, Folder targetFolder, ElcSubAssistant elcSubAssistant, Action retentionActionType, Int32 totalFailuresSoFar, List`1& foldersWithErrors, Int32& newMoveErrorsTotal)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.LocalArchiveProcessor.MoveToArchive(ItemSet itemSet, ElcSubAssistant assistant, FolderArchiver folderArchiver, Int32 totalFailuresSoFar, List`1& foldersWithErrors, Int32& newMoveErrorsTotal)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagExpirationExecutor.PrepareAndExpireInBatches(List`1 listToSend, Action retentionActionType)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ExpirationExecutor.ExecuteTheDoomed()
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ExpirationExecutor.CheckAndProcessItemsOnBatchSizeReached(List`1 list)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ExpirationTagEnforcer.EvaluateAndEnlistItem(Object[] itemProperties, PropertyIndexHolder propertyIndexHolder)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ExpirationTagEnforcer.CollectItemsToMoveByDefault(MailboxSession session)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ExpirationTagEnforcer.CollectItemsToExpire(MailboxSession session)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ExpirationTagEnforcer.Invoke()
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagEnforcerManager.InvokeInternal(MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagEnforcerManager.Invoke(MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.InvokeInternal(MailboxSession mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.Invoke(MailboxSession mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeCore(MailboxSession mailboxSession, StatisticsLogEntry logEntry, ElcParameters parameters)
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeInternalAssistant(MailboxSession mailboxSession, InvokeArgs invokeArgs, List`1 customDataToLog, Int32 totalAttempts)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.DoWork(AssistantTaskContext context)
   at Microsoft.Exchange.Assistants.TimeBasedDatabaseJob.ProcessMailboxUnderPoisonControl(AssistantTaskContext context, EmergencyKit kit)
   at Microsoft.Exchange.Assistants.TimeBasedDatabaseJob.<>c__DisplayClass9.<ProcessStoreMailbox>b__8()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)

Hi did you ever fix the above issue? I have the exact same problem on my exchange 2010 server