Skip to main content

Solved: MapiExceptionNetworkError When Moving Arbitration or Other Mailbox

By April 9, 2018September 18th, 2020Blog, Microsoft, Office 365
MapiExceptionNetworkError message

I was moving an arbitration mailbox is when I got this error; however I’ve seen this on other mailboxes as well.

MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

(PID 5396, Thread 640) Task New-MoveRequest writing error when processing record of index 0. Error: Microsoft.Exchange.MailboxReplicationService.MailboxReplicationTransientException: Service ‘net.tcp://ex01.stu.local/Microsoft.Exchange.MailboxReplicationService’ encountered an exception. Error: MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

Diagnostic context:

Lid: 12952   dwParam: 0x6BA      Msg: EEInfo: prm[3]: Long val: 1722
Lid: 16280   dwParam: 0x6BA      Msg: EEInfo: ComputerName: n/a
Lid: 8600    dwParam: 0x6BA      Msg: EEInfo: ProcessID: 2268
Lid: 12696   dwParam: 0x6BA      Msg: EEInfo: Generation Time: 2010-06-30 12:15:24:818
Lid: 10648   dwParam: 0x6BA      Msg: EEInfo: Generating component: 8
Lid: 14744   dwParam: 0x6BA      Msg: EEInfo: Status: 1722
Lid: 9624    dwParam: 0x6BA      Msg: EEInfo: Detection location: 1442
Lid: 13720   dwParam: 0x6BA      Msg: EEInfo: Flags: 0
Lid: 11672   dwParam: 0x6BA      Msg: EEInfo: NumberOfParameters: 1
Lid: 8856    dwParam: 0x6BA      Msg: EEInfo: prm[0]: Unicode string: EX03
Lid: 25922   StoreEc: 0x977      —> Microsoft.Exchange.MailboxReplicationService.MailboxReplicationTransientException: Exception details: MapiExceptionNetworkError (80004005): MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)

Check out Lid: 8856 above, you’ll notice it had an issue with EX03.

When digging deeper in the log you will see the 0x80004005 error code, which could be an authentication problem. So next I tried performing a New-MoveRequest, and this time with validated Exchange admin credentials. That worked the first time I ran into this issue; however it didn’t the last time, which is why I’m writing this blog.

The next few things to check and try are

  • Can you ping, telnet on 25, or RDP to the server? (Verifying any means of connectivity here)
  • Do you have multiple NICs, perhaps a DAG network?
  • Firewalls, always check the firewalls on both sides.
  • Resolution, can you resolve the server via NETBIOS name?

My issue this particular time was due to a missing DNS suffix on the primary NIC of the server. I added the old DNS suffix to my NIC on the source server, flushed DNS and was back in business.

Brandon Stuart, PEI

Leave a Reply