Forum Discussion
Phil123
Jun 01, 2021Brass Contributor
Migration to M365 failed
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 ...
Phil123
Jun 02, 2021Brass Contributor
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.
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.
Thomas35
Jun 04, 2021Copper Contributor
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.
- Phil123Jun 09, 2021Brass ContributorThanks 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- Phil123Jun 10, 2021Brass ContributorEdit:
After e restart of the Exchange Server, the new Batchs works.
Phil