failed to migrate mailbox database from Exchange 2010 to Exchange 2016

ezz 1 Reputation point
2021-09-14T03:04:31.03+00:00

Hi,

I'm trying to migrate my Mailbox database from Exchange 2010 (running on Server 2012) to Exchange 2016 (Server 2016), but it failed.
The Error message was;

Error: MigrationTransientException: MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80004005, ec=2423)‎ Diagnostic context: ...... Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1722 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 323 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0 Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0421-09-09T07:24:02.9210000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1237 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 313 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0 Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0421-09-09T07:24:02.9210000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 311 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 135 Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0 Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0x8B5A8C000000000 Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0421-09-09T07:24:02.9210000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 318 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0 Lid: 53361 StoreEc: 0x977 Lid: 51859 Lid: 33649 StoreEc: 0x977 Lid: 43315 Lid: 58225 StoreEc: 0x977 Lid: 39912 StoreEc: 0x977 Lid: 54129 StoreEc: 0x977 Lid: 50519 Lid: 59735 StoreEc: 0x977 Lid: 59199 Lid: 27356 StoreEc: 0x977 Lid: 65279 Lid: 52465 StoreEc: 0x977 Lid: 60065 Lid: 33777 StoreEc: 0x977 Lid: 59805 Lid: 52487 StoreEc: 0x977 Lid: 19778 Lid: 27970 StoreEc: 0x977 Lid: 17730 Lid: 25922 StoreEc: 0x977 --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80004005, ec=2423)‎ Diagnostic context: ...... Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1722 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 323 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0 Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0421-09-09T07:24:02.9210000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1237 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 313 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0 Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0421-09-09T07:24:02.9210000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 311 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 135 Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0 Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0x8B5A8C000000000 Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6252 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0421-09-09T07:24:02.9210000Z Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 318 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0 Lid: 53361 StoreEc: 0x977 Lid: 51859 Lid: 33649 StoreEc: 0x977 Lid: 43315 Lid: 58225 StoreEc: 0x977 Lid: 39912 StoreEc: 0x977 Lid: 54129 StoreEc: 0x977 Lid: 50519 Lid: 59735 StoreEc: 0x977 Lid: 59199 Lid: 27356 StoreEc: 0x977 Lid: 65279 Lid: 52465 StoreEc: 0x977 Lid: 60065 Lid: 33777 StoreEc: 0x977 Lid: 59805 Lid: 52487 StoreEc: 0x977 Lid: 19778 Lid: 27970 StoreEc: 0x977 Lid: 17730 Lid: 25922 StoreEc: 0x977

If I try to pry on port 135 the result was;

TCP 0.0.0.0:135 ***:0 LISTENING
RpcSs
[svchost.exe]

Can anyone help me with this?
Thanks in advance

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,429 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Amit Singh 4,861 Reputation points
    2021-10-07T02:53:42.17+00:00

    This error appeared when you failed to connect to the server itself. So you can start investing below points.

    Also, can you please verify that there is a problem with mailboxes or anything which makes all processes fail?

    • You can try to configure one to a separate server in your Exchange environment and try that new endpoint.
    • If you have only one, start investing on the same server, as that is the server that cannot be connected.
    • Also, users who had problems for looking up the source server by NetBIOSname, were getting this error. I would suggest using the FQDN even when their connections were correct.

    I can recommend using a different migration endpoint if you have that option (but again, you could have the same setup problems on more than one server).

    I hope this will help you.

    You can also check out this article for step by step process - How to Upgrade Exchange 2010 to 2016.

    1 person found this answer helpful.
    0 comments No comments