Article ID: 812806
Article Last Modified on 10/25/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
- Microsoft Exchange 2000 Enterprise Server
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When a Microsoft Exchange 2000 Server user or a Microsoft Exchange Server 2003 user composes and sends a message to a recipient on an external domain that is configured to use a custom non-delivery report (NDR), if the address of the recipient is non-deliverable, the Exchange user may not receive the custom NDR as expected. Instead, the Exchange user receives a standard NDR in Microsoft Outlook that is similar to the following:
CAUSE
This issue occurs because when you use a MAPI client to open and view an NDR, the NDR is reformatted by the Exchange 2000 or Exchange 2003 information store, and any customization that the NDR contains is lost. If you access the message from a non-MAPI client, the customizations that are contained in the NDR are retained.
RESOLUTION
Cumulative rollup information for Exchange 2000
To resolve this problem in Exchange 2000, obtain the September 2003 Exchange 2000 Server post-Service Pack 3 (SP3) Rollup. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824282 September 2003 Exchange 2000 Server post-Service Pack 3 Rollup
After you install the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup, edit the registry to add the RenderDSNsAsMessages DWORD value to the following registry subkey on the server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent
To do this, follow these steps.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Click Start, and then click Run.
- In the Open box, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent - On the Edit menu, point to New, and then click DWORD Value.
- Type RenderDSNsAsMessages, and then press ENTER.
Important Make sure that you choose a REG_DWORD value type. - On the Edit menu, click Modify.
- In the Value data box, type 1, and then click OK.
- Quit Registry Editor.
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Component: Information store
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 tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------- 09-Jan-2003 18:44 6.0.6397.0 3,915,776 Cdoex.dll 09-Jan-2003 18:18 6.0.6397.0 131,072 Drviis.dll 09-Jan-2003 18:44 6.0.6397.0 3,571,712 Excdo.dll 09-Jan-2003 18:19 6.0.6397.0 258,048 Exmime.dll 09-Jan-2003 18:36 6.0.6397.0 1,691,648 Exoledb.dll 09-Jan-2003 18:36 6.0.6397.0 303,104 Exsmtp.dll 09-Jan-2003 17:48 6.0.6397.0 2,260,992 Mdbmsg.dll 09-Jan-2003 17:19 6.0.6397.0 32,768 Mdbrole.dll 09-Jan-2003 18:15 6.0.6397.0 94,208 Peexch50.dll 09-Jan-2003 18:16 6.0.6397.0 393,216 Phatcat.dll 09-Jan-2003 18:18 6.0.6397.0 4,591,616 Store.exe
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
After you install the hotfix, edit the registry to add the RenderDSNsAsMessages DWORD value to the following registry subkey on the server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent
To do this, follow these steps.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Click Start, and then click Run.
- In the Open box, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent - On the Edit menu, point to New, and then click DWORD Value.
- Type RenderDSNsAsMessages, and then press ENTER.
- On the Edit menu, click Modify.
- In the Value data box, type 1, and then click OK.
- Quit Registry Editor.
Information for Exchange 2003
Exchange 2003 supports the following registry subkey. Therefore, you do not have to apply the hotfix that is mentioned for Exchange 2000. To resolve this problem in Exchange 2003, edit the registry to add the RenderDSNsAsMessages DWORD value to the following registry subkey on the server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent
To do this, follow these steps.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
- Click Start, and then click Run.
- In the Open box, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\InternetContent - On the Edit menu, click New, and then click DWORD Value.
- Type RenderDSNsAsMessages, and then press ENTER.
- On the Edit menu, click Modify.
- In the Value data box, type 1, click Decimal under Base, and then click OK.
- Quit Registry Editor.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Additional query words: kbExchange2000preSP4septbarFix
Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB812806
