Reason: invalid token 'xyz' in CORS header 'Access-Control-Allow-Headers'.Reason: expected 'true' in CORS header 'Access-Control-Allow-Credentials'.Reason: Did not find method in CORS header 'Access-Control-Allow-Methods'.Reason: Credential is not supported if the CORS header 'Access-Control-Allow-Origin' is '*'.Reason: CORS request external redirect not allowed.Reason: CORS preflight channel did not succeed.Reason: CORS header 'Origin' cannot be added.Reason: CORS header 'Access-Control-Allow-Origin' missing.Reason: CORS header 'Access-Control-Allow-Origin' does not match 'xyz'.CSP: require-trusted-types-for Experimental.CSP: plugin-types Non-standard Deprecated.CSP: block-all-mixed-content Deprecated.Sec-CH-UA-Platform-Version Experimental.Sec-CH-UA-Full-Version-List Experimental.Sec-CH-Prefers-Reduced-Motion Experimental.Large-Allocation Non-standard Deprecated.Accept-CH-Lifetime Non-standard Deprecated.I hope i’ve explained correctly the problem, and that you will be able to help me !ĮDIT : Formatting. I know for sure that there is an user which is affected right now, and waiting for a fix.īasically, i just want to have answers to these questions :Ģ/ Why does the problem happens randomly across different users ?ģ/ What does this registry value does exactly ? (MSOAuthDisabled)Ĥ/ What can we do to prevent that to happen again ? The issue is still happening, but we don’t have an exact count. We had around 10 users who had the issue, and we had 40 users in Premium O365 License at the time. When it happened to several users back in september, my team and I thought it was related to some maintenance going on Exchange services. Since about a week, it works well for UserA. Doesn’t apply here, it’s Office 2016.Īlright, so the fix worked for UserA ! awesome ! let’s try it with someone else experiencing the problem ! Well, i wouldn’t post on Reddit if it worked obviously… This issue appears to have been introduced in the June Public Update. Revert Outlook 2013 to the May 2015 Public Update version. Some google-fu later, i stumble across this page : Yay, at least i can isolate the scope of the problem ! Conclusion : it’s related to user’s session. I go back in UserA’s environment, it doesn’t work. Srv Record lookup for failed (0 x 8004010F)Īlright, so at this point, i take CompA, i log in with my own credentials, i set myself an O365 Premium License, i launch Outlook 2016. this report comes from CompA, with credentials of UserA. ON OUTLOOK 2016, FROM A PREMIUM O365 OFFICE 2016 SETUP. Redirect Check to Succeeded (0 x 00000000) Local autodiscover for Failed (0x8004010F) ON OUTLOOK 2013 H&B OEM, this report comes from a working outlook profile on another computer : test with the mail account to starting When i do the Autodiscover diag (Ctrl + rightclick on Outlook in the notification zone) : I’ll reference this user by UserA, with the computer CompA. I have a perfect example of a user whom the problem happened to : Freshly created Active Directory account, Brand new Laptop with Windows 10 Installed with an ISO obtained with the Microsoft Media Creation Toolkit, Office365 Premium License, no fancy tweak, windows update ran in the first place, drivers updated from manufacturer website (including Bios). We click on it, we have a blank window which appears, and disappears quickly. When i say connection problem, i mean that in the Outlook 2016 interface, in the bottom-right, we see a button : Password Required. Everything works fine with Skype for Business, Onedrive, office online, OWA,… it’s only related to Outlook 2016. In-depth details : Users in our organization, whom uses Office 2016 (OEM H&B or O365 Premium Business ) have, or used to have, a connection problem with their Outlook. TL DR : We have an Autodiscover-related issue it happens randomly to users it fixes itself randomly i have found a fix for one which doesn’t work for another i’m desperately trying to UNDERSTAND the mechanism of Autodiscover and what settings can be culprit on the client-side, and why it seems to happen randomly across different users. I really hope that you guys can provide me some details, the issue has been running since september… Since i’ve tried to get an answer from the support i have access to (i don’t know if i can name it, but it’s an international provider of computers and services related to IT), and didn’t have any useful information, i’m asking this here. "DisableADALatopWAMOverride"=dword:00000001
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |