Migration to M365 failed

%3CLINGO-SUB%20id%3D%22lingo-sub-2402781%22%20slang%3D%22de-DE%22%3EMigration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2402781%22%20slang%3D%22de-DE%22%3E%3CP%3EHi%20Community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20migrating%20from%20an%20Exchange%20Server%202013%20via%20hybrid%20to%20Microsoft%20365.%3C%2FP%3E%3CP%3EDue%20to%20the%20small%20data%20line%20and%20the%20large%20mailboxes%2C%20the%20migration%20takes%20already%202%20weeks.%3C%2FP%3E%3CP%3EWhen%20I%20looked%20at%20Migration%20Jobs%20a%20few%20days%20ago%2C%20I%20received%20the%20following%20error%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22css-775%22%3E%3CEM%3EMigration%20rate%3A%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22css-775%22%3E%3CEM%3EError%3A%20TooManyTransientFailureRetriesPermanentException%2FStoragePermanentException%2FFolderCreationBlockedException%3A%20Error%3A%20The%20job%20encountered%20too%20many%20transient%20failures%20(82)%20and%20is%20quitting.%20The%20most%20common%20failure%20is%20StoragePermanentException%2FFolderCreationBlockedException%20with%20the%20hit%20count%2060.%20--%26gt%3B%20Exception%20encountered%20initializing%20default%20folder.%20--%26gt%3B%20Implicit%20folder%20creation%20is%20not%20allowed%20on%20this%20session.%3C%2FEM%3E%3C%2FDIV%3E%3CDIV%20class%3D%22css-775%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22css-775%22%3E%3CP%3EA%20total%20of%205%20migration%20jobs%20with%20a%20total%20of%2050%20mailboxes%20have%20been%20created.%3C%2FP%3E%3CP%3EAt%20first%20it%20was%20just%20a%20job%2C%20but%20there%20are%20now%20a%20lot%20of%20mailboxes%20with%20this%20error%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20somebody%20has%20any%20idea%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20Regards%2C%3C%2FP%3E%3CP%3EPhilipp%3C%2FP%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2402781%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Emigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2403384%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2403384%22%20slang%3D%22en-US%22%3EI%20can't%20help%20you%20here%2C%20but%20I%20have%20exactly%20the%20same%20problem%20now.%20We%20also%20use%20EX2013.%20The%20migration%20worked%20before%2C%20but%20now%20it%20doesn't%20work%20anymore.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2403648%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2403648%22%20slang%3D%22en-US%22%3EIt%20also%20started%20for%20us%20about%20last%20Friday.%20Maybe%20MS%20changed%20something%20in%20O365%20in%20the%20background.%20I%20have%20already%20opened%20a%20ticket%20with%20MS.%20Let's%20wait%20and%20see%20what%20MS%20support%20has%20to%20say%20about%20it.%20But%20I%3CBR%20%2F%3Ehave%20now%20determined%20for%20myself%20that%20the%20problem%20is%20not%20ours.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2403848%22%20slang%3D%22de-DE%22%3ESubject%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2403848%22%20slang%3D%22de-DE%22%3ESame%20problem%20here.%20Many%20of%20the%20Mailboxes%20can%20be%20migrated%20but%20not%20all%20of%20them.%3CBR%20%2F%3EAll%20Ending%20in%20the%20same%20Error%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20The%20job%20encountered%20too%20many%20transient%20failures%20(61)%20and%20is%20quitting.%20The%20most%20common%20failure%20is%20StoragePermanentException%2FFolderCreationBlockedException%20with%20the%20hit%20count%2060.%20--%26gt%3B%20Exception%20encountered%20initializing%20default%20folder.%20--%26gt%3B%20Implicit%20folder%20creation%20is%20not%20allowed%20on%20this%20session%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2404148%22%20slang%3D%22de-DE%22%3ESubject%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2404148%22%20slang%3D%22de-DE%22%3EThanks%20to%20everyone%20for%20the%20answers.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20hope%20that%20Microsoft%20gets%20this%20under%20control%20soon%20and%20that%20the%20jobs%20don't%20have%20to%20be%20created%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2406884%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2406884%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3Ewe%20have%20exactly%20the%20same%20problem%20since%20yesterday.%20There%20is%20also%20no%20message%20in%20the%20365%20status%20center%20that%20would%20explain%20it.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20it%20get%20fixed%20asap.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2407165%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2407165%22%20slang%3D%22en-US%22%3EHi%20%2C%3CBR%20%2F%3EWe%20also%20had%20same%20issue%20last%20night%20for%2030%20mailboxes%20out%2080%20mailboxes.%20The%20mailbox%20size%20is%20also%20less%20(approx%2050%20MB).%3CBR%20%2F%3EI%20did%20suspend%20and%20resume%20the%20failed%20move%20request%20couple%20of%20time%20but%20that%20did%20not%20help.%3CBR%20%2F%3EFinally%20I%20had%20removed%20the%20failed%20move%20request%20and%20created%20new%20move%20request%20and%20migration%20completed%20.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2407168%22%20slang%3D%22de-DE%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2407168%22%20slang%3D%22de-DE%22%3EHi%2C%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20I%20have%20poor%20lines%20at%20the%20customer's%20site%20and%20mailboxes%20over%2030%20GB.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20don't%20want%20to%20recreate%20the%20JObs.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20hope%20MS%20can%20get%20this%20under%20control.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2415945%22%20slang%3D%22en-US%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2415945%22%20slang%3D%22en-US%22%3EThe%20migration%20works%20for%20us%20again.%20Existing%20jobs%20can%20also%20be%20continued.%20Unfortunately%2C%20I%20noticed%20that%20the%20mailboxes%20are%20no%20longer%20properly%20synchronized%20-%20in%20EXO%20there%20were%20still%20mails%20that%20had%20already%20been%20deleted%20on-premises.%20So%20I%20recreated%20the%20batches%20to%20be%20on%20the%20safe%20side.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2429533%22%20slang%3D%22de-DE%22%3ERe%3A%20Migration%20to%20M365%20failed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2429533%22%20slang%3D%22de-DE%22%3EThanks%20for%20your%20information.%3CBR%20%2F%3E%3CBR%20%2F%3ESome%20batches%20are%20now%20working%20again%20for%20me.%20However%2C%20I%20cannot%20say%20yet%20whether%20items%20were%20not%20synchronized%20correctly.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20migration%20will%20be%20completed%20over%20the%20weekend.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20addition%2C%20however%2C%20I%20had%20to%20create%20a%20new%20batch%20with%20around%208%20mailboxes%2C%20which%20always%20resulted%20in%20an%20error%3A%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20SourceMailboxAlreadyBeingMovedPermanentException%2FFolderSaveException%2FPropertyErrorException%3A%20Error%3A%20Couldn't%20switch%20the%20mailbox%20into%20Sync%20Source%20mode.%20This%20could%20be%20because%20of%20one%20of%20the%20following%20reasons%3A%20Another%20administrator%20is%20currently%20moving%20the%20mailbox.%20The%20mailbox%20is%20locked.%20The%20Microsoft%20Exchange%20Mailbox%20Replication%20service%20(MRS)%20doesn't%20have%20the%20correct%20permissions.%20Network%20errors%20are%20preventing%20MRS%20from%20cleanly%20closing%20its%20session%20with%20the%20Mailbox%20server.%20If%20this%20is%20the%20case%2C%20MRS%20may%20continue%20to%20encounter%20this%20error%20for%20up%20to%202%20hours%20-%20this%20duration%20is%20controlled%20by%20the%20TCP%20KeepAlive%20settings%20on%20the%20Mailbox%20server.%20Wait%20for%20the%20mailbox%20to%20be%20released%20before%20attempting%20to%20move%20this%20mailbox%20again.%20--%26gt%3B%20An%20error%20occurred%20while%20saving%20the%20changes%20on%20the%20folder%20%22TwAAAAAbVfogqmYRzZvIAKoAL8RaCQBIAERSLUFEUy0wMS5kcnVtYWcubG9jYWwAIds5z5U8502Q9yVsmRyuHY8f4TDVWERIhZ3deG1cAzb%2F%22.%20Error%20details%3A%20Failed%2C%20Property%3A%20%5B0x66180003%5D%20InTransitStatus%2C%20PropertyErrorCode%3A%20AccessDenied%2C%20PropertyErrorDescription%3A%20''.%20--%26gt%3B%20Property%3A%20%5B0x66180003%5D%20InTransitStatus%2C%20PropertyErrorCode%3A%20System.Runtime.Serialization.TypeLoadExceptionHolder%2C%20PropertyErrorDescription%3A%20.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20hope%20they%20work%20again%20after%20a%20new%20creation.%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20a%20day%20of%20waiting%2C%20the%20batches%20still%20did%20not%20work.%3CBR%20%2F%3E%3CBR%20%2F%3EGreetings%2C%20%3CBR%20%2F%3E%20Phil%3C%2FLINGO-BODY%3E
Contributor

Hi Community,

 

I am migrating from an Exchange Server 2013 via hybrid to Microsoft 365.

Due to the small data line and the large mailboxes, the migration takes already 2 weeks.

When I looked at Migration Jobs a few days ago, I received the following error message:

 

Migration rate:
Error: TooManyTransientFailureRetriesPermanentException/StoragePermanentException/FolderCreationBlockedException: Error: The job encountered too many transient failures (82) and is quitting. The most common failure is StoragePermanentException/FolderCreationBlockedException with the hit count 60. --> Exception encountered initializing default folder. --> Implicit folder creation is not allowed on this session.
 

A total of 5 migration jobs with a total of 50 mailboxes have been created.

At first it was just a job, but there are now a lot of mailboxes with this error message.

 

Does somebody has any idea?

Thanks.

Best Regards,

Philipp

 

11 Replies
I can't help you here, but I have exactly the same problem now. We also use EX2013. The migration worked before, but now it doesn't work anymore.

Hi,

I have since Friday the same problem and have no idea what has changed since then

 

It also started for us about last Friday. Maybe MS changed something in O365 in the background. I have already opened a ticket with MS. Let's wait and see what MS support has to say about it. But I
have now determined for myself that the problem is not ours.
Same Problem here. Many of the Mailboxes can be migrated but not all of them.
All Ending in the same Error

