Hello,

I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?

T

Have you looked at the report?

Get-MoveRequestStatistics -Identity "Name" -IncludeReport | FL Report

Yes,
Here's the output:

Report : 1/4/2014 5:26:19 PM [exch13] '' created move request.

it stays like this forever. What components are being used for the actual mailbox

Yes, absolutely. Restart to services multiple times.

What components are being used for the actual mailbox move? Services, ports, etc?

Here's a similar thread; perhaps it might help.

http://social.technet.microsoft.com/Forums/exchange/en-US/cd815709-65ac-438b-802c-4fd37ddda81b/exchange-2010-2013-mailbox-move-syncing-with-no-progress-stalled?forum=exchangesvrdeploy

Have increased diagnostic logging for mailbox move:

Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Mailbox Move" -level high
Set-EventLogLevel -Identity "MSExchange Mailbox Replication\Service " -level high

Getting the following exception:

2014-01-05T03:07:29.678Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5739226, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:admin@domain.loc:SyncStarting:1/5/2014 1:26:13 AM::"
2014-01-05T03:07:34.732Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:35.372Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.5744619, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:admin@domain.loc:SyncStarting:1/5/2014 1:26:13 AM::"
2014-01-05T03:07:40.427Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:41.066Z,15,MigrationServicelet,Information,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.589772, job 1:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:ExchangeLocalMove:Staged:4:admin@domain.loc:SyncStarting:1/5/2014 1:26:13 AM::"
2014-01-05T03:07:46.136Z,15,MigrationServicelet,Information,",,",ProcessCacheEntry: beginning processing /o=test/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=b31d04e95d224880be9d3330b66dddef-Migra
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Error,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,test@domain.loc","MigrationJobItem.SetTransientError: job a19d0cec-1b9b-472f-b849-5cd6f8a065d1:test@domain.loc:Syncing,   at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String commandString, Exception ex)    at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions)    at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand command, ICollection`1 ignoreExceptions)    at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId)    at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId subscriptionId)    at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2()    at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory)    at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession, IConfigDataProvider globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate errorHandler)    at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord()    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"
2014-01-05T03:07:46.745Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,test@domain.loc",Set TransientError: Syncing:1/5/2014 2:41:56 AM:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'. --> Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.: count 10 original time 01/05/2014 02:41:56
2014-01-05T03:07:46.760Z,15,MigrationServicelet,Warning,",a19d0cec-1b9b-472f-b849-5cd6f8a065d1,1,test@domain.loc","NotifyOfTransientException:   at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String commandString, Exception ex)    at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions)    at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand command, ICollection`1 ignoreExceptions)    at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionSnapshot(ISubscriptionId subscriptionId)    at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.RetrieveSubscriptionStatus(ISubscriptionId subscriptionId)    at Microsoft.Exchange.Migration.SubscriptionHandlerBase.<>c__DisplayClass3.<GetJobItemsForActiveSubscriptionCheck>b__2()    at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)|transient error occurred for job items:a19d0cec-1b9b-472f-b849-5cd6f8a065d1:test@domain.loc:Syncing||Microsoft.Exchange.Data.Storage.Management.MigrationTransientException|Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|InnerException:ManagementObjectNotFoundException:Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: Couldn't find a move request that corresponds to the specified identity 'domain.loc/Admins/test'.    at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory)    at Microsoft.Exchange.Configuration.Tasks.RecipientTaskHelper.ResolveDataObject[TDataObject](IConfigDataProvider dataSession, IConfigDataProvider globalCatalogSession, ADServerSettings serverSettings, IIdentityParameter identity, ObjectId rootId, OptionalIdentityData optionalData, String domainController, CategorizedGetDataObjectDelegate getDataObjectHandler, TaskVerboseLoggingDelegate logHandler, ErrorLoggerDelegate errorHandler)    at Microsoft.Exchange.Management.RecipientTasks.GetMoveRequestStatistics.InternalProcessRecord()    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|"

Those MRS errors ...

Perhaps this: http://support.microsoft.com/kb/2669562/en-us ???

I had similar situation some time back but then it was move from 2007 to 2010. I was trying to move while in Console to exchange 2007 and it was either giving error or failing. So just as a work around I tried while in Exchange 2010 console and remote move which completed without error.

I know this might not be the solution for your question but no harm trying as a workaround.

tnx

Thanks for the input. I'm performing the command from Exchange 2013. As much as I know, it's the only Microsoft-supported way.

There's no Exchange Online involved in this scenario, only 2007 and 2013.
I was referring to:

http://technet.microsoft.com/en-us/library/jj150543(v=exchg.150).aspx

"In Exchange 2013 you must move mailboxes between Exchange 2007 and Exchange 2010 and Exchange 2013 from the Exchange 2013 admin center (EAC) and the Exchange Management Shell."

Similar issue:

http://social.technet.microsoft.com/Forums/en-US/269e6795-d7af-4a18-9b0c-2e16fb80a2c3/unable-to-migrate-users-with-archives?forum=exchangesvrdeploy

Yes, that would be correct.

I'm afraid that I can't make any sense of the report you posted so all I can suggest is to open a support ticket with Microsoft.

Ended up resolving it by creating a new database and moved mailboxes that way. Either new DB on Exchange 2007 or/and new DB on Exchange 2013 did the trick.

Very weird though.

Thanks for your help.

Hi,

Thanks for your response.

It's great to hear the good news.

Best regards,
Amy

I also had this issue.

I created a new database on the Exchange 2013 server.

I did not need to create a new database on the old Exchange 2007 server.

Perhaps it is of interest.

I found in such a case, that the target database had inconsistent copies. I needed to tell through EAC to complete the transfer. Once this was done, I could start new batches for mailbox migration.

Reason for the inconsistent copies was, that the log partition ran full and brought the databases down.

Cheers Franz

• Proposed as answer by MPO79 Tuesday, January 27, 2015 2:59 PM
• Unproposed as answer by MPO79 Tuesday, January 27, 2015 2:59 PM

I also had this issue.
Exchange 2013 CU7.
Mailbox moverequests stuck in queue.

Service restarts didnt resolve the issue.
There are no eventlog entries.

The reason for the issue in my case:

I increased simultaneous Move-Requests in the the MsExchangeMailboxReplication.exe.config file before.

After undoing these changes the moverequests working again.

Hello,

i have same situation like frakel1.

Reason for the inconsistent copies was, that the log partition ran full and brought the databases down in target sever.

Now i have 3 mailbox in Relinquished status, with migration status in progress.

I tried to restart replication Mialbox service in source server (ex 2007 SPe ru 16) and target server (ex 2013 cu8) but problem remain. I have also stopped migration job and resumed migration job but i ave always stutus Relinquished.

It is safe to remove migration job that move all 3 mailbox and recreate another to resolve this problem?

Thanks in adavance for your support.