Move request that uses RemoteLegacy from Exchange Server 2013 to Exchange Server 2007 never completes

Symptoms
Assume that you have an environment that has Microsoft Exchange Server 2013 and Exchange Server 2007 deployed in different organizations. When you move a mailbox from Exchange Server 2013 to Exchange Server 2007 by running the New-MoveRequest cmdlet together with the RemoteLegacy parameter, the move request is created. However, the process remains in the "InProgress" state for a long time and then fails. Additionally, you receive an error message that resembles the following:
Error: Move for mailbox '/o=Contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user1' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'Exch1\First Storage Group\Mailbox Database' (agent None).
Failure Reason: Information for database 887f8adb-1e98-4b6d-99f8-1542a630ab6c hasn't been collected.

When this issue occurs, you can also detect event ID 10015 or 10012 in the Application log of Exchange Server 2013 server that performs the move request.
Cause
This issue occurs because Exchange Server 2013 incorrectly performs a DataMoveReplicationConstraint check against the Exchange Server 2007 database.
Workaround
To work around this issue, follow these steps to disable the DataMoveReplicationConstraint check on the Exchange Server 2013 server that you want to perform the move request:
  1. Browse to the MsExchangeMailboxReplication.exe.config file and open it in Notepad.

    Note The file is located in the %ExchangeInstallPath%\bin path.
  2. Search for "EnableDataGuaranteeCheck" in Notepad.
    • If you hit the following entry, skip it, and then continue search:
      EnableDataGuaranteeCheck = true, false, true
    • If you hit the following entry, change "true" to "false":
      EnableDataGuaranteeCheck="true"
      The changed entry should read as follows:
      EnableDataGuaranteeCheck="false"
  3. Save the file.
  4. Restart the Microsoft Exchange Mailbox Replication Service.
  5. Re-create the move request.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information

Event logs when this issue occurs


Log Name: Application
Source: MSExchange Mid-Tier Storage
Event ID: 10015
Task Category: (10)
Level: Warning
Keywords: Classic
User: N/A
Description:
Active Manager Client already doing query for object 'Mailbox Database MailboxDatabase' on another thread, however this thread didn't complete in 100 msec.


Log Name: Application
Source: MSExchange Mid-Tier Storage
Event ID: 10012
Task Category: (10)
Level: Error
Keywords: Classic
User: N/A
Description:
Throttling for database 887f8adb-1e98-4b6d-99f8-1542a630ab6c cannot be checked, because database was not found in active directory.


Properties

Article ID: 3037077 - Last Review: 07/14/2015 17:09:00 - Revision: 2.0

Microsoft Exchange Server 2013 Enterprise, Microsoft Exchange Server 2013 Standard

  • kbsurveynew kbbug kbfix kberrmsg kbexpertiseadvanced KB3037077
Feedback