Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

EdgeTransport.exe crashes when you view details of messages in the poison message queue


View products that this article applies to.

Symptoms

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

↑ Back to the top


Cause

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.

↑ Back to the top


Resolution

To fix this issue, install Cumulative Update 12 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.

↑ Back to the top


Workaround

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.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

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

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3134952
Revision : 1
Created on : 1/7/2017
Published on : 3/15/2016
Exists online : False
Views : 238