Forum Discussion
Teams error "We ran into a problem. Reconnecting..."
We have a large number of users reporting that when they launch Teams or try to join a meeting in Teams they encounter an error message that states either "We ran into a problem. Try again in a few minutes" or "We ran into a problem...Reconnecting...". Screenshots attached.
- This happens both on the company network and on VPN while at home.
- All PCs are running Windows 10 1809
- Issue occurs on multiple Dell laptop models
Things we have tried:
- Sign out of Teams and sign back in (defaults to UPN@domain.com)
- Sign out of Teams and sign back in with the full email address instead of UPN@domain.com (example: "firstname.lastname@domain.com" instead of "UPN@domain.com")
- This seems to have temporarily worked for some of the users that attempted this workaround on 9/14
- Uninstall/Reinstall the Teams desktop app
- Clear Teams cache in %appdata%\Microsoft\Teams
- Uninstall/Update Teams mobile app
- Clear cached credentials in Credential Manager
- Update drivers/BIOS
Any input or advise would be much appreciated!
55 Replies
- unluky, our turn. several people face this now...
- any help, we have a problem, the same. But we have a problem with both Outlook and Teams, which cannot connect to the server. We use web apps but this is the same.
So maybe it is from a server problem, right? Folks, if this still occurs - check if your Firewall and geo-blocking rules.
I found that if I logged onto the VPN - the issue was resolved.
Checked against the Firewall and my IP was geo located in JP. Which was recently geo blocked here....
Once the rule was removed, Teams is now working okay.
- In my case, the culprit is the McAfee Antivirus/Firewall that came with the DELL notebook. Its subscription is free for the first few months. The Teams connections worked. Then the free subscription ended. Instead of disabling itself, somehow it blocked certain connections.
I uninstalled it and use Windows Defender now.
Josiah_H I didn't have this problem until we moved to webroot a/v, just throwing it out there. Stopping the 16 teams processes running in the background has temporarily fixed me.
- I've been having this problem for weeks. I'm glad I'm not alone!!
nickmckennaalso started occuring in my business since Monday. The temporary solution is to uninstall, remove all Teams related folders under %APPDATA%, install again and then it works. But the error "We ran into a problem. Reconnecting..." comes back the next day like a loop.
- Is this still going on? been plaguing me all month, I finally bit the bullet and rebuilt my boot drive from scratch, all fresh installs, then the issue started reoccurring today. so frustrating!!
- Hi,
I know that this is an old thread but had same problem just today.
I'm pretty sure it won't apply to everyone but for me a cause was that I had Telerik Fiddler 4 application open.
It was just running in the background. After putting my computer into sleep and waking it back up my Teams app couldn't connect. Of course, restarting it didn't help.
I tried deleting the Teams folder from APPDATA but it was in use (Teams was closed). Then it suddenly came to me that the Fiddler could be using it. I was correct š - It worked for me. Wifi disconnect and reconnect method
- It worked for me. I did not reset the wifi router, but disconnect and reconnect the wifi of the PC and then it worked.
Thank you so much. Has anyone heard from Microsoft with a real root cause analysis and an ETA on a fix?
I'm getting the "We ran into a problem. Reconnectingā¦" message regularly appearing at the top of a browser Teams session on a Chromebook which has direct Internet access. It occurs for both wired and wireless connectivity. While the message is on the screen I am still able to navigate around the Teams environment, compose and send messages, and I'm fairly sure I have had an active call (which was unaffected). This is mostly a cosmetic nuisance for me (the chat compose window shifts down and up when the message appears / disappears). But I am concerned that there may be a problem behind the scenes and it just may impact a call or a meeting one day.
I keep meaning to set up a network tap and grab a wireshark trace of it doing it - but I doubt anyone at Microsoft would be interested so it doesn't seem worth the effort.
- open run and then type "msconfig" without quotes and now in that box select services. then select enable all and then apply . Restart device and you are good to go
- Solution: Disable AdFender and Exit it. This should fix the problem.
- This problem in the my laptop
- Any permanent solution for this issue. I can see for the same issue there is a old problem ticket with Microsoft: Ticket number TM170445