The job encountered too many transient failures (61) and is quitting. The most common failure is StoragePermanentException/FolderCreationBlockedException with the hit count 60. --> Exception encountered initializing default folder. --> Implicit folder creation is not allowed on this session
Thanks to everyone for the answers.

I hope that Microsoft gets this under control soon and that the jobs don't have to be created again.
Hi,

we have exactly the same problem since yesterday. There is also no message in the 365 status center that would explain it.

Hope it get fixed asap.
Hi ,
We also had same issue last night for 30 mailboxes out 80 mailboxes. The mailbox size is also less (approx 50 MB).
I did suspend and resume the failed move request couple of time but that did not help.
Finally I had removed the failed move request and created new move request and migration completed .
Hi,

I have poor lines at the customer's site and mailboxes over 30 GB.

I don't want to recreate the JObs.

I hope MS can get this under control.
The migration works for us again. Existing jobs can also be continued. Unfortunately, I noticed that the mailboxes are no longer properly synchronized - in EXO there were still mails that had already been deleted on-premises. So I recreated the batches to be on the safe side.
Thanks for your information.

Some batches are now working again for me. However, I cannot say yet whether items were not synchronized correctly.

The migration will be completed over the weekend.

In addition, however, I had to create a new batch with around 8 mailboxes, which always resulted in an error:

SourceMailboxAlreadyBeingMovedPermanentException/FolderSaveException/PropertyErrorException: Error: Couldn't switch the mailbox into Sync Source mode. This could be because of one of the following reasons: Another administrator is currently moving the mailbox. The mailbox is locked. The Microsoft Exchange Mailbox Replication service (MRS) doesn't have the correct permissions. Network errors are preventing MRS from cleanly closing its session with the Mailbox server. If this is the case, MRS may continue to encounter this error for up to 2 hours - this duration is controlled by the TCP KeepAlive settings on the Mailbox server. Wait for the mailbox to be released before attempting to move this mailbox again. --> An error occurred while saving the changes on the folder "TwAAAAAbVfogqmYRzZvIAKoAL8RaCQBIAERSLUFEUy0wMS5kcnVtYWcubG9jYWwAIds5z5U8502Q9yVsmRyuHY8f4TDVWERIhZ3deG1cAzb/". Error details: Failed, Eigenschaft: [0x66180003] InTransitStatus, PropertyErrorCode: AccessDenied, PropertyErrorDescription: ''. --> Property: [0x66180003] InTransitStatus, PropertyErrorCode: System.Runtime.Serialization.TypeLoadExceptionHolder, PropertyErrorDescription: .

I hope they work again after a new creation.

After a day of waiting, the batches still did not work.

Greetings,
Phil
Edit:

After e restart of the Exchange Server, the new Batchs works.

Phil