(hr=0x80004005, ec=1142) when trying to migrate Exchange Server user

Ardan Zaki 236 Reputation points
2023-04-06T07:28:33.7966667+00:00

Hi, I want to do On-premise Exchange 2016 to 2019 Migration and Co-existence. I got this error when trying to migrate user from 2016 to 2019 server. image

Exchange | Exchange Server | Other
Exchange | Exchange Server | Management
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Amit Singh 5,306 Reputation points
    2023-04-07T05:03:53.81+00:00

    To anyone who might face this problem HR 0x80004005 EC 1142 in the future, the solution was to enable MAPI over HTTP: Set-OrganizationConfig -MapiHttpEnabled $true.


  2. Xuyan Ding - MSFT 7,601 Reputation points
    2023-04-07T07:26:06.88+00:00

    Hi @Ardan Zaki ,

    Please check the firewalls on both sides to ensure the network connection between the servers.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  3. Xuyan Ding - MSFT 7,601 Reputation points
    2023-04-10T09:18:43.3733333+00:00

    Hi @Ardan Zaki ,

    Please check first whether the status of the target database is mounted and then try the following.
    User's image

    1.Try to migrate via New-MoveRequest command:

    New-MoveRequest -Identity '<mailbox>' -TargetDatabase "<database name>"
    

    2.Try to move the user to a new database on another server to determine if the migration problem is caused by the mailbox.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  4. Ardan Zaki 236 Reputation points
    2023-06-15T09:22:46.4066667+00:00

    Hi everyone, we finally found the root cause of this problem. Turns out the Antivirus was blocking the transaction and it resolved after we disabled the antivirus and reconfigured it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.