I am migrating 1600 mailboxes from Exchange 2007 to Exchange 2013, over 700 have moved fine, but 1 mailbox fails repeatedly. 

When I run the migration in ecp it says the migration status is complete, but it also says that 0 mailboxes were synced, 0 were finalized and 0 failed. I also receive an email saying it completed successfully. The only thing, apart from the fact it says it worked when it didn't, is that the Total column changes from 1 to 0 while it is in Syncing status.

I'm confused, why is this not working? What do I need to do to fix it?

• Edited by GADavies Thursday, December 18, 2014 2:19 AM additional information

Hi GADavies,

*Ensure you are clearing any old Migration Batch or Move Requests.

Use below to list existing batches, which might contain earlier move attempted users.

Get-MigrationBatch 

Get-MigrationUserStatistics -Identity BatchName -Status | Format-List

*See if restarting these services on each participating server helps:

When you use move request to move mailboxes, the move requests are processed by the following two services:
Microsoft Exchange Mailbox Replication service
Microsoft Exchange Mailbox Replication Proxy

*Check for any eventlogs indicating any issues on the servers, Get-ServerHealth -Server <Server01>, Test-ServiceHealth

Get-MailboxServer | Test-MRSHealth

Try this:

1. Start Active Directory Users and Computers.
2. Click View, and then click to enable Advanced Features.
3. Right-click the object where you want to change the Exchange Server permissions, and then click Properties.
   
   Note You can change permissions against a user, an organizational unit, or a domain.
4. On the Security tab, click Advanced.
5. Click Add, type Exchange Servers, and then click OK.
6. In the Apply to box, click Descendant msExchActiveSyncDevices objects.
7. Under Permissions, click to enable Modify Permissions.
8. Click OK three times.

Thanks Lionardo,

That fixed it

Great that it worked out. But not able to understand how its linked with ActiveSync permissions.

http://support.microsoft.com/kb/2579075

I don't get it either, but after reading the post that ultimately fixed the issue I checked the users ActiveSync settings. ActiveSync was enabled and Exchange 2007 had the Manage mobile device link listed (usually only seen if there is or has been a device connected), but when I clicked it there was no device listed, no first sync time, last sync time, policy date or anything.

I have a feeling Lionardo had seen this before, and to be honest I don't mind what fixed it as long as I could move the mailbox to the new Exchange environment I am migrating everybody to

Good advice, but it was just this 1 mailbox that was causing issues. It was originally part of a csv batch migration where all other mailboxes moved fine, other subsequent batches also went through fine.

As soon as migrations complete I remove the jobs, we are moving our entire Exchange setup to 2013 from 2007 so there are a lot of migration jobs being run and leaving old ones there makes it difficult to keep track.

Stopping and restarting the services was not something I would do in this situation, if other migrations were failing I would have, but just 1 mailbox failing out of over 250 moved in the last 2 days does not equate to a problem with the services.

I had the same problem with this error moving mailboxes from Exchange2007 to Exchange2013.

I manage to resolve this by running these Exchange Management Shell commands:

Get-moverequest -identity 'mailbox name'   (showed me a failed status for this mailbox)

Remove-moverequest -identity 'mailbox name'  (clears out the move migration for this mailbox)

New-moverequest -identity 'mailbox name' -baditemlimit '100' -targetdatabase 'Mailbox Database name'  (runs the move via command line instead of via EAC and ignoring up to 100 baditems)

Hope this helps others.

Hi Khaily,

Appreciate for taking your time to update here.

Same thing here.

The only difference is that I was doing a local migration (within same server) on Exchange 2013. In the first migration batch I forgot to select the target DB and the mailbox ended up going to the wrong DB. When I created a new batch, it would complete the task but not move the mailbox.

Deleting the first migration batch fixed the issue.