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.

NDRs are deleted by the Microsoft Exchange Information Store service when a public folder is designated as the recipient in Exchange Server 2003


View products that this article applies to.

Symptoms

In Microsoft Exchange Server 2003, non-delivery reports (NDRs) are deleted by the Microsoft Exchange Information Store service (Store.exe) when a public folder is designated as the recipient.

Additionally, the following event is logged in the Application log to indicate that the NDR has been deleted:


Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Transport Delivering
Event ID: 2028
Description: The delivery of a message sent by public folder TESTPFA8D6137940507B2FE9665C90202A1EEE00B7A6 has failed. To: TEST_USER Cc: The non-delivery report has been deleted.

This behavior occurs even if you use Exchange System Manager to set the Diagnostics Logging tab to None in the following tree view:
MSExchangeIS\Public Folder\Transport Delivering

↑ Back to the top


Cause

This issue occurs because Exchange Server 2003 ignores the configured diagnostic logging level. Therefore, Exchange Server 2003 always logs event ID 2028 if the following conditions are true:
  • A public folder is designated as the recipient in Exchange Server 2003.
  • A DR or an NDR message is sent to the recipient.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 1 (SP1).

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993 How to obtain the latest service packs for Exchange Server 2003

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Exchange Server 2003 post-Service Pack 2 hotfixes
File nameFile versionFile sizeDateTimePlatform
Exhotfixuninst.dll6.5.7233.4113,82408-Aug-200522:02x86
Store.exe6.5.7650.155,248,51221-Dec-200504:23x86
Exhotfix.cdfNot applicable2,27421-Dec-200506:38Not applicable
Exchange Server 2003 post-Service Pack 1 hotfixes
File nameFile versionFile sizeDateTimePlatformSP requirement
Exhotfixuninst.dll6.5.7232.8913,82403-Mar-200521:51x86SP2
Mdbmsg.dll6.5.7233.313,261,95225-Jun-200502:29x86SP2
Redir.aspNot applicable3,30404-Jun-200501:56Not applicableSP2
Store.exe6.5.7233.315,176,83225-Jun-200503:03x86SP2
Exhotfix.cdfNot applicable2,61627-Jun-200519:10Not applicableSP2

↑ 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


More information

After you install this hotfix, the Exchange Server 2003 server will examine the configured diagnostic logging level. However, Exchange Server 2003 logs the event ID 2028 if you use Exchange System Manager to increase the diagnostic logging level.

Event ID 2028 is logged only when you use Exchange System Manager to increase the diagnostic logging to Minimum, to Medium, or to Maximum in the following tree view:
MSExchangeIS\Public Folder\Transport Delivering
To increase the diagnostic logging level, follow these steps.

Note Because there are different versions of Exchange Server 2003, the user interfaces may be different for Exchange System Manager.
  1. Start Exchange System Manager.
  2. Expand Administrative Groups, expand AdministrativeGroupName, and then expand Servers.
  3. Right-click Exchange_Server, and then click Properties.
  4. Click the Diagnostics Logging tab, expand MSExchangeIS, and then click Public Folders in the Services list.
  5. In the Categories list, click Transport Delivering.
  6. In the Logging Level area, click Medium, click Apply, and then click OK.
  7. Quit Exchange System Manager.

↑ Back to the top


Keywords: kbnosurvey, kbarchive, kbqfe, kbhotfixserver, kbexchstore, kbfix, kbbug, kbexchange2003presp2fix, kbautohotfix, KB900088

↑ Back to the top

Article Info
Article ID : 900088
Revision : 8
Created on : 1/16/2015
Published on : 1/16/2015
Exists online : False
Views : 317