Share via

Problem on completion (on 95%) when performing migration from O365 to On-Premise. No TMG/ISA.

Anonymous
2016-06-08T03:51:41+00:00

Dear colleagues,

We have recently configured hybrid in our environment. Migration to O365 works all fine, problem is when we try to move mailbox back.

Errors what I see in:

Get-MoveRequest acobjtestuser | Get-MoveRequestStatistics -IncludeReport

FailureCode                              : -2146233088

FailureType                              : CommunicationErrorTransientException

FailureSide                              : Target

Message                                  : Error: The call to 'owa.domain.com/.../mrsproxy.svc <ExchangeHybridServerName>.domain.com (15.1.396.30 ca

                                           ps:2FFFBF7FFFFFCB07FFFF)' failed. Error details: Exception from HRESULT: 0x8144D018. --> Exception from HRESULT: 0x8

                                           144D018

It is trying 700 times after reaching 95% (when completing), after that it is crashing, and at the and of move report I got:

2016-06-07 17:36:35 [VI1PR0101MB1935] Stage: FinalIncrementalSync. Percent complete: 95.

                                           2016-06-07 17:36:35 [VI1PR0101MB1935] SessionStatistics updated.

                                           2016-06-07 17:36:35 [VI1PR0101MB1935] Verifying mailbox contents...

                                           2016-06-07 17:36:37 [VI1PR0101MB1935] The job encountered too many transient failures (701) and is quitting. The mos

                                           t common failure is CommunicationErrorTransientException with the hit count 60.

                                           2016-06-07 17:36:37 [VI1PR0101MB1935] Fatal error CommunicationErrorTransientException has occurred.

RequestExpiryTimestamp                   : 2116-05-13 20:52:32

ObjectState                              : New

Command:

Get-MigrationUser  acobjtestuser | Get-MigrationUserStatistics -IncludeReport

Gives me:

Status                           : CompletionFailed

StatusSummary                    : Failed

LastSubscriptionCheckTime        : 2016-06-07 17:37:05

TotalQueuedDuration              : 00:00:09.3881506

TotalInProgressDuration          : 11:14:11.1011233

TotalSyncedDuration              : 02:03:12.8943903

TotalStalledDuration             : 21:14:11.0368122

Error                            : MigrationMRSPermanentException: Error: The call to 'owa.domain.com/.../mrsproxy.svc <ExchangeHybridServerName>.domain.com

       (15.1.396.30 caps:2FFFBF7FFFFFCB07FFFF)' failed. Error details: Exception from HRESULT: 0x8144D018. --> Exception f

                                   rom HRESULT: 0x8144D018

MigrationType                    : ExchangeRemoteMove

So like pretty much the same. We are not using TMG/ISA (as read many posts there is a flood prevention cousing it)

Any ideas that can cause the issue?

Appreciate any help, kindest regards,

Pawel Jarosz

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
2016-06-09T02:38:29+00:00

Hi Pawel,

According to the error you put, we can see in the final incremental sync, the migration failed. But we cannot the why it failed. To help you troubleshoot the issue, I would like to confirm the following information.

1. Please run the following PS cmdlets and send us the results via PM (protect your privacy)

Get-MigrationBatch | flGet-MigrationStatistics | fl

2. And select one of the failed mailboxes, run the following cmdlet and send us results in PM as well

Get-MigrationUserStatistics -Identity *** Email address is removed for privacy *** -IncludeReport | FLGet-MigrationUser *** Email address is removed for privacy *** | fl

I have sent you a PM to request this information. Please click on the link below to access to your Private Message.

https://community.office365.com/user/conversations 

And also, please try using New-MoveRequest cmdlet to do a move to see if there is any improvement.

Many thanks,

Ran

Was this answer helpful?

0 comments No comments

9 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-07-13T03:12:55+00:00

    Dear RanMo_MSFT,

    I am having the same issue with my migrations. I am not running TSG. I opened a case with Microsoft has not been able to find a solutions. I would like to know how did you resolve this problem? How can I know if the tenant that I am running is not up to date?

    I am running Exchange hybrid 2016 CU2.

    I greatly appreciate your help and support.

    Carlos

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-10T04:24:47+00:00

    Hi Pawel,

    Thanks for the updates on this issue. You can share the case number (service request ID ) via PM with us so that we can check the process and monitor the case for you.

    Best regards,

    Ran

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-09T04:15:18+00:00

    Hi Ran Mo,

    Thank you for your help. Actually yesterday we had a call with engineer from MS support. What appeared was:

    • We might have old tenant version, engineer told me he will upgrade it and later we will see the migrate cmdlet - if it wil start to work,
    • He told me that there is some sort of problem currently and that we need to increase limit for bad items, I was told that even if mailbox is ok, somehow these problems on O365 side cause mailbox failure with such weird error

    -We restarted the MRS service on our hybrid node (the one that was pointed as migration endpoint)

    After restart of that service, and increasing amount of baditems - MOVES are going good, we still have troubles with migration tasks.

    Problem with migration tasks we see is that, after I create a migration tasks for one mailbox (form CSV, user given directly, using powershell or GUI - whatever) at the begininng first few seconds I see that there is one maibox to migrate. BUT just after few seconds mailbox count is 0 - Magic :D really. so MS engineer was shocked a bit, checked the tenant version, and told me that it might be connected to that, so currently we are waiting to have out tenant upgraded.

    Thanks for all your help,

    Pedro vel . Captain Email

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more