Microsoft Teams hangs when not connected to server

[Makosuke]

Co-worker has been having trouble with Microsoft Teams, and after some troubleshooting we narrowed down that if he's connected to our fileserver it's fine, and if he's not it beachballs as soon as he opens it. It'll also apparently hang if the server gets connected while in a meeting.

It seems obvious that Teams is trying to access a file or directory on the server, and chokes if the server isn't there.

Problem: I can't seem to find anywhere in my own same-version Teams' preferences where it has any file paths identified. So what the heck is it doing, and how the heck do I reset it so it looks at the local drive like it's supposed to?

He's already tried reinstalling it, that didn't help, and is working from home so I don't have direct access which makes it harder to dig around and delete prefs or whatnot. He's apparently fine just using it that way, but I'm not--the mystery is bugging me.

Anybody else run into this?

 

[Slartibart]

Make sure the user is logged out from Teams.
Make sure that Teams is not started automatically when booting up the Mac.
Then clear Library -> Application Support -> Teams and the Library -> Caches -> com.microsoft.teams folder.
Start Teams. Login. (Hopefully 😎).

 

[Makosuke]

Thanks for the suggestion. Basically, the nuclear option.

One rather hopes that'll do it, although I'm still left puzzling how Teams managed to end up with an internal path pointing to a mounted volume.

 

[Slartibart]

Thanks for the suggestion. Basically, the nuclear option.

not really. This deletes just files Teams will copy there if not found on startup. But damaged files in the e.g. Application Support can infamously interfere with the user login process.

One rather hopes that'll do it, although I'm still left puzzling how Teams managed to end up with an internal path pointing to a mounted volume.

As in diskimage? Well that happens when Teams is executed from one. I thought thats a problem for some older version though…

 

[Makosuke]

As in diskimage? Well that happens when Teams is executed from one. I thought thats a problem for some older version though…

Mounted volume as in network mount—a SMB share.

Although if executing Teams from a disk image was known to cause problems, I wonder if the user launched it directly off the share to start with and that hosed some internal pref path…