locked
Exchange 2013/2007 Co-existence RPC over HTTP connectivity failed RRS feed

  • Question

  • Hi all,

    Hope someone who experienced this before please shed some light for us.

    In present, we are migrating exchange 2007 to 2013, and co-exist until we decommission the legacy 2007, then move on migration path to exchange 2016. We did the migration by using Exchange Deployment Assistant. Everything went smooth such as owa, activesync, outlook client on legacy mailbox and outlook client on new mailbox, they are working fine. So we are curious out of nowhere and did the MRCA Outlook Connectivity test, it failed at 

    Attempting to ping the MAPI Mail Store endpoint with identity: b4fc456a-0bde-4c90-81ac-9de53b0e77e5@contoso.com:6001.
    The attempt to ping the endpoint failed.
     Tell me more about this issue and how to resolve it
    Additional Details
    The RPC_E_ACCESS_DENIED error (0x5) was thrown by the RPC Runtime process.
    RPC Status: 5 AccessDenied
    Timestamp: 9/16/2020 11:07:47 AM
    Generating Component: 13 (RpcHttp)
    Status: 5
    Detection Location: 1352 (HTTP2WinHttpTransportChannel__Open30)
    Flags: 0
    Parameters:
    5
    Timestamp: 9/16/2020 11:07:47 AM
    Generating Component: 14 (WinHttp)
    Status: 5
    Detection Location: 1380 (WinHttpCallback10)
    Flags: 0
    Parameters:
    12017
    /rpc/rpcproxy.dll?b4fc456a-0bde-4c90-81ac-9de53b0e77e5@contoso.com:6001
    Timestamp: 9/16/2020 11:07:47 AM
    Generating Component: 13 (RpcHttp)
    Status: 5
    Detection Location: 1680 (StartServiceIfNecessary10)
    Flags: 0
    Parameters:
    2
    /rpc/rpcproxy.dll?b4fc456a-0bde-4c90-81ac-9de53b0e77e5@contoso.com:6001

    It is strange that the Outlook clients are able to established RPC/HTTP to new exchange and legacy servers, but have no clue of what reason MRCA showed this error. Despite searching solution on Internet but turns out none of them are applied to our scenario. We have multiple authoritative accept domains in the exchange, don't think this is the root caused.

    Help is greatly appreciated.

    EDIT: IPv6 is enabled on Exchange 2013, and off on legacy exchange 2007.
    • Edited by Lim Ruenn Shiang Wednesday, September 16, 2020 11:42 AM add ipv6 info
    Wednesday, September 16, 2020 11:17 AM

All replies