Return
-
Title
MAgE processing stalls after an Exchange Server reboot or loss of connectivity from the Agent Host -
Description
MAgE processing may be found to have stalled after the reboot of a source or target Exchange Server reboot or after temporary loss of network connectivity from the Agent Host.
A Windows Event Log error may be observed on the Agent Host with Source: QMMEX and a stack as follows:
Index was outside the bounds of the array. at Quest.MigrationManager.Exchange.Basis.Lock.LockReleaseForced(Int32 ix)
at Quest.MigrationManager.Exchange.Basis.Lock.Latcher.UnlatchForced()at Quest.MigrationManager.Exchange.Basis.Lock.Latcher.DisposeUnmanaged()at Quest.MigrationManager.Exchange.Basis.Lock.Latcher.Dispose(Boolean disposing)at Quest.MigrationManager.Exchange.Basis.Lock.Latcher.Finalize() -
Resolution
If restarting the agents does not cause processing to resume, a reboot of the Agent Host may be required. -
Additional Information
There may be informational Windows events also or instead of the error above. The Description will take the form: Exceeded number of allowed failed thread aborts '1', going to restart ourselves (QMMEXA), running SOMECOMPANYNAME..MMEx.Agent.Restarter.exe "QsMAgE (AgentHost)(UnifiedCalendarSync_1)" 6612 "C:\ProgramData\Quest Software\Migration Agent for Exchange\UnifiedCalendarSync_1\MAgE.log" 1