How to troubleshoot Microsoft Teams process logs

Last week in my first post about troubleshooting Microsoft Teams. I mentioned how to get the logs for the Microsoft Teams client. In this post I will look at the other logs in Microsoft Teams?

Are there other logs??

When you have a look at the background process of Microsoft Teams there is another Get logs option.

The logs in this  log are slightly different from the client logs:

[code lang=text]
Mon Aug 07 2017 08:58:25 GMT+0100 (GMT Daylight Time) <14256> — info — Clean up calling complete. Resuming window close
Mon Aug 07 2017 08:58:25 GMT+0100 (GMT Daylight Time) <14256> — info — Saved window state to {“x”:2046,”y”:150,”width”:1486,”height”:774,”isMaximized”:false,”isFullScreen”:false}
Mon Aug 07 2017 08:58:25 GMT+0100 (GMT Daylight Time) <14256> — info — Preventing app from exiting and minimizing.
Mon Aug 07 2017 08:58:28 GMT+0100 (GMT Daylight Time) <14256> — info — Is foreground set to true
Mon Aug 07 2017 08:58:28 GMT+0100 (GMT Daylight Time) <14256> — info — Is foreground set to true
Mon Aug 07 2017 08:58:30 GMT+0100 (GMT Daylight Time) <14256> — info — Saved window state to {“x”:2046,”y”:150,”width”:1486,”height”:774,”isMaximized”:true,”isFullScreen”:false}
Mon Aug 07 2017 08:58:30 GMT+0100 (GMT Daylight Time) <14256> — info — Sending clean up calling on window close.
Mon Aug 07 2017 08:58:31 GMT+0100 (GMT Daylight Time) <14256> — info — Is foreground set to false
Mon Aug 07 2017 08:58:31 GMT+0100 (GMT Daylight Time) <14256> — event — duration: 3.1679999828338623
name: desktop_foreground_duration
Mon Aug 07 2017 08:58:32 GMT+0100 (GMT Daylight Time) <14256> — info — Clean up calling complete. Resuming window close
Mon Aug 07 2017 08:58:32 GMT+0100 (GMT Daylight Time) <14256> — info — Saved window state to {“x”:2046,”y”:150,”width”:1486,”height”:774,”isMaximized”:true,”isFullScreen”:false}
Mon Aug 07 2017 08:58:32 GMT+0100 (GMT Daylight Time) <14256> — info — Preventing app from exiting and minimizing.
[/code]

As you can notice from the above section of the logs that I found these latest messages appear at the end of the log. So far almost all logs I’ve ever seen generated by Microsoft application are latest message at the top. This could become quite painful when the logs get larger.

Like with the client logs there are multiple log levels.

• info – Information only messages
• event – Each section within the log ends with an event level message giving the success or failure of the event.
• error – error messages

Some examples of error messages that I found is:

[code lang=text]
Thu Apr 20 2017 23:35:21 GMT+0100 (GMT Daylight Time) <363228> — info — Main window closed
Thu Apr 20 2017 23:35:21 GMT+0100 (GMT Daylight Time) <363228> — error — There are 1 open windows after main window closed, force closing all windows
Thu Apr 20 2017 23:35:21 GMT+0100 (GMT Daylight Time) <363228> — event — name: desktop_orphan_windows
count: 1
[/code]

[code lang=text]
Thu May 04 2017 15:37:27 GMT+0100 (GMT Daylight Time) <14892> — info — Hang tight! We’re getting you connected. diag:0
Thu May 04 2017 15:37:27 GMT+0100 (GMT Daylight Time) <14892> — info — adalsso:statusChanged to: Hang tight! We’re getting you connected.
Thu May 04 2017 15:37:27 GMT+0100 (GMT Daylight Time) <14892> — error — SSO: ssoerr – (status) Unable to get errCode. Err:Error: ADAL error: 0xCAA10001SSO: ssoerr – (status) Unable to get errorDesc. Err:Error: ADAL error: 0xCAA10001
Thu May 04 2017 15:37:27 GMT+0100 (GMT Daylight Time) <14892> — event — status: success
isLoggedOut: true
scenario: b1637139-c643-484f-89e6-35b21ee8ab9e
scenarioName: desktop_win_sso
name: desktop_win_sso
step: interaction_require
sequence: 6
delta: 39
scenarioDelta: 39
elapsed: 21529
Scenario.Name: desktop_win_sso
Scenario.Step: interaction_require
Scenario.Status: success
[/code]