Jul 26 2019 09:14 AM
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
Jul 26 2019 09:36 AM
Jul 26 2019 10:12 AM
@adam deltinger, hmm. Tried that script, came up with a couple of errors, then seemed to run. But the same issue. So I'm thinking maybe the info didn't clear out.
I'm just going to see what happens with uninstalling and re-installing the app.
Dave
Nov 12 2019 10:24 PM
Jan 09 2020 09:29 AM
Solution@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.
Mar 16 2020 08:53 AM
It's not working for me either and I'm a office 365 user. Same messages as yours. TLS is not the problem.
Apr 28 2020 11:31 PM
For me the problem was caused when I tried to login from my home PC. The login page tried to redirected to our company sign on for authorisation against our firewall but I was already connected via a Cisco product. So it displayed a blank page and then timed out with caa70004. I needed to disconnect from Cisco first, then log in to Teams and then our internal sign on page appeared successfully, then I could login to Teams. Then log back in to Cisco. This only happened when I changed my password.
May 22 2020 04:07 AM
@Rhys Allen Thanks! this worked 🙂
Jun 08 2020 05:33 AM - edited Jun 08 2020 05:34 AM
Jun 11 2020 06:51 PM
Post resetting my office password teams started showing the issue was receiving the same page
"run into a issue" with error code caa70004.
Tried the following and it worked flawlessly, the inital mistake i was doing was that i was on VPN & company sign in page already.
>>> ensure you are not on any vPN or company related production connection, keep it on simple internet connectivity.
>>> clear the cache in all cache folders only
%AppData%\Microsoft\teams\application cache\cache
during the above ensure teams is not running, post clearing the cache start the teams on plain internet connectivity and then it shows the organisation sign in page post that it should work unless you have other underlying symptoms.
Jun 26 2020 09:12 AM
@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
Aug 26 2020 09:46 AM
Aug 31 2020 05:48 AM
@DHuttemaafter disconnecting VPN I was able to login the teams. After that teams was working thru VPN as well.
Sep 08 2020 09:03 AM
@Rhys Allen thanks! That worked!
Sep 17 2020 11:00 AM
¬¬¬Life SAVER¬¬¬
I just turned my BitDeffender Firewall OFF and everything worked like a charm.
I even had issues with "licencing" failures and all these went away.
Thanks again 🙂
Sep 23 2020 08:05 PM
Oct 27 2020 12:25 PM
Script seems to be not working. Error below.
"teams_clear : The term 'teams_clear' is not recognized as the name of a cmdlet, function, script file, or operable prog
ram. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ teams_clear
+ ~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (teams_clear:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"
Jan 18 2021 11:02 PM
Hi I cannot sign in my teams account ,
Jan 31 2021 01:51 PM
@Rhys Allen thank u man u solve my problem
Jan 09 2020 09:29 AM
Solution@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.