Forum Discussion
DHuttema
Jul 26, 2019Copper Contributor
User can't get Teams to work - error message
Have a user in a business environment in Peer to peer, getting the following error:
microsoft teams won't allow the user to sign in, getting error code caa70004
Teams is currently the free version, so finding support for this is next to impossible. The app just wants to Restart, and goes no where but the error code. Local users, not on O365, but the users account can log in on office.com.
Any help would be appreciated. And no, have not just done the uninstall/re-install, yet.
Thanks,
Dave
DHuttema We had this same issue today with teams installed on one of our machines, it turned out the TLS was switched off in Internet Explorer. Turning this back on resolved this issue for us.
- Open Internet Explorer.
- Go to the Tools menu.
- Select Internet Options.
- Select the Advanced tab and scroll down to the Security section.
- Check to see if you have TLS 1.1 enabled, TLS 1.2 enabled (checked). If not, check the box to enable it.
- Select OK.
- Close Internet Explorer
- petergroftCopper ContributorThe Microsoft Teams desktop app automatically updates whenever a new version gets released. You can check your current version here:
Click the menu next to your profile picture at the top right of Teams
Hover on About
Select Version
You can also check if there are any available updates instead:
Click the menu next to your profile picture
Select Check for updates
Microsoft Teams will check if there are any updates. It should automatically update your Teams while you use the app
This May Work,
Peter- EricSzajaCopper Contributor
I spent a few hours trying to fix this issue on business 365 account. Teams just stopped working on a single computer with the error caa70004. All other 365 Apps worked fine.
I tried re-installing, tried clearing the cache multiple times, attempted multiple suggested solutions.
This was on a Windows 11 Pro machine with everything up to date.
Finally gave enabling TLS 1.1 and TLS 1.2 in Internet Options.
That seemed to solve everything. Signed in without any issues after that.
Thought I'd update in case anyone else is loosing their mind trying to get this to work 🙂- EricSzajaCopper ContributorAlso, not Teams related but at the same time had another user that was having trouble signing into Outlook desktop application. Just stopped working in the middle of the day. He was getting error 0x80004005 (unable to sign in)
After trying everything, I suggested he'd try to enable TLS 1.1 and TLS 1.2 in Internet Options. Figured if it fixed issues with signing into Teams, it might also fix issues with signing into Outlook.
He enabled TLS 1.1 and TLS 1.2 and Outlook immediately started working again.
- DHuttema150Copper Contributor
Sorry, this issue has long been fixed. Re-installed and upgraded to the paid version with Microsoft 365. No issues since, and Teams only just keeps getting better.
- gbduenowCopper Contributor
Remove User Windows Credentials in Control Panel Credential Manager
Uninstall Teams
Delete 'C:\Users\username\AppData\Roaming\Teams' folder
Reboot
Reinstall Teams
- DHuttema150Copper Contributor
This issue has long been completed.
Complete re-install of teams likely using the fix-it utility from Microsoft repaired the issue.
Since then we have gone to the full Office 365/Microsoft 365, just makes it better. - mlopezc025alumnouaemCopper Contributor
- adklsyCopper Contributor
Hi I cannot sign in my teams account ,
Error code - caa5004b,will you please help? Thank you ! - mhadnanaliCopper ContributorHad same problem. just turned off vpn and started working. I hope it may work for someone.
- CaseyBBrass Contributor
DHuttema - I saw this error, tried clearing cache, uninstalling, rebooting etc. Nothing worked. But we do use a web proxy agent, and when I disabled the agent, then Teams could sign in. So I'd also check your web proxy and any agents that are filtering traffic on your network. I need to follow up on why on this one PC the Teams sign-in was being block -- other PCs are configured the same way but don't have the problem. Seems this is an error with many potential fixes - some cache-related, some network, etc