Forum Discussion
Microsoft Teams Error Code 0xcaa80000
0xcaa80000
Hi,
Has any come across this error code for Teams 0xcaa80000? Seem to be a lot of forum post about Outlook on various forums, but nothing for Teams.
I have tried from a different Windows account on the same machine and can login fine. Tried deleting the cache etc. Made sure the time is correct and is auto updating.
Teams was signing in previously for the user, but has stopped working today.
They can log to the Teams web app fine from the same windows account.
Our authentication goes via a local ADFS server.
Full message is:
We can't connect you
It looks like we can't connect to one of our services at the moment. Please try again later, or contact your helpdesk if the issue persists.
0xcaa80000
adfs.domain.com
I found that deleting the token binding key had resolved the issues for a number of people in Google searches that I did. Only thing is when I deleted the token key I logged into the Teams app and it error'd again. Then as part of a fiddler trace I was doing I kept trying to connect a few times with Teams one after the other and finally the ADFS page popped up to enter the users username and password and it signed in! Unsure if deleting the binding key fixed the issue or not!
C:\Users\BobSled\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Microsoft\Crypto\TokenBindingKeys\Keys
fb47a8d42be514593f982d4b0d7edd08_90cb05ef-cd90-4066-aafe-3397eb8039a5_4068bc0f75fd0f09b9c2c7507f15f982
8 Replies
- Hi,
I'm not sure if anyone else will face this issue again, but it happened to me, and it was resolved after I changed my TLS version to 1.2 in Internet Options. I had changed it earlier for some VPN testing.
Thanks blue_man
This may relate to the following articles:
- https://www.reddit.com/r/sysadmin/comments/190tvru/office_http_404_in_avd/-https://www.reddit.com/r/VMwareHorizon/comments/1avofn9/authentication_issues_with_latest_version_of_365
- https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Anyone-having-issues-with-Outlook-or-Teams-after-latest-Windows/td-p/3009088/page/2
- https://kb.vmware.com/s/article/97111
https://www.reddit.com/r/sysadmin/comments/190tvru/office_http_404_in_avd/stefanwey-umb can someone please explain to me why we, those of us in the community, are the ones responsible for continually fixing problems created by this crappy software from a crappy company called Microsoft?
Hello blue_man A quick search of past posts in this community yielded this: https://techcommunity.microsoft.com/t5/outlook/0xcaa80000-outlook-2016-you-need-internet-for-this/m-p/199922
Let us know if it doesn't work for you....
I found that deleting the token binding key had resolved the issues for a number of people in Google searches that I did. Only thing is when I deleted the token key I logged into the Teams app and it error'd again. Then as part of a fiddler trace I was doing I kept trying to connect a few times with Teams one after the other and finally the ADFS page popped up to enter the users username and password and it signed in! Unsure if deleting the binding key fixed the issue or not!
C:\Users\BobSled\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Microsoft\Crypto\TokenBindingKeys\Keys
fb47a8d42be514593f982d4b0d7edd08_90cb05ef-cd90-4066-aafe-3397eb8039a5_4068bc0f75fd0f09b9c2c7507f15f982YOUR THE WINNER! Thanks alot. We searched 2-3 weeks for the resolution/fix, and this works! Thanks!
We removed the complete AAD.BrokerPlugin folder.
