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.

XADM: How to Prevent Mail Loss When Move Mailbox Operation Is Unsuccessful


View products that this article applies to.

This article was previously published under Q252869

↑ Back to the top


Symptoms

After you perform a Move Mailbox operation, the mailbox is displayed in the "mailbox resources" of both the source and destination servers. On the source server, the total kilobytes displayed is close to 0. On the destination server, the total kilobytes displayed is the correct amount of data.

If you attempt to perform another Move Mailbox operation, the following error message is displayed:
A duplicate mailbox was found due to problems during a Move Mailbox procedure. The duplicate mailbox has been deleted. Try again later. Microsoft Exchange Server Information Store ID no: c1040b00
The mailbox data on the destination server is deleted and the mail is lost.

↑ Back to the top


Cause

During a Move Mailbox operation the mailbox data is moved to the destination server, but the directory object is not. This results in the data being homed on the destination server and the Mailbox Directory Object being stranded on the source server.

If you attempt to move the mailbox a second time, the user's mailbox information is removed from the destination server's information store. The source server also removes the mailbox data because it detects the move as being successful. At this point, the user's mailbox information is lost.

↑ Back to the top


Workaround

Do not attempt a second Move Mailbox operation on the mailbox because you will lose all data. To work around the behavior, use the following steps.

WARNING: If you use the raw mode of the Exchange Server Administrator program (admin /r) incorrectly, serious problems may occur that may require you to reinstall Microsoft Windows NT Server, Microsoft Exchange Server, or both. Microsoft cannot guarantee that problems that result from using raw mode incorrectly can be solved. Use raw mode at your own risk.

  1. Start the Microsoft Exchange Server Administrator program in raw mode by typing the following at a command prompt:
    c:\exchsrvr\bin\admin /r
  2. Use the appropriate method:

    Method 1

    1. On the source server, locate the Recipients container and click the mailbox.
    2. On the File menu, click Raw Properties.
    3. Change the Home-MDB and Home-MTA attributes to reflect the destination server.

      NOTE: These names need to be in the following Distinguished Name (DN) format:
      /o=<Organization>/ou=<Site>/cn=Configuration/cn=Servers/cn=<ServerName>/cn=Microsoft Private MDB
      /o=<Organization>/ou=<Site>/cn=Configuration/cn=Servers/cn=<ServerName>/cn=Microsoft MTA

    Method 2

    1. On the source server, delete the server recipient for the mailbox.
    2. On the destination server, re-create the mailbox that you deleted on the source server and use the same Distinguished Name (DN).
    The user can now log on to the mailbox with no data loss.

↑ Back to the top


More information

The first Move Mailbox operation did not work because during the Move Mailbox process, the Administrator program first copies the selected user's mailbox to the selected destination server (the Move Mailbox operation only works between servers in the same site). After the mailbox is successfully moved, the Move Mailbox function then issues a DS Sync command. During the synchronization process, the Administrator program passes the same source and destination server to the Move Mailbox function. As a result, the user's directory object is not moved.

↑ Back to the top


Keywords: KB252869, kbprb

↑ Back to the top

Article Info
Article ID : 252869
Revision : 5
Created on : 10/27/2006
Published on : 10/27/2006
Exists online : False
Views : 413