Microsoft KB Archive/328292

= XADM: The Recipient Update Service Creates Duplicate LegacyExchangeDNs =

Article ID: 328292

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange Server 2000 Service Pack 3
 * Microsoft Exchange Server 2000 Service Pack 1
 * Microsoft Exchange 2000 Server Service Pack 2

-



This article was previously published under Q328292





SYMPTOMS
Two or more users with the same alias may also have the same LegacyExchangeDN. Because of this, Exchange 2000 may return mail to the sender and generate non-delivery reports (NDRs).



CAUSE
The Recipient Update Service looks up entries on the global catalog server before the Recipient Update Service stamps the LegacyExchangeDN, to try to make sure that no duplicates exist.

This problem may occur if the global catalog server did not have had time to receive the replicated changes from a domain controller. Therefore, the Recipient Update Service incorrectly determines that the current address that the Recipient Update Service is stamping is unique.



Cumulative Patch Information
To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

813840 XGEN: March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

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 fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Component: Recipient Update Service

The English version of this fix has the file attributes (or later) 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 --  28-AUG-2002   18:30:28   6.0.6318.0   602,112   Abv_dg.dll NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.



MORE INFORMATION
After you apply this fix, the Recipient Update Service looks at a domain controller and also the global catalog servers to make sure that the Recipient Update Service does not stamp a duplicate LegacyExchangeDN.

Additional query words: RUS DC kbExchange2000preSP4marchbarFix

Keywords: kbhotfixserver kbqfe kbbug kbexchange2000presp4fix kbfix kbqfe KB328292

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.