Teams Error - "We're sorry -- We've run into an issue"

What an idiotic answer. Your product fails. Your answer shouldn't be so convoluted. Why would I bother when you don't even know if that's a solution.

Unfortunately the only thing I (and we of this forum) can say for sure is that MS is not going to fix this. They have simpler bugs that are much older. If the web isn't working.. I think you are out of luck. In not sure why that could be. I'm sure you've tried both chrome and edge. Firefox seems to work for me.

Shaming and threats are the most likely path to success that I can see. Eventually MS will shut down this forum.

Sorry, welcome to the list of unfortunate users.

Thanks for your response. I am using alternate tech generally, however when a customer sets up a teams call, and we have to join, we are not able to get in much of the time.

This is on both the app and the web version.

This means it's also affecting big customers of MS....

I don't know if your having the same problem the rest of us are. My problem seems to stem from Microsoft not understanding ldap & trusted domains, or perhaps just having a **** product and not caring that a small percentage of their users are unable to use it.

Some of your comments sound like you're using the web site. The web site, almost always works for me. But the features needed for a meeting/work are absent. The phone app also almost always works but dealing with files, copy/pasting, doing business related work and audio quality don't make this a viable option.

Clearing cookies and incognito mode are not going to help the exe. Well I don't think so.

If the web site isn't working or the app isn't working you might be having a different issue.

The bash script I posted seems to work for me about 80% of the time. When it works it's still crashing after the first login. ---> Run script, login crash, login success.

Specifically my experience is like this:

The login prompt will always populate the login name with an account that does not exist. Microdic takes the user from the wrong domain prepends that with the wrong domain for a suffix and assumes that this is your email. In my case this creates a non-existing email address. Below there is a link something like "sign in with a different email". Click that fix address, sign in, crash. So run script, click that link again crash, login in again click that link again and success it asks for a password.

In other words crashing is a mandatory step towards logging in, 100% of the time. In the latest version of the exe there is either one or two links next to the "sign in with a different email" link (I forget what the other says.. Perhaps "forgot my password". ) Only when the single link is present did the bash script work. If two links are present just run the script again. If I have to run the script multiple times ~5 times then it's time for a reboot.

In case it is not clear Microsoft really really sucks. They do not care about you, and your company should consider moving to Linux/Mac and Zoom. They would rather lose a few customers than to deal with this bug. Meanwhile Microsoft has been working hard on creating new avatars and presenting the meeting with a fun little avatar theater. There are new "like" animations and white board features (not sure what that even is). They plan to get off the electron based app someday because of a few annoying user bugs like this one. Btw, another 4-year old bug is that sometimes when you type the text shows up backwards. (I am not kidding, the textbox loads up to slowly and send the text to a new textbox that was rendered late, the letters are sent over one at a time and wind up in reverse)

I'm sorry that's about as much help as I can provide. If you do login please do us all a favor and go to the help > suggestions feature. Make sure to use ALL CAPS! and be bountiful with adjectives and colorful language. Some interns at Microsoft has to click delete for each suggestion you provide. Perhaps we can get that intern to complain to his manager someday.