Microsoft KB Archive/251533

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:15, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base

XADM: Moving Mailboxes Between Exchange Server 5.5 and Exchange 2000 Server Results in Store Error c1040af4

Article ID: 251533

Article Last Modified on 2/27/2007


  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Exchange Server 5.5 Standard Edition

This article was previously published under Q251533


When you are using the Microsoft Exchange Server 5.5 Administrator program to move mailboxes between computers that are running Microsoft Exchange 2000 Server and Exchange Server 5.5, you may receive the following error message:

An internal processing error has occurred. Try restarting the Microsoft Exchange Administrator program or the Microsoft Exchange Server computer, or both.
Microsoft Exchange Information Store id: c1040af4.

When you perform the operation, shortly after the Progress dialog box appears (at 1 percent complete), the error message is displayed.

Another symptom is that you might receive the following error:

The Microsoft Exchange Server computer does not respond.

Microsoft Exchange Directory ID no: DS_E_COMMUNICATIONS_PROBLEM


Currently, using the Administrator program to move mailboxes is not supported. To move mailboxes, you must use the Active Directory Users and Computers MMC snap-in and follow these steps:

  1. Open Active Directory Users and Computers.
  2. Connect to the domain in question.
  3. Navigate to the user container that contains the Exchange 5.5 user that you want to migrate.
  4. Right-click that user and select Exchange Tasks.
  5. Follow the prompts and select the option to Move Mailbox.

If Move Mailbox is not a choice in the Exchange Tasks Wizard, make sure that the Active Directory Connector has been properly configured and that the Recipient Update Service has been properly updated.


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

Additional query words: exch2kp2w

Keywords: kbbug kberrmsg kbpending KB251533