3 stories
today

Microsoft Teams Tips: fixing a 500 login error

The developers behind Microsoft’s new set of Teams apps have been on a publicity tour of sorts as they explain the various features of the productivity program while extolling the differences between it and its nearest competitor, Slack.

For the most part, the Teams team has had a relatively easy job as the apps are bundled with Office 365 subscriptions and are becoming a no-brainer for users already invested in Microsoft ecosystem.

However, there has been a small sect of people who are invested in Microsoft ecosystem, eager to try out Teams and ready to get start with enterprise level chat and collaborative communications but are being met with a huge roadblock. Some individuals who tested the preview version of Teams are now being met with an Error 500 code that prevents the Windows 10 desktop app from fetching the server and thus not opening.

Anecdotally, I suffered from the Error 500 code issue and joined the crowd of unfortunate users who had to settle on using the web version of the app to continue to collaborate with co-workers. Fortunately, there is a really simple workaround that will help most users avoid the resetting of a Windows 10 PC that I went through.

A user over at the Microsoft Tech Community page has a solution that seems to have helped most who have run into Error 500 and it includes a simple three step process to fixing the issue.

I had Teams clean-installed recently and I get the error from the get-go. This is how I fixed mine….

1. Go to the System Tray and right-click on the Teams icon

2. Select Log Out

3. The app will go through the motions of logging off and restart, then ask for your credentials. Enter your O365 credentials and you should be fine.

I discovered that my issue was likely due to my having a Hotmail account to login to my Windows 10 PC. Teams was probably picking up on that and using this wrong account to login, which incidentally caused it to fail. Logging off and logging in with the correct credentials solved mine.

After applying the fix myself, I can vouch that it does address the Error 500 issue and should help those suffering from it, get back to using Teams quickly.

Let us know what other issues you might be having with Teams, and hopefully, we’ll continue to find solutions as time goes on.

Further reading: , , ,

How has your Teams experience been going?