This is a re-posting of a Erin’s IT blogpost
This issue I have been fighting with for a couple of days, thinking that something was actually wrong with the migration. But it turns out its a cosmetic issue with some Office 365 tenants. In the downloaded report you will see:
Couldn’t find a request that matches the information provided. Reason: No such request exists in the specified index. –> Couldn’t find a request that matches the information provided. Reason: No such request exists in the specified index.
However, it seems that everything is, in fact, OK… though I am still working on confirming this for certain with Microsoft.
Erin’s IT original Post
Problem – Running a Microsoft cutover migration fails with following error:
MigrationTransientException: No such request exists in the specified index. –> No such request exists in the specified index.
Mitigation – This issue is just a cosmetic issue in the reporting part, which will be resolved in future releases, in the next 1-2 weeks.
The problem is related to looking at the underlying data move – the Migration service is unable to retrieve it, or manage it in any way (Start, Stop, Remove, Set), so it assumes that it has failed. Even so, the migration of data is working as expected.
You may run, from time to time, the following commands in order to compare the values, in order to ensure that indeed the data is migrated:
Get-MailboxStatistics <mailbox> -debug | fl
Get-MailboxFolderStatistics <mailbox> -IncludeOldestAndNewestItems -IncludeAnalysis -Debug | fl
Expected resolution – June 2016
Cause – Unknown, affects seemingly random tenants.
