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

Hello,

We have 2 Exchange 2013 (build 712) servers in a DAG with distinct subnets. Cisco ASA in between was set to have no filtering between servers in subnet.

We cannot add database copies nor move mailboxes.

Tes-Mapiconnectivty fails with

unspaceId  : e8a087f1-6197-48df-b094-d5c93a7b6070
Server      : CLI-SRV01
Database    : CLI-MDB01
Mailbox     : SystemMailbox{376e8d54-7154-484a-a0a3-58f22d73236f}
MailboxGuid :
IsArchive   :
Result      : *FAILURE*
Latency     : 00:00:00
Error       : [Microsoft.Exchange.Data.Storage.MailboxOfflineException]: Cannot open mailbox /o=First
              Organization/ou=Exchange Administrative Group
              (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=CLI-SRV01/cn=Microsoft System Attendant. Inner error
              [Microsoft.Mapi.MapiExceptionMdbOffline]: MapiExceptionMdbOffline: Unable to make connection to the
              server. (hr=0x80004005, ec=1142)

In event log:

The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: RDB
Error: MapiExceptionRecoveryMDBMismatch: Unable to open message store. (hr=0x80004005, ec=1165)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=132]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=248][latency=0]

Adding database copy fails with

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'CLI-SRV02.CLI.ch'. Hresult: 0xc7ff07d7. Error: Failed to open a log truncation context because the Microsoft Exchange Information Store service is not running. [Database: CLI-PFDB02, Server: CLI-SRV01.CLI.ch]

How can I further verify communication from CLI-SRV02 to CLI-SRV01 ?

Any help w

July 18th, 2014 2:17pm

I think you have verified that you are having communication problems.
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2014 1:32am

I agree.

How can I possibly prove it to the Cisco FW admin?

July 21st, 2014 5:44am

Show him the error message?
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2014 4:36am

Hi,

Let's begin with the following similar thread:
http://social.technet.microsoft.com/Forums/en-US/b651d65c-92f3-460c-b555-247acb8e6fd7/recovered-exchange-2013-arbitration-system-mailboxes?forum=exchangesvravailabilityandisasterrecovery
It is the same error in the event log with you when moving mailboxes. And it can be resolved by recreating the mailboxes.

Additionally, to check the network connection between two servers, I recommend you use the network monitor to catch the package.
Thanks

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

July 25th, 2014 6:38am

Hi Angela,

thanks for the hint but I'm afraid thread isw not applicable for my case. I have no problem with databases nor with arbitration mailboxes relocation.

There's a general mapi connectivity issue between the two servers despite

- TCP 135 being reachable both ways
- Netmon log showing multiple TCP & MSRPC conversations between servers while test-mapiconnectivity is ran; no trace of retransmit attempts
- Local Test-MapiConnectivity reports no problem
- Cisco ASA in between has no filter set between those two servers (reported from Network Admin)

FYI I opened a case at MPS and expecting a session in 2h.

Regards

Free Windows Admin Tool Kit Click here and download it now
July 25th, 2014 8:29am

Hi,

How about the issue now after you open a case at MPS? If you have any question, please feel free to let me know.

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

July 28th, 2014 9:32am

Did you ever get a response to this? 

I am having the same problem and have had a case open with MS for nearly 3 weeks to no avail...

Free Windows Admin Tool Kit Click here and download it now
April 13th, 2015 10:18am

To simplify it you can lock down the MAPI ports to two, then you'll know what ports to look at after the endpoint mapper (TCP 135) assigns a port.

http://social.technet.microsoft.com/wiki/contents/articles/864.configure-static-rpc-ports-on-an-exchange-2010-client-access-server.aspx

April 13th, 2015 9:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics