Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


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 fix this issue, install Cumulative Update 12 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.


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.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?

Thank you for your feedback!