locked
RPC over HTTP connectivity failed - Outlook Anywhere issues for Migration to Office 365 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Any help would be greatly appreciated! I need to move my on-site Exchange 2007 users to cloud based Office 365 ASAP.

    I have a single Windows SBS 2008 server with Exchange 2007 SP3 and IIS 7.

    I cannot get a successful test on the Microsoft Remote Connectivity Analyzer so because of this I cannot configure the Migration tool in my 365 portal account.

    First issue from the RCA is the RPC over HTTP error:

    "Testing RPC over HTTP connectivity to server domain.ca. RPC over HTTP connectivity failed."

    I can connect to Outlook Anywhere internally and externally from a browser without a problem.

    Externally I use my domain.ca/remote and I get the OA login page.

    But I cannot configure domain.ca/remote as an Outlook Anywhere address in Exchange Server Configuration / Client Access properties as it's not a valid host name.

    I am thinking I need to point to remote.domain.ca, but I am not sure how to configure IIS 7 to achieve this.

    I do have a public DNS with remote.domain.ca, it resolves fine.

    My SSL certificate is set to my domain.ca.

    Or how can I configure my IIS to redirect any domain.ca request to the RPC over HTTP for migration purposes.

    Second issue is MAPI mail store error:

    "Attempting to ping the MAPI Mail Store endpoint with identity: server.doamin.local:6001"

    I do have the registry key VALIDPORTS configured with FDQN and NetBIOS names to ports 6001-6002 and 6004.

     Thank you for your time,

    Thursday, August 10, 2017 5:43 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    We have no idea of the method you're using to move to Office 365, so we can't answer your question.

    Normally I would recommend adding an Exchange 2013 server to your organization, configuring Hybrid, and then moving the mailboxes.

    If all of this is Greek to you, then I suggest that you hire an experienced consultant to guide you through your migration.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Friday, August 11, 2017 4:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, Matrx

    So you are using the method that is similar in this blog?

    https://blogs.technet.microsoft.com/canitpro/2013/11/19/step-by-step-migrating-from-exchange-2007-to-office-365/

    And when you verify Outlook Anywhere, you meet error meesage. What's the error message in detail? Would you mind to provide the screen shot?

    Have you considered other migration methods?

    https://support.office.com/en-us/article/Ways-to-migrate-multiple-email-accounts-to-Office-365-0a4913fe-60fb-498f-9155-a86516418842 

    Best Regards,

    Lynn-Li
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Matrx Friday, August 11, 2017 12:49 PM
    Friday, August 11, 2017 9:13 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Lynn-Li,

    Thank you for your answer!
    Yes I am trying to perform a Cutover Migration to cloud based Office 365 exactly like the first link you sent.

    A few notes:
    -I can connect to Outlook Anywhere through a browser no problems with https://domain.ca/remote but I cannot use that address in the Outlook Anywhere configuration in Exchange - Server Configuration - Client Access properties. I think I should have https://remote.domain.ca configured to work, but not sure how to achieve that in IIS7.
    -I have a valid SSL with my domain.ca domain
    -I am sort of thinking the issue comes from IIS7 not being able to see or connect to the RPC app under SBS Web Application maybe?
    -ValidPorts registry key as all the FDQN and NetBIOS names with ports 6001-6002 and 6004

    Here is part of the results (errors) when I run the Remote Connectivity Analyser to test.

    Error #1

    Testing Outlook connectivity.
      The Outlook connectivity test failed.
     
    Additional Details
     
    Elapsed Time: 8403 ms.
     
    Test Steps
     
    Testing RPC over HTTP connectivity to server domain.ca
      RPC over HTTP connectivity failed.
     
    Additional Details
     
    HTTP Response Headers:
    Content-Length: 58
    Content-Type: text/html
    Date: Thu, 10 Aug 2017 14:05:23 GMT
    Server: Microsoft-IIS/7.0
    WWW-Authenticate: Basic realm="domain.ca"
    X-Powered-By: ASP.NET
    Elapsed Time: 8403 ms.

    ************************

    Error #2

    Attempting to ping the MAPI Mail Store endpoint with identity: server.domain.local:6001
    The attempt to ping the endpoint failed.
    The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

    Thank you so much for taking the time to help!

    Friday, August 11, 2017 12:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Another
    note I should add:

    I can
    access the following sites manually but no success with Remote Connectivity
    Analyzer:

     https://domain.ca/remote I
    get the Outlook Anywhere login, login works fine.

    https://domain.ca/autodiscover I get a login
    prompt, login and get the following message:

    the page cannot be displayed because an internal server error has
    occurred

    But the Autodiscover portion is successful in the RCA test.

    https://domain.ca/owa I get the webmail
    login, login works fine

    What is the
    RCA test looking for when testing RPC over HTTP??

    is it looking for something like https://remote.domain.ca?


    If I do https://remote.domain.ca
    I get the 403 Forbidden: Access is denied

    Where do I give permission on this folder? if it even exists...

    Thank you
    for any help you can provide!

    Friday, August 11, 2017 5:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    But the Autodiscover portion is successful in the RCA test.

    https://domain.ca/owa I get the webmail
    login, login works fine

    What is the
    RCA test looking for when testing RPC over HTTP??

    is it looking for something like https://remote.domain.ca?


    If I do https://remote.domain.ca
    I get the 403 Forbidden: Access is denied

    Where do I give permission on this folder? if it even exists...

    Thank you
    for any help you can provide!

    RPC over HTTP is Outlook Anywhere, RCA test will check that.

    And what't this URL? "https://remote.domain.ca" ExternalHostname for OutlookAnywhere?

    And "Autodiscover portion is successful in the RCA test"? Do you mean RCA test overall result is successful?  

    Best Regards,

    Lynn-Li
    TechNet Community Support


    Please remember to mark the replies as answers.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, August 17, 2017 10:11 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Again Lynn-Li

    Thank you for your answer!

    Yes the Autodiscover portion of the RCA test is successful!

    My Outlook Anywhere External address (in Exchange) is domain.ca.
    Should it be something like remote.domain.ca??

    I have a DNS entry for remote.domain.ca which resolves to my static IP.

    I can connect to domain.ca/remote Externally but remote.domain.ca just brings me at the door.
    Not sure how to redirect remote.domain.ca to my IIS ?

    I am still getting this error:
    Attempting to ping the MAPI Mail Store endpoint with identity: server.domain.local:6001
    The attempt to ping the endpoint failed.
    The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process

    My ValidPorts registry key seems to be properly configured with all my domain, FDQN and NetBIOS with 6001-6002 and 6004 ports.

    Thank you for your help!

    Friday, August 18, 2017 1:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Your Outlook Anywhere external hostname should point to the Exchange server.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Friday, August 18, 2017 4:27 PM