Symptoms

After you use the Suspend-Queue cmdlet to stop processing on a queue in Microsoft Exchange Server 2019 or Exchange Server 2016, more than 100 messages stuck in the submission queue but no event is raised in the Microsoft.Exchange.ManagedAvailability\Monitoring channel. In addition, the Microsoft-Exchange-ActiveMonitoring/MonitorResult channel shows the following error message:

ResultName: SubmissionQueueLengthMonitor

Log Name: Microsoft-Exchange-ActiveMonitoring/MonitorResult

Source: Microsoft-Exchange-ActiveMonitoring

Monitor result (Name=SubmissionQueueLengthMonitor)

<Error>Transition timeout should be in increasing order. TransitionId=1</Error>

<Exception>System.ArgumentException: Transition timeout should be in increasing order. TransitionId=1

It’s expected that there's an event in the Microsoft.Exchange.ManagedAvailability\Monitoring channel stating that the submission queue length exceeds threshold.

Workaround

To work around this issue, you can use the following monitoring override:
Add-ServerMonitoringOverride -Server <servername>  -Identity HubTransport\SubmissionQueueLengthMonitor -ItemType "Monitor" -PropertyName StateTransitionsXml -PropertyValue  '<StateTransitions> <Transition ToState="Degraded" TimeoutInSeconds="0" /> <Transition ToState="Unhealthy" TimeoutInSeconds="1" /> </StateTransitions>'

Resolution

To fix this issue, install one of the following updates:

References

Learn about the  terminology that Microsoft uses to describe software updates.

Daha fazla yardıma mı ihtiyacınız var?

Yeteneklerinizi geliştirin
Eğitimleri keşfedin
Yeni özellikleri ilk olarak siz edinin
Microsoft Insider 'a katılın

Bu bilgi yardımcı oldu mu?

Deneyiminizi ne etkiledi?

Geri bildiriminiz için teşekkür ederiz!

×