XGEN: No DSN Relay for Exchange Server 5.5 Mailbox Users and Event ID 2078 Message Is Logged

Article translations Article translations
Article ID: 307215 - View products that this article applies to.
This article was previously published under Q307215
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

When a user with a Microsoft Exchange Server 5.5 mailbox sends an e-mail message with a delivery receipt requested outside that user's organization by means of a Simple Mail Transfer Protocol (SMTP) smart host that is connected by an Exchange 2000 server, the Exchange Server 5.5 mailbox may not get Delivery Status Notification (DSN) relay.

The information store in the Exchange 2000 may also generate an event ID 2078 message in the Application event log:
Event ID: 2078
Source: MSExchangeIS Mailbox
Category: Transfer Out Of Gateway
Computer: BO00SXPCN1
Description: Unable to submit, send or transfer out a message. Database "First Storage Group\Mailbox Store (BO00SXPCN1)".
Check PR_REPORT_DESTINATION_ENTRYID.
You may also receive non-Deliverable messages with the following text in the body: "The recipient was detected looping within the message transfer service".

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: Transport Core

Collapse this tableExpand this table
File nameVersion
Phatcat.dll6.0.4720.54
Peexch50.dll6.0.4720.54

NOTES:
  • Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
  • Apply the hot fix to the server that currently has the issue and any server that could be a possible failover server for Internet Mail.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Properties

Article ID: 307215 - Last Review: October 24, 2013 - Revision: 1.4
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kberrmsg kbexchange2000presp2fix kbexchange2000sp2fix kbfix KB307215

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com