Office 365 Migration Failure: O365 to On-Prem
Posted on October 19, 2016 by Richard Brynteson in Exchange Server
Everyone once in a while I step outside the Lync/Skype for Business world and do some fiddling around with Exchange. In my home lab, I setup Office 365 integration with my test tenant. I’ve been doing all sorts of migrations from Exchange 2013 On-Premise to Office 365 and had no problems. Today, I wanted to move one of those mailboxes back on-prem and it failed.
While playing around on the Exchange Online, I ran this command to get log information from the O365 side:
Get-MigrationUserStatistics -IncludeReport -Identity firstname.lastname@example.org | fl
When running this, I found this error:
ERROR MESSAGE: Transient error ResourceUnhealthyException has occurred. The system will retry.
While doing multiple searches I couldn’t find any particular fix to this issue. While searching for transient error message, I found people having issues with their Exchange DAGs. Everyone led to running this command:
This lead to two different possible solutions. I tried this solution first:
- Create a new Active Directory group that is named “ContentSubmitters”. Right click on the group, select Security tab and then grant Admistrators and NetworkService full access to the group.
- Force or wait for Active Directory replication.
Restart the following services:
- Microsoft Exchange Search
- Microsoft Exchange Search Host Controller
I did this, waited for a long time and it didn’t seem to fix the issue. So I turned to the second solution for a Failed ContentIndexState and that is to delete the full-text index catalog directory. Since I’m an Exchange newb I did some searching to make sure I didn’t screw up anything.
The steps were easy.
- Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller.
Go to the directory where the Exchange Database Index is in a failed state. Find the folder GUID and delete this folder. Personally, I moved mine to another drive just to make sure I had a copy but I’m sure I didn’t need to.
- Start the Microsoft Exchange Search Host Controller. Wait a few minutes and then start the Microsoft Exchange Search service.
After these steps, the ContentIndexState changes from Failed to Crawling: <a href="https://i0.wp.com/masteringlync.gcmtotalsolutions.com/wp-content/uploads/sites/2/2016/10/4.png" rel="attachment wp-att-1306"><img class="alignnone wp-image-1306" src="https://i0.wp.com/masteringlync.gcmtotalsolutions.com/wp-content/uploads/sites/2/2016/10/4.png?resize=602%2C71&ssl=1" alt="4" width="602" height="71" srcset="https://i2.wp.com/masteringlync.com/wp-content/uploads/sites/2/2016/10/4.png?w=966&ssl=1 966w, https://i2.wp.com/masteringlync.com/wp-content/uploads/sites/2/2016/10/4.png?resize=300%2C35&ssl=1 300w, https://i2.wp.com/masteringlync.com/wp-content/uploads/sites/2/2016/10/4.png?resize=768%2C91&ssl=1 768w" sizes="(max-width: 602px) 100vw, 602px" data-recalc-dims="1" /></a> I than went back to the Office 365 Portal and attempted my mailbox migration and my migration from Office 365 to On-Prem completed successfully.