The Microsoft 365 Status Twitter account informed the world that incident TM173756 was progressing. Understanding the Status of Incident TM173756 That can help if you have some local corruption, but it has absolutely no effect when a back-end service is bust. Mon 15:35:47 GMT+0000 (GMT Standard Time) - event - name: desktop_page_bad_response, responseCode: 500, errorUrl: Mon 15:35:47 GMT+0000 (GMT Standard Time) - info - Handled get response details with http response code 500: If you search the internet, the advice for dealing with a 500 error is often to remove all Teams credentials from the Windows Credential Manager. Here’s an example: Scenario.Name: desktop_win_sso, Scenario.Step: stop, Scenario.Status: success, No Joy Found in Teams LogsĮxamining the Teams logs (click the Teams logo in the system tray and select Get Logs from the menu) didn’t shed any light onto the problem. No amount of signing out and back in again helped because the problem existed in the Teams back-end services and the client could not obtain the necessary token. In any case, once the time came for the client to reauthenticate itself, it failed and “D’oh” appeared. The desktop and browser clients are built with Electron and the desktop client is essentially a wrapper around the browser client. This is probably due to the way that the desktop/browser clients authenticate once an hour to refresh their tokens while the mobile client uses a different mechanism. Error 500 as the Teams client can’t connect to its servicesĭuring the incident the Teams mobile client continued working. Dutifully reporting “D’oh Something went wrong…” and issuing a totally unhelpful 500 error code because the client couldn’t connect to (or even just at times), the problem turned out to be the first major world-wide outage for Teams. These reports can also be exported in PDF, CSV, XLS, or HTML formats.Everything was progressing normally until lunchtime (UTC) Monday when my Teams desktop decided that it didn’t want to connect to the Teams back-end services any longer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |