Edge Transport service crashes when you view the properties of a poison message in Exchange Server 2016

When you use Queue Veiwer or run the Get-Message cmdlet to view the properties of a poison message in a Microsoft Exchange Server 2016 environment, the Edge Transport service (Edgetransport.exe) crashes. The crash causes messages in process to be moved to the poison queue unexpectedly.
This issue occurs because the value of the count parameter that's used internally isn't changed correctly when the ID of the poison message is given to internal process. It makes internal condition conflicted, and then the EdgeTransport.exe process crashes.
To fix this issue, install Cumulative Update 1 or a later cumulative update for Exchange Server 2016.
To work around this issue, use the Get-Message -queue <server>\poison cmdlet instead of the Get-Message -identity <server>\poison\12345678 cmdlet.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 3139730 - Last Review: 03/15/2016 16:13:00 - Revision: 1.0

Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition

  • kbsurveynew kbfix atdownload kbexpertiseadvanced KB3139730