9hbhq (9hbhq) asked a question.
MS Teams Thick client - Okta Widget - "there was an unexpected internal error. Please try again" following a password reset
We have a number of users reporting the above error when attempting to authenticate to the MS Teams Thick client locally on domain joined Windows 10 laptops following a password reset
- Note - users are able to sign in to Teams Web client, use Outlook Thick client, Auth to Okta portal, sign in to Teams thick client on a different machine, any other account that attempts to auth to team thick client on the effected machine fails but will work on a different machine with no issue.
We have no device trust in place and no sign on policies requiring MFA for any 365 applications currently and all effected users have exchange on premise mailboxes.
We have attempted :-
- a full cleardown of credentials manager,
- sign out of MS applications,
- Close all MS applications,
- Clear all MS Teams app data,
- Remove teams completely,
- Remove O365 and reinstall,
- Machine reboot
- full reset of IE / Chrome /
none of the above has been sucessfull?
Any quick wins here from others experiences as Okta support don't seem to have a great deal of insight at this stage and as we get more passwords being reset per our company policy this is likely going to be come a wider spread issue
Hello @9hbhq (9hbhq)
I hope you are having a great day
This type of error are very generic and may represent an unexpected situation most likely caused by an invalid configuration or environment (or source code, for developers). In most cases, there will be more information in the console log that needs to be properly analyzed, I suggest you to open a case with our support team using the information found in the link below:
https://help.okta.com/en/prod/Content/Topics/Directory/get-support.htm
Have a great day ahead
Regards
Henry Esquivel
Okta Inc
Good Morning,
We have an account with the same issue.
Followed the same exact steps you outlined above with the same result.
The account works fine on another machine but fails on this one.
Any new leads on the cause of the issue?
We found that windows devices on version 1703 or earlier intermittently present this issue after password reset, the proposed and confirmed fix for this from Okta support was to upgrade the OS to 20H2 we had 10 users experiencing this and all have been resolved with this fix, I hope it works for you
Kind regards
Ryan Makepeace
Team Lead, System Engineering - EMEA
s y n c r e o n - supply chain synergy
Mobile +44 7523 908 282
Ryan.makepeace@syncreon.com<mailto:Ryan.makepeace@syncreon.com> * www.syncreon.com<http://www.syncreon.com/>
Unit 5, Logix Park * Watling Street * Hinckley, Leicestershire, LE10 3BQ * UK
This account is using an older Windows 10 client and recently had a password reset.
Thanks for the info.
Hello!
We have found a solution after trying it all here.
Go to the teams file location and right click - properties.
Under compatibility select the mode for windows 8.
After you have done this re-run teams and it should resolve the issue.
Had to post this as this was a huge issue when users changed their password.