The SRV record is technically a fallback autodiscover method, and isn't used unless http and https requests fail. Outlook doesn't query the SRV autodiscover record because the first attempts on https and http worked, just returned bogus results, thereby telling you "Something went wrong". If the registry hacks for ExcludeHttpsAutoDiscoverDomain fix your problem, you probably have the issue that highlighted - your web hosting provider is answering autodiscover requests on https:/ / :443/ autodiscover/ autodiscover.xml before the SRV record pointing to Microsoft can answer them. Look at the URL and it's probably pointed to your rather than If you have this issue it will indicate that your Autodiscover is getting bad information.
SETTING UP MICROSOFT OUTLOOK 2016 DOWNLOAD
To test to see if this is your issue you can download the "Fix Outlook and Office 365 problems with Microsoft Support and Recovery Assistant for Office 365" tool and run it. "Local Mail Exchanger" to "Remote Mail Exchanger" click on the "Change" button and you should be good to go. The fix is simple log into your cPanel management console and go to MX Settings. By default the cPanel application redirects the autodiscover request from Outlook and points it to your website domain rather than to the Office 365 autodiscover. In our case the issue started when we turned on web hosting using cPanel. However sometimes it is just easier and quicker to start a fresh profile. I spent hours on this uninstalling Office, setting registry keys, etc.įor me the difference between a new profile and so-called "corrupted profile" is always a simple registry setting or deleting an app specific setting. Removing the account from there and trying to add the account to Outlook is what fixed the issue for me! Along with adding the credentials to control panel Credential Manager it also adds the account to the "Access Work or School" section as mentioned. When you add a new Office 365 account as part of the newer Outlook 2016 Account Wizard it asks if you want to add this account to the computer or something to that effect.
SETTING UP MICROSOFT OUTLOOK 2016 WINDOWS
It was in the Windows 10, 'Change Account Settings" section under "Access Work or School"
The problem was credential related but not the control panel credential manager. None of these suggested fixes actually fixed my problem. Not 100% sure what this reg change does, but it's also referenced in an office Microsoft Article. Solves the issue immediately, not restart required. Right Click, create new Dword (32bit) Value, name it 'ProtectionPolicy' then edit it to the value of 1. "To work around this problem, set the value of the ProtectionPolicy registry entry to 1 to enable local backup of the MasterKey instead of requiring a RWDC in the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb Applied it and it fixed the VPN issue and just for kicks tried the Outlook set up again and it went through immediately. The computer must be trusted for delegation and the current user account must be configured to allow delegation.
Started looking into the VPN connection error ( I had this problem and also could not set up a PPTP VPN connection. I hope this helps others that were just a frustrated as me. I find that this is definitely a bug in Outlook 2016. You should be able to use the Mail control panel tool to set this up as we have always done. Note: Having worked with Exchange and outlook for a very long time I find that this change was not intuitive and does not comply with standard processes maintained by Microsoft for a decade. You must use the Outlook setup wizard that will start when you open outlook for the first time with no profiles. Don't use the Mail(Outlook 2016) in control panel to setup the new account, it will not work.Ĥ. In Control Panel, Mail (Outlook 2016), delete all profiles and close it.ģ. Uninstall all older versions of office and reboot.Ģ. I discovered that outlook 2016 is quite grumpy and so you must follow NEW protocol.ġ. However, office365 works fine from webmail, iPhone, android, and previous versions of outlook. I get the "something went wrong message." This problem occurred on several computers with office 2016 on different networks and operating systems. Symptom: Can't setup outlook 2016 to get my office365 email.
I have been struggling with this same issue for many weeks and I found my solution.
0 kommentar(er)
