
This was run to get more info on the move request.

Running Get-MoveRequestStatistics and including a full report (with -IncludeReport) shows in part the below. In the above I have highlighted some of the errors I was seeing – with the “could not create folder” message, the first indicator is that I have too many folders to migrate or I have a corrupt mailbox.

(hr=0x80004005, ec=1253) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned Lid: 52176 ClientVersion. –> MapiExceptionFolderHierarch圜hildrenCountQuotaExceeded: Unable to create folder. I was moving some mailboxes to Exchange Online when I came across the following error in the migration batch results:ĭata migrated: 18.18 MB (19,060,890 bytes)Įrror: MigrationMRSPermanentException: Error: Could not create folder 2288. But what happens if you have a mailbox with less than this number of folders and it still fails for this same reason? This is the problem, with resolution, I outline below. If you try and migrate a mailbox with more than this number of folders then it will fail – and that would be expected. Exchange Online has a limit of 10,000 folders within a mailbox.
