In an Exchange Server 2013 environment, when you try to view the details of messages in the poison message queue by using one of the following methods, EdgeTransport.exe crashes:
Queue viewer console
Get-Message cmdlet when you're using the Message ID option in the Exchange Management Shell
This issue occurs because, when you access a poison message by specifying Message ID, an internally used counter value is not incremented. In this situation, an exception occurs and EdgeTransport.exe crashes.
To work around this issue, use the -queue option instead of the Message ID option as in the following example:
get-message -queue server_name\poison
Note There is no workaround when you use the Queue Viewer console.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.