XADM: Delivery Receipts Not Properly Routed to MTA for Delivery, Causing 2006 Events

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q243626

Expand all | Collapse all

SYMPTOMS

During normal operation, the following event may appear in the application event log:

Event ID: 2006
Source: MSExchangeIS Private
Category: Transport Sending
Description: The generation of a delivery report or a non-delivery report has failed due to error 0xfffff9bf.

Back to the top

Delivery receipts (DRs) are not being properly routed to the message transfer agent (MTA) for delivery when delegates and recipients exist on different servers. See the "More Information" section for exact steps to reproduce this issue.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

191014 (http://support.microsoft.com/kb/191014/EN-US/ ) XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack

The following files are available for download from the Microsoft Download Center:

x86:

Collapse this imageExpand this image

Download Q248838engi.exe now (http://www.microsoft.com/downloads/release.asp?ReleaseID=25443)
Alpha:

Collapse this imageExpand this image

Download Q248838enga.exe now (http://www.microsoft.com/downloads/release.asp?ReleaseID=25444)

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (http://support.microsoft.com/kb/119591/EN-US/ ) How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Back to the top

APPLIES TO

Microsoft Exchange Server 5.5 Standard Edition

Back to the top

kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbexchange550sp4fix kbfix kbgraphxlinkcritical kbqfe KB243626

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top