I'm in the process of moving mailboxes from Exchange 2010 to Exchange 2013, the major of the mailboxes have moved successfully, however I did not anticipate the additional space required by Exchange 2013 and ran out of disk space during the mailbox move, and some mailboxes did not move successfully.

I have since added additional space but can't seem to get the remaining mailboxes to sync.

I have tried :

Rebooting

Clearing out migration batches and recreating

Stopping and resuming batches.

I see nothing helpful in the Migration log files.

2013-05-20T23:59:57.904Z,14,MigrationServicelet,Information,",827890ff-522d-4c13-9f42-96fbfefb57f4,,","Job type ExchangeLocalMove, status SyncStarting, result Working, length 0.2724593, job :827890ff-522d-4c13-9f42-96fbfefb57f4:ExchangeLocalMove:Staged:4::SyncStarting:2013-05-17 2:59:12 PM::"

When I download the report for one of the users I see this, but don't know what it means :

The job is currently stalled due to 'Content Indexing' lagging behind on resource 'CiAgeOfLastNotification(Mailbox Database 2065686096)'

For one of the other users the downloaded report only shows :

2013-05-16 2:11:18 PM  '' created move re

Hi

I found the similar issue. Create a new AD group named ContentSubmitters and grant Admistrators and NetworkService full access to it, this method fixed it, you can try it.

http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/1562fc53-2147-406e-af60-a132948dd421

If you have any feedback on our support, please click here

Any update ?

If you have any feedback on our support, please clickhere

I have to fix the content index first and create the ContentSubmitters group, once the Content Index completed it's rebuild then syncing started to work again.

I had already created the contentsubmitters and it helped with the speed of the mailbox moves.  We have a SMB with >100 users and everything was working great, migrating from 2007 to 2013.  If I had it to do over, maybe it would have been better to go to 2010 on a 2008 R2 box but decided to jsut go straight to 2013 on a 2012 R2 server.  But the one thing I REALLY wish I had to do over again is to allocate about 3 times more space to the drive that was to hold the mailbox database.  Everything was working so well until a mailbox was being moved - a batch of several, I was doing maybe 5 at a time for the larger mailboxes - the disk filled up.  Also, before I realized what was going on, I ran some cmdlets thinking my receive connectors weren't right.  I recovered the database - at first it would not mount at all... but after eseutil /r and /p (and allocating more disk space) I could mount the database and open the mailboxes.  But from then on, nothing is being received and if you send, it goes to sent items - doesn't hang in outbox, but never goes anyhere except into a queue.  I have MS support working on it and it's been escalated to the top. If they fix it I will try to post any helpful information I can learn from it. But one lesson - I will read the planning and preparations documentation thoroughly from now on.

Oh, and also, I keep getting this message in the ECP when navigating to the Recipients>migration applet:

Cannot open mailbox /o=<Organization>/ou=Exchange Asministrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/CN=<yourExchangeserver>/cn=Microsoft System Attendant.

If you did the same thing, (and didn't hang yourself or jump in front of a speeding locomotive), you are stronger than I.  Not that I have taken the path of the Samurai network admin or anything....

And if you were able to fix it, I am impressed and would love to know how you fixed this.

Thanks and best,

Sam 

I have successfully migrated a number of mailboxes from exchange 2010 to 2013, but the last three are stuck with statusdetail:StalledDueToCI

Is this Content Indexing something that we just have to wait and let finish, or is it something that needs to be addressed?

I did try creating the Group "contentsubmitters" with the permissions mentioned here, but that has not helped.

• Edited by ken_at_novus 9 hours 5 minutes ago

I have successfully migrated a number of mailboxes from exchange 2010 to 2013, but the last three are stuck with statusdetail:StalledDueToCI

Is this Content Indexing something that we just have to wait and let finish, or is it something that needs to be addressed?

I did try creating the Group "contentsubmitters" with the permissions mentioned here, but that has not helped.

• Edited by ken_at_novus Thursday, March 12, 2015 10:15 PM

I have successfully migrated a number of mailboxes from exchange 2010 to 2013, but the last three are stuck with statusdetail:StalledDueToCI

Is this Content Indexing something that we just have to wait and let finish, or is it something that needs to be addressed?

I did try creating the Group "contentsubmitters" with the permissions mentioned here, but that has not helped.

• Edited by ken_at_novus Thursday, March 12, 2015 10:15 PM

you can turn off the Content Indexing and then try to move.

EMS:

  Set-MailboxDatabase YourMailboxDatabase -IndexEnabled:$False

then restart the services:

  Microsoft Exchange Search 
  Microsoft Exchange Search Host Controller
  Microsoft Exchange Mailbox Replication

now you can try to move

then  Set-MailboxDatabase YourMailboxDatabase -IndexEnabled:$True

• Proposed as answer by ken_at_novus 15 hours 49 minutes ago

Yes, that worked. The last few stalled mailboxes transferred after turning off content indexing. It is not clear to me why content indexing would cause this problem, perhaps Microsoft could issue an update to resolve this because I am sure I am not the only person to experience this problem.

If it helps diagnose... these were Exchange 2010 mailboxes that had recently been migrated from Exchange 2003. Most of the mailboxes then migrated to Exchange 2013, but three had problems. They were the largest mailboxes, 5-7 GB 

Thanks.

you can turn off the Content Indexing and then try to move.

EMS:

  Set-MailboxDatabase YourMailboxDatabase -IndexEnabled:$False

then restart the services:

  Microsoft Exchange Search 
  Microsoft Exchange Search Host Controller
  Microsoft Exchange Mailbox Replication

now you can try to move

then  Set-MailboxDatabase YourMailboxDatabase -IndexEnabled:$True

• Proposed as answer by ken_at_novus Monday, March 23, 2015 3:33 PM

In case this helps someone else...

The first time I tried to migrate an account it failed with an error, so I went to the properties of the account and the permissions, clicked advanced then clicked the bottom check box.

Then I tried 4 more times to migrate the account, no luck.  Each time I was trying it would show 0's and send the completion email but didnt actually move. Then I noticed on the original job (from the first migration attempt) if I clicked on the batch job it gave me the option to resume, so I tried it.   It then worked.   

So the original job failed, but was still holding on to it, so any other new job couldnt use it.

JC