Exchange account set-up missing for Outlook 2016

Anonymous
2015-05-10T20:07:40+00:00

I recently upgraded to Office 2016 Preview from Office 2013.  I had several POP / IMAP and Exchange accounts that all worked fine prior to the upgrade.  After the upgrade the POP / IMAP accounts work fine but non of the Exchange accounts work.  I got the following message "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The Microsoft Exchange information service in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service" Ok, so deleted the account and tried to set it up again however, under "Add Account" there is no longer an option to set up an Exchange account. There are only two options: 1) Outlook.com or Exchange ActiveSync compatible service or 2) POP or IMAP. The Microsoft Exchange Server or compatible service option is missing?

Microsoft 365 and Office
Microsoft 365 and Office

A comprehensive suite of productivity tools and cloud services that enhance collaboration, communication, and efficiency. Combining classic Office apps with advanced Microsoft 365 features, it supports both personal and business needs

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

101 answers

Sort by: Most helpful
  1. Anonymous
    2015-07-31T08:06:33+00:00

    hi Diane,

    Hope you are well.

    I'm having the same issue when trying to setup my outlook.com address in Outlook 2016

    error message "An encrypted connection to your mail server is not available. Click next

    to attempt using an unencrypted connection" but also fails.

    many thanks.

    Regards,

    Hernan

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-07-24T12:51:53+00:00

    Alright here's my update.  The POP/SMTP solution wasn't actually pushing my e-mail.  Apologies if I got hopes up.  I really hope Microsoft fixes this.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-07-21T23:01:26+00:00

    Hi Diane,

    No joy.  I implemented the reg entry, deleted the autodiscover xml files -- and tried to create a new outlook profile via autodiscover.

    Simply doesn't want to complete the autodiscover.

    Reverting back to the profile created via Outlook 2013 restores my connectivity.

    Rackspace did not give an ETA, but did say the issue is on their radar :)

    Best/jim

    Was this answer helpful?

    0 comments No comments
  4. Diane Poremsky MVP 17,526 Reputation points MVP Volunteer Moderator
    2015-07-21T16:03:47+00:00

    Sadly for you DivakarBal I'm glad to have someone else chime in - presumably with a different ISP hosting your exchange account.

    Rackspace has acknowledged that it does not yet have MAPI over HTTP enabled, but that reg tweak to turn off this "protocol" did not solve my problem..

    Perhaps our friends at MS will decide to back out of removal of RPC over HTTP, or otherwise determine why autodiscover doesn't work for us :)

    The best bet is opening a support case so the engineers can look at your system.

    Did Rackspace say when they were going to implement mapi over http?

    This is the key you set?

    Key: HKEY_CURRENT_USER\Software\Microsoft\Exchange

    DWORD: MapiHttpDisabled

    Value: 1

    Did you also do this (from http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx)

    I updated the registry key to disable MAPI/HTTP on a client but the connection didn’t change?

    The registry entry simply controls what Outlook sends to Exchange about its MAPI/HTTP capability during an Autodiscover request. It does not immediately change the connection method Outlook is using nor will it change it with a simple restart of Outlook. Remember, the Autodiscover response Outlook gets only has MAPI/HTTP or RPC/HTTP settings in it so it has no way to immediately switch types. You must allow Outlook to perform its next Autodiscover request and get a response from Exchange after setting this registry entry before the change will take place. If you must attempt to speed along this process, there are two options.

    1. Set the registry entry as you wish, close Outlook, delete the Outlook profile, and then restart Outlook and go through the profile wizard. This should result in an immediate switch, but any settings stored in the Outlook profile are lost.
    2. Set the registry entry as you wish, close Outlook, delete the hidden Autodiscover response XML files in %LOCALAPPDATA%\Microsoft\Outlook, and restart Outlook.
    3. Restart Outlook once more to complete the switch.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-07-21T14:22:34+00:00

    I take that back.  Outlook was working for a little while.  But then I sent an email on Friday and didn't really use outlook on my laptop until this morning (Tuesday).  I closed outlook and it stated that there were unsent items in my outbox.  Turns out the email on Friday never was sent.  Tried to resend it and it just sat there in my outbox.  Closed and reopened outlook and the error returned.  Had to recreate my profile again.  Was able to close and reopen outlook again with no error.  But I don't trust it at this point to work at all.  Who knows when it's going to stop sending my emails.

    Was this answer helpful?

    0 comments No comments