Microsoft KB Archive/818324

From BetaArchive Wiki
Knowledge Base


Article ID: 818324

Article Last Modified on 10/26/2006



APPLIES TO

  • Microsoft Exchange 2000 Server Standard Edition




SYMPTOMS

After you migrate a Microsoft Exchange Server 5.5 organization to Microsoft Exchange 2000 Server, when users reply to messages that they received before the migration, they may receive a non-delivery report (NDR).

CAUSE

This problem occurs if the Exchange 5.5 organization contains a plus sign (+) in the organization name. During the migration, the Exchange Migration Wizard creates an X.500 proxy e-mail address to the Microsoft Active Directory directory service account of the migrated mailbox. This X.500 proxy e-mail address is the distinguished name of the mailbox in the Exchange 5.5 organization. During the migration, if the Exchange 5.5 Lightweight Directory Access Protocol (LDAP) query locates a plus sign in the Exchange 5.5 organization name, the Migration Wizard places quotation marks around the organization name. The Migration Wizard does not remove these quotation marks when it creates the X.500 proxy address in Active Directory. For example, the Migration Wizard may generate an X.500 proxy address that is similar to the following:

/o="My+Org"/ou=MIGWIZOLD/cn=Recipients/cn=Username


This prevents the migrated users from replying to messages that they received before the migration. If you manually remove the quotation marks from around the organization name in the X.500 proxy address, users can successfully reply to messages that they received before the migration.

RESOLUTION

Cumulative Rollup Information

To resolve this problem, obtain the September 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:

824282 September 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 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: Migration Wizard

The English version of this hotfix 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
   --------------------------------------------------------------  
   24-Apr-2003  00:37  6.0.6458.0      2,551,808  Mlmig32.dll      
   23-Apr-2003  20:16  6.0.6458.0         69,632  Mlmignts.dll     

Note Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). For additional 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


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.


Additional query words: kbExchange2000preSP4septbarFix

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB818324