Share via

Error:MigrationTransientException:No such request in specified index. -->No such request in specified index.

Anonymous
2017-07-12T20:23:45+00:00

Hi Everyone,

As of late I am getting the above errors when doing a staged migration from E2K7 to Exchange Online. It use to happen when the mailboxes were 10GB and up but now it just errors out when migrating a new mailbox. I have checked if we have enough licenses when migrating the users, the spelling in the csv file that you need to upload, verified my ISP is not throttling my connection, and searched countless web sites to see if my problem is out there but lucky me it is just my scenario.

Any help will be greatly appreciated.

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2017-07-18T17:40:04+00:00

Hi Mark,

It turns out that this was my problem.

Was this answer helpful?

0 comments No comments

5 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-07-18T15:01:45+00:00

    Hi Ryan,

    Any update will be appreciated.

    Regards,

    Alan

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-07-16T15:09:57+00:00

    Hi Ryan,

    Please provide the screenshot and the output of the cmdlet (you can also upload a screenshot about it) in the PM.

    Regards,

    Alan

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-07-14T19:20:26+00:00

    Alan,

    I shot you a PM. Please advise.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-07-13T06:23:29+00:00

    Hi Ryan,

    For your situation, please try the following methods to see if it works:

    1. Delete the old migration batch.
    2. Start a new migration batch to re-perform the migration with the new mailbox. For the Staged Migration, you can refer tohttps://support.office.com/en-us/article/Perform-a-staged-migration-of-email-to-Office-365-83bc0b69-de47-4cc4-a57d-47e478e4894e
    3. Change another network environment (differed from the one having the problem).

    If the issue persists, I’d like to collect the following information for further trobelshooting:

    1. The screenshot about the migration in Office 365 Exchange Admin Center (EAC).
    2. The Output of **Get-MigrationUserStatistics -Identity ****@corp.contoso.com -IncludeReport | FL Status,Error,Report  ( Note: ******@contoso.com stands for the affected/failed on-premises mailbox. Before running the PowerShell cmdlet, it needs to connect to Exchange Online PowerShellvia an admin credential.)

    For protecting your privacy, I suggest you provide the above information in the Private Message (PM).

    Regards,

    Alan

    Was this answer helpful?

    0 comments No comments