02-18-2019 06:23 AM
02-18-2019 06:23 AM
Not sure if this is the right place, but i can't do the "report from within teams" since teams won't start.
This happened to both myself and colleague, immediately after we were invited as guests to another organisations teams, in addition to our own. It hung and now it crashes on start-up saying "Something went wrong" and suggesting we log out and in again. Tried that. Doesn't help. Also tried removing first cache folder contents then whole teams folder from AppData/Roaming/Microsoft/teams. Only change is it now says "Failed to reach https://" instead of "Failed to reach https://teams.microsoft.com" as it did before.
I can't even get in via web browser. If i go to teams.microsoft.com I get asked to log in, but having done so I get a page at https://teams.microsoft.com/_ which just says "The page cannot be displayed because an internal server error has occurred."
02-18-2019 06:26 AMSolution
02-18-2019 06:31 AM - edited 02-18-2019 06:32 AM
These are the main problems I can see:
GET https://teams.microsoft.com/scripts/extra.js net::ERR_ABORTED 500
Uncaught Error: [$injector:modulerr] http://errors.angularjs.org/1.5.13/$injector/modulerr?p0=teamspace&p1=TypeError%3A%20Cannot%20read%2...)
I have cleared all msteams credentials from credential manager, I've cleared all storage, logged out and back in. Can't get past this script failing to download.
02-18-2019 06:51 AM
Following thread also. I have three team members down. Looking for and eta, and wondering if this is effecting anything else in Office 365?
02-18-2019 06:51 AM
Oddly, although I can't get in to Teams (two different tenants) on Mac Desktop app or Chrome, I can apparently log in from my iPhone app.
02-18-2019 06:56 AM
Our Admin had to reach out to support in order to find out MS is having issues. Sounds like they didn't know either.
02-18-2019 06:57 AM
I guess the "Admin panel" is only accessible to my sysadmins? At least, I can't find a link from www.office.com and the docs i found refer to a specific email. I'm just a humble developer (but as such I try to admin my own machine pretty far). Don't see the need to restrict access to status info
02-18-2019 07:03 AM
02-18-2019 07:09 AM
Thanks. I'll discuss that with my admins. (That link redirects to www.office.com for me, since I'm already logged in.)
I do feel however, this should be public functionality to start with - or at least available to everyone once logged in. The whole point of a status page is to avoid unnecessary time spent troubleshooting and unnecessary calls to support - so why design it so that as a user you have to spend the time anyway - or make unnecessary calls to our own support/admin. i mean, MS posted a public tweet saying there was an issue, but it just gives the ID number to follow it in the admin-only space! Makes no sense. But I guess that's a separate ticket :)
02-18-2019 07:11 AM
02-18-2019 07:29 AM
We are having the same problem with our organization.
If ANYONE signed out or signs out, the get the error trying to get back in so I cannot get to my Teams today and this is main software we use now. :(
02-18-2019 07:52 AM - edited 02-18-2019 08:18 AM
If you follow @MSFT365Status on Twitter you'll see their issue tweet - they're pretty good about getting them out there.. They tweeted an hour ago.
And west coast is affected as well. My client is still logged into Win10 so that one is fine, but I logged out of my Mac client to test and can't get back in.
Error message on Mac is Error code 500: Failed to reach: https://teams.microsoft.com
I like that they've got the actual error with a guid on the error screen - don't think that was there before.
Editing to add: there is this site: https://portal.office.com/servicestatus - that should be accessible to all. Too bad it doesn't reflect Teams status! Maybe they should add it...
And this is useful because it has a heat map https://downdetector.com/status/teams
02-18-2019 08:39 AM
Getting the same problem in the UK - Windows desktops all broken in the office (error 500 from server) but IOS app works OK. If you are already logged-in then you are OK but you can't log back in again.
02-18-2019 08:39 AM
No twitter update from Microsoft, but I can now log into both tenants via web and Mac desktop app where it was failing before.
02-18-2019 09:23 AM
Microsoft's advisory TM173756 (through the 365 admin center) said half an hour ago "We've rerouted traffic to alternate healthy infrastructure and our telemetry indicates connectivity improvement. We're analyzing the remaining affected infrastructure to determine if any other traffic needs to be rerouted." It may be that not all affected users are fixed yet, depending on what tenant and infrastructure they happen to be hitting.
03-07-2019 06:38 AM
Doesn't crash for me, but will not allow me to log in. I get the 'modern authentication failed here' error, with status: caa2000b, then Error Code: AADSTS500014: Resource 'https://api.spaces.skype.com' is disabled.
Then an endless loop of 'authentication failed. please try again.' This is making me a little crazy.
I don't even use Teams, and was simply trying to disable launch on startup. I've uninstalled it several times, but it keeps coming back. Must have been installed as part of Office364 for me, which is working just fine.
05-09-2019 05:14 AM - edited 05-09-2019 05:15 AM
@kelmar2290 okay I will try logging in tomorrow.But one of team members who is not from our organisation and doesn't have Microsoft account even he is not able to login for last two days.I added him as guest .I wanted to check what is happening so I tried signing out,now I am also not able to login from desktop team app.Though I am able to login navigating from my Microsoft account which opens in web
In Desktop Teams app I see this error code