Share via

Error: MigrationMRSPermanentException: Error: Could not create folder Archive. --> MapiExceptionCollision

Anonymous
2017-02-05T23:56:00+00:00

I created a cutover migration that has been running fine with no failures, all accounts had either completed or synced status, and then a few days later during incrementals I received the following error on one account.  Can anyone assist on what might be the cause.

Data migrated: 5.517 GB ‎(5,923,706,961 bytes)‎ 

Migration rate: 0 B ‎(0 bytes)‎ 

Error: MigrationMRSPermanentException: Error: Could not create folder Archive. --> MapiExceptionCollision: Unable to create folder. ‎(hr=0x80040604, ec=-2147219964)‎ Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=169] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=228][latency=1] Lid: 52176 ClientVersion: 15.1.874.25 Lid: 50032 ServerVersion: 15.1.874.6025 Lid: 35180 Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropCreateFolder [28] Lid: 17082 ROP Error: 0x80040604 Lid: 25953 Lid: 21921 StoreEc: 0x80040604 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 41352 qdwParam: 0x8D44E1ADC10ECD8 Lid: 55033 dwParam: 0x0 Lid: 10786 dwParam: 0x0 Msg: 15.01.0874.025:SN2PR15MB0991 Lid: 1750 ---- Remote Context End ---- Lid: 31418 --- ROP Parse Done --- Lid: 22417 Lid: 30609 StoreEc: 0x80040604 Lid: 29073 Lid: 20369 StoreEc: 0x80040604 Lid: 63664 Lid: 40448 StoreEc: 0x80040604 

The job encountered too many transient failures (61) and is quitting. The most common failure is ObjectExistedException with the hit count 60.

2/5/2017 11:01:03 PM [SN2PR15MB0991] Fatal error ObjectExistedException has occurred.

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-02-07T09:40:15+00:00

Hi AdminIT-PA,

Thanks for your information in the private message.

I have checked all PowerShell results. I noticed that everything works well at the beginning. However, there are 7 corrupted items on 19th Jan and then the system retries many times. The system will stop if the hit count 60.

You can try deleted these corrupted items if you don’t need them. After that, create a new batch for the user. if you still need them, we suggest you move this use via pst.

If you have any concerns about it, please feel free to let me know.

Best Regards,

Erick

Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-02-09T09:53:26+00:00

    Hi AdminIT-PA,

    Do you need any further assistance?  

    Best Reagrds,

    Erick

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-02-06T09:23:09+00:00

    Hi AdminIT-PA,

    Based on the error message, may I confirm whether you enable the archive for the problematic user?

    Meantime, to better help you, I’d like to collect the following PowerShell results:

    Get-MigrationBatch -identity <name of the migration batch> |fl *status*

    Get-MigrationUserStatistics -Identity “user’s email address” -IncludeReport | FL

    Get-MigrationStatistics | fl

    To protect your privacy, I have sent you a private message to collect them. Please click on the link below to access your Private Message:

    https://answers.microsoft.com/en-us/privatemessages/list

    Best Regards,

    Erick

    Was this answer helpful?

    0 comments No comments