Advertisements

How to troubleshoot Microsoft Teams client logs

Over the last few months Microsoft Teams has been making a great impact! It’s been awesome to see an application that gives you the call and video functionality of Skype for Business and the collaboration strengths of SharePoint together with integration options with other application.

Over the last few days however there has been quite a lot of trouble with Microsoft Teams. Just to give a bit of an idea of the impact that faulty Channels in teams has, here is one of the conversations on Tech Community.

So how do you troubleshoot Teams.

 

The magic key combination is: Ctrl – Shift – Alt – 1

Well that is the easy part of troubleshooting Microsoft Teams!

 

I’m not going to try and understand all the messages here, but there seem to be two parts to this file.

First there is a bit of json formatted text:

[code lang=text]
{
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Teams/1.0.00.19451 Chrome/58.0.3029.110 Electron/1.7.1 Safari/537.36",
"sessionId": "414f85d5-fbf1-f9b4-f290-17b3b7418dad",
"version": {
"buildDate": "2017-07-19T00:07:39.747Z",
"versionDate": "2017-07-18T23:46:35.000Z",
"versionHash": "aff87a541c1617faad141e6d6ee80aea44b9505b",
"clientVersion": "27/1.0.0.2017071801",
"semver": "1.0.2017071801"
},
"stateHistory": [
{
"url": ":middlePane/:slug?threadId&messageId&ctx&context",

"views": {
"0@": {
"templateUrl": "components/middle-messages-stripe/middle-messages-stripe.html",
"controller": "MiddleMessagesStripeController",
"controllerAs": "middleMessagesStripe"
}
….

[/code]

This is followed by lines that have a time stamp, an message level and a message.

The message levels that I have seen are:

  • War : Warning
  • Err: Error
  • Inf: Information

[code lang=text]
2017-08-03T14:28:26.278Z War Analytics service: Panel data not present to populate panel action, falling back to main

2017-08-03T14:28:26.278Z War Analytics service: Panel data not present to populate panel action, falling back to main

2017-08-03T14:28:26.175Z Inf AUTHSSO:ELEC: IPC correlationId:8b4fd8eb-de46-4fef-82c8-c1c41348fe0d call success. sendEvent:sso-getAdalSsoToken-send receiveEventsso-getAdalSsoToken-receive

2017-08-03T14:28:26.174Z Inf AUTHSSO:ELEC: IPC correlationId:8b4fd8eb-de46-4fef-82c8-c1c41348fe0d call returned. sendEvent:sso-getAdalSsoToken-send receiveEventsso-getAdalSsoToken-receive

2017-08-03T14:28:23.061Z War MessageThreadListViewModel: Attempt was made to add start marker again

2017-08-03T14:28:23.050Z Inf MessageService: getMessagesForReplyChains() latestDeliveryTimeExclusive: undefined replyChainCount: 5 conversationId:19:12aad3df90b5433b81ce8e4c444bc127@thread.skype
2017-08-03T14:28:22.730Z War conversationToChannel: ThreadTopic – Name mismatch!
2017-08-03T14:28:22.391Z Err Unhandled exception. Error: [ngRepeat:dupes] http://errors.angularjs.org/1.5.5/ngRepeat/dupes?p0=channel%20in%20team.overflowChannels%20track%20by%20channel.objectId&p1=threads&p2=%7B%22_activityCount%22%3A0%2C%22_unreadCount%22%3A0%2C%22_isHighImportance%22%3Afalse%2C%22isHoisted%22%3Afalse%2C%22objectId%22%3A%22threads%22%2C%22displayName%22%3A%22SharePoint%20on%20premises%20development%22%2C%22parentTeamId%22%3A%2219%3A8ad0bd298b80478682e96c2b98a8fe6f%40thread.skype%22%7D, cause:
[/code]

The above errors show that there were some errors with the channels, which matches the issue in the above tech community link. Microsoft is currently working on this.

For more information on logging please also read: https://veenstra.me.uk/2017/08/07/microsoft-teams-how-to-troubleshoot-microsoft-teams-part-2/

Advertisements

6 thoughts on “How to troubleshoot Microsoft Teams client logs

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: