locked
Outlook 2013/2016 error The action cannot be completed, The connection to Microsoft exchange is unavailable. Outlook must be online to complete this action. RRS feed

  • Question

  • Hi,

    In preparation to upgrade our Exchange 2013 to 2019,We had setup a testing environment to test Exchange 2019, we had installed exchange 2019 , configured external /internal URL, configured outlook anywhere and configured SSL certificate which we used internal CA. The installation was successful and email (sending/receiving) internally works in OWA, we can send and receive locally when acessing the OWA.

    But then there's an error when we setup the Outlook 2013/2016, it PASS to "Establishing Network connection" and "Searching for Account settings" but FAILS to "Logging on the Server", the error is "The action cannot be completed, The connection to Microsoft exchange is unavailable. Outlook must be online to complete this action."

    Did i miss something? Hoping for any help and advise.

    Sunday, June 14, 2020 2:42 PM

Answers

  • If this domain joined computer has access to the Internet, you can login the mailbox even outside this test environment. Then you can use Test E-mail Autoconfiguration for Exchange 2019 users.

    Please use the following command to check AutoDiscoverServiceInternalUri, make sure you can create the A record for the used FQDN, and point to the correct IP address:

    Get-ClientAccessService |fl name,AutoDiscoverServiceInternalUri

    Please check the SCP from ADSI Edit.

    Go to Configuration > CN=Configuration,DC=domain,DC=com > CN=Services > CN=Microsoft Exchange > CN=org_name > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Servers > CN=CAS_server > CN=Protocols > CN=Autodiscover.

    Right click the SCP, choose Properties and check the serviceBindingInformation attribute. Make sure the serviceBindingInformation is set to use the AutoDiscoverServiceInternalUri, which you can get by Get-ClientAccessService cmdlet.

    Try to access AutoDiscoverServiceInternalUri (https://server.domainname.com/Autodiscover/Autodiscover.xml) from your Exchange server browser, enter the credential and check to see if you will get 600 error as expected.

    Additionally, please also try to use Outlook 2019 to see if the issue can be reproduced.

    Regards,

    Lydia Zhou


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

    Thursday, June 18, 2020 9:59 AM

All replies

  • Hi,

    Do you create the Outlook profile for mailboxes located on Exchange 2019?

    If so, please makes sure you have installed the latest Office service pack and the latest public update for Outlook 2013/2016. For your reference: Clients.

    Please use the following command to check your AutoDiscoverServiceInternalUri on Exchange 2019. Make sure the related A record is pointed to a correct IP address:

    Get-ClientAccessService |fl name,AutoDiscoverServiceInternalUri

    You can use the Test E-mail Autoconfiguration feature in Outlook for mailboxes on Exchange 2019:

    1. Locate the Outlook icon in the notification area, hold the CTRL key, right click the icon, and then click Test E-mail AutoConfiguration.

    2. Enter the user's email address and password, only choose Use AutoDiscover. 

    3. View the result on the Log tab.

    Regards,

    Lydia Zhou


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

    Monday, June 15, 2020 3:18 AM
  • Hi Lydia,

    Thanks for the reply and help.

    The AutoDiscoverServiceInternalUri  address is correct, it is pointing to the ip address of the Exchange 2019 server, below is the AutoDiscoverServiceInternalUri address.


    We cannot test the  E-mail Autoconfiguration feature in Outlook because Outlook is not connected, below is the error;


    What do you mean by Outlook profile for mailboxes located on Exchange 2019? and how to do it? as i did not configure that one.

    Thanks very much again...waiting for your reply.

    Monday, June 15, 2020 6:59 AM
  • Hi Lydia,

    Additionally below is the contents when accessing the Autodiscover xml, is this correct??


    Thanks very much...waiting for your reply

    Monday, June 15, 2020 10:27 AM
  • Since our Exchange forum is a public platform, we helped you cover the domain name. Please pay attention next time.

    ErrorCode 600 means the autodiscover internal uri is set correctly, it can connect to the server and return information.

    >> What do you mean by Outlook profile for mailboxes located on Exchange 2019? and how to do it? as i did not configure that one.

    Do you have other user mailboxes work well with Outlook when use internal network?

    With domain joined computer in your organization, you can log into with an Exchange 2013 mailbox. Then locate to the icon to use Test E-mail Autoconfiguration. Enter the mailbox email address, and this mailbox must be the Exchange 2019 mailbox.

    Please also install the latest Office service pack and the latest public update for Outlook 2013/2016 to make the Outlook be supported to Exchange 2019. Also, you can try and test with Outlook 2019, check if the issue can be reproduced.

    Regards,

    Lydia Zhou


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

    Tuesday, June 16, 2020 6:46 AM

  • Hi Lydia,

    Thanks for the help and reply.

    This is a testing environment which we setup in preparing ourselves to a new exchange Server 2019 .

    For us to be familiar first with the Exchange 2019 server with its features, we had setup an isolated Testing environment with a fresh installed domain(windows 2019 server) and exchange server 2019 CU5. The installation looks OK and email (sending/receiving) works in OWA.

    It can send/receive emails when acessing the OWA but the issue are with the OUTLOOK 2016/2013 connecting to Exchange 2019 CU5 server, below is the error, all the users created have the same error With domain joined computer.

    best regards...



    Wednesday, June 17, 2020 7:15 AM
  • If this domain joined computer has access to the Internet, you can login the mailbox even outside this test environment. Then you can use Test E-mail Autoconfiguration for Exchange 2019 users.

    Please use the following command to check AutoDiscoverServiceInternalUri, make sure you can create the A record for the used FQDN, and point to the correct IP address:

    Get-ClientAccessService |fl name,AutoDiscoverServiceInternalUri

    Please check the SCP from ADSI Edit.

    Go to Configuration > CN=Configuration,DC=domain,DC=com > CN=Services > CN=Microsoft Exchange > CN=org_name > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Servers > CN=CAS_server > CN=Protocols > CN=Autodiscover.

    Right click the SCP, choose Properties and check the serviceBindingInformation attribute. Make sure the serviceBindingInformation is set to use the AutoDiscoverServiceInternalUri, which you can get by Get-ClientAccessService cmdlet.

    Try to access AutoDiscoverServiceInternalUri (https://server.domainname.com/Autodiscover/Autodiscover.xml) from your Exchange server browser, enter the credential and check to see if you will get 600 error as expected.

    Additionally, please also try to use Outlook 2019 to see if the issue can be reproduced.

    Regards,

    Lydia Zhou


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

    Thursday, June 18, 2020 9:59 AM
  • It's great that you can get useful information in replies above. Here is a brief summary about this thread.

    Issue Symptom:

    In preparation to upgrade our Exchange 2013 to 2019,We had setup a testing environment to test Exchange 2019, we had installed exchange 2019 , configured external /internal URL, configured outlook anywhere and configured SSL certificate which we used internal CA. The installation was successful and email (sending/receiving) internally works in OWA, we can send and receive locally when acessing the OWA.

    But then there's an error when we setup the Outlook 2013/2016, it PASS to "Establishing Network connection" and "Searching for Account settings" but FAILS to "Logging on the Server", the error is "The action cannot be completed, The connection to Microsoft exchange is unavailable. Outlook must be online to complete this action."

    Possible Cause:

    The configuration for Autodiscover, or Outlook 2013/2016 version is not supported with Exchange 2019.

    Suggestions:

    Makes sure you have installed the latest Office service pack and the latest public update for Outlook 2013/2016. Also try to use Outlook 2019 to see if the issue can be reproduced.

    Please use the following command to check your AutoDiscoverServiceInternalUri on Exchange 2019. Make sure the related A record is pointed to a correct IP address:

    Get-ClientAccessService |fl name,AutoDiscoverServiceInternalUri

    You can use the Test E-mail Autoconfiguration feature in Outlook for mailboxes on Exchange 2019

    Please check the SCP from ADSI Edit.

    Regards, 

    Lydia Zhou


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

    Monday, June 22, 2020 9:39 AM