Microsoft KB Archive Search

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.

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

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

View products that this article applies to.

Symptoms

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.

↑ Back to the top

Cause

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.

↑ Back to the top

Resolution

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

↑ Back to the top

Workaround

To work around this issue, use the Get-Message -queue <server>\poison cmdlet instead of the Get-Message -identity <server>\poison\12345678 cmdlet.

↑ 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

Keywords: kbsurveynew, kbfix, atdownload, kbexpertiseadvanced, kb

↑ Back to the top

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