Share via

Error while migrating a large mailbox

Anonymous
2017-01-26T15:57:56+00:00

Having an issue with a large mailbox. This support thread describes the issue. Early posts say “escalate this issue to our Engineering team.” Later posts say the issue is fixed.

Report: 1/25/2017 6:38:36 PM [BL2PR16MB0962] Setting up ISInteg repair run up front for this mailbox since it's a large mailbox.

"Primary mailbox size = 12425668622, Archive mailbox size = 0, Large mailbox size threshold config value = 10737418240

#it gets started fine

1/25/2017 6:45:13 PM [BLUPR16MB0290] Copy progress: 312/34903 messages, 92.52 MB (97,012,650 bytes)/11.57 GB (12,426,515,249 bytes), 9/77 folders completed.

#but errors out before completion

1/25/2017 11:36:57 PM [BLUPR16MB0290] Copy progress: 32157/34920 messages, 11.33 GB (12,170,578,618 bytes)/11.57 GB (12,426,643,294 bytes), 20/77 folders completed.

1/25/2017 11:41:31 PM [BLUPR16MB0290] Transient error CommunicationErrorTransientException has occurred. The system will retry (2/820).

1/26/2017 12:15:08 AM [BLUPR16MB0290] The Microsoft Exchange Mailbox Replication service

'BLUPR16MB0290.namprd16.prod.outlook.com' (15.1.860.21 caps:07FFFF) is examining the request.

1/26/2017 12:15:11 AM [BLUPR16MB0290] The job encountered too many transient failures (62) and is quitting. The most common

failure is EndpointNotFoundTransientException with the hit count 58.

1/26/2017 12:15:11 AM [BLUPR16MB0290] Fatal error EndpointNotFoundTransientException 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

8 answers

Sort by: Most helpful
  1. Anonymous
    2017-02-02T14:20:27+00:00

    Hi Vmann_40,

    Any updates?

    Thanks,

    Gary

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-01-31T15:27:25+00:00

    Hi Vmann_40,

    First, run a Windows PowerShell cmdlet “Get-Recipient ******@domain.com on this user in on-premises and Exchange Online separately.

    If the “RecipientType of this user is “MailUser” in on-premises and “UserMailbox” in Exchange online, it means the mailbox has been migrated to Exchange Online successfully. According to “1/25/2017 11:36:57 PM [BLUPR16MB0290] Copy progress: 32157/34920 messages, 11.33 GB (12,170,578,618 bytes)/11.57 GB (12,426,643,294 bytes), 20/77 folders completed”, please run cmdlet “***Get-MailboxStatistics –Identity ***@domain.com | fl displayname, totalitemsize, itemcoun” in Exchange Online to check if the size of this user’s email data is 11.33 GB.

    Moreover, please provide the entire migration log via the private message.

    Thanks,

    Gary

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-01-30T16:14:39+00:00

    Gary,

    We are hybrid, however we do not have Microsoft TMG deployed. This is the first migration to have this issue, and also the first one of this size (greater than 10 GB).

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-01-29T14:49:31+00:00

    Hi Vmann_40,

    Have you referred to my reply? Any updates?

    Thanks,

    Gary

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-01-27T09:24:55+00:00

    Hi Vmann_40,

    Given the error message you provided, I’d like to confirm whether you are doing a hybrid deployment of Microsoft Exchange Online in Microsoft Office 365 and on-premises Microsoft Exchange Server and you receive the error message when you move mailboxes from your on-premises environment to Office 365.

    If yes, this issue may occur if the on-premises Microsoft Forefront Threat Management Gateway (TMG) server blocks HTTP requests from servers in the Office 365 environment. This occurs because of the flood mitigation feature in the forefront TMG. This mechanism helps lessen flood attacks. To confirm that this is the issue that you are experiencing, examine the alerts that are displayed in the Forefront TMG management console. To do this, follow these steps:

    1. Open the Forefront TMG Management console.
    2. In the tree, click Monitoring, and then click the Alerts tab.
    3. Check whether a warning that contains the following text is displayed:

    The number of HTTP requests per minute from the source IP address IPAddress exceeded the configured limit. Forefront TMG will block new HTTP requests sent from this IP address.

    If such a warning is displayed, you are experiencing this issue.

    To resolve this issue, configure flood mitigation settings in Forefront TMG to increase the custom limit for the maximum number of HTTP requests per minute. To do this, please refer to “Solution” part of this article:

    https://support.microsoft.com/en-us/help/2654376/error-message-when-you-move-mailboxes-from-an-on-premises-environment-to-office-365-mailbox-move-to-the-cloud-fail-with-error

    Meanwhile, the support thread link could not be opened, can you provide the link again?

    Thanks,

    Gary

    Was this answer helpful?

    0 comments No comments