Apr 13 2020 10:53 PM
Apr 13 2020 10:53 PM
A member of my team is having an issue opening the MS Teams (Mac) app on her iMac (identical to mine).
We deleted the cache files, then associated files, and re-installed Teams before posting this.
Basically, when she opens MS Teams, she gets the "spinning wheel" for about a minute. At the end of the minute, we get the OSX "Cannot connect to Server xxx.xxx.x.x", where x's are our local server that we currently do not have access to (working from home). I have ALSO tried disabling the NIC for this device.
We cannot locate ANYTHING in Teams that may be looking for this IP address, even shortcuts in chats.
I have the log file and can't see anything clearly out of order.
Nov 03 2020 01:31 AM
I have the same problem with an user with the latest Catalina update. Did you ever solve this problem?
Nov 05 2020 11:26 PM
@Matt_1975 Greetings Matt,
The problem for me was that before launching Microsoft Teams, the shared folders connected to the Mac was forced to be online. After a lot of troubleshooting my problem was solved by deleting the shared folders on the Mac, thereafter Teams could start normally.
Really wacky problem/solution though...
Nov 19 2020 03:23 AM
@LinusKarlsson thanks, how do you delete shared folders? or which shared folders!
Nov 19 2020 03:28 AM
Nov 19 2020 04:51 AM
Earlier this year I attached a shared folder to the MAC, these shared folders can be found at users and group if I remember correctly.
Nov 23 2020 09:09 AM
@LinusKarlsson sorry users and groups where? in Microsoft 365? Are you clear that it's ONLY when starting Teams that it hangs for us - eventually asking for this server.
ie not when the user logs into the mac, as that would try and and mount a volume if it was in the users & groups users startup items but it's not present, the machine operates normally unless we try to use Teams.
Therefore as I mentioned it's Teams asking for this server.
Feb 09 2021 11:05 AM
@MattPetersen Some issue here. I thought I was alone.
What's worse is I added a new Team -- and now I have to wait for it to try to connect to the server TWICE. Frustrating.
Mar 09 2021 07:10 AM
@DrN8PhD I have the exact same issue. Teams has decided that whenever I open or close it, it cannot comply until it mounts a specific network share that I have. It's a NAS device with a folder called "backup".
With Teams closed, I unmount Backup. Open Teams, and Teams causes the volume to be mounted before opening.
With teams open, I unmount Backup. Quit Teams, and Teams causes the volume to be mounted before closing.
When I am on my work VPN they block access to my Backup volume. This means that I have to wait for Teams to time out attempting to mount it whenever I open or close it.
Mar 21 2021 11:23 PM
Same here: MacBook Pro, all software up to date on Big Sur. Problem persisted since Catalina.
It waits for two (!) NAS shares to mount (one regular share and one Time machine share); works per se quite fast. But as mobile user, I am working in different places. And whenever I am outside my home network, I also have to wait for the process to time out.
This is very annoying when you have someone on the phone "...let me pull up teams real quick and have a look..."
All my data concerning work/TEAMs are on sharepoint, I access them via TEAMs or OneDrive. TEAMs has no business reading or writing on my NAS-shares and therefore should not have to wait until these are mounted.
Mar 22 2021 05:58 AM
Mar 22 2021 06:07 AM
@amd_andy I did. I scheduled a session with a tech and demonstrated the issue to him. I sent him console logs, and even provided a wireshark capture of the networking. He is currently sending me daily emails to let me know how things are going. So far basically none of the devs have had time to look at it, but at least he keeps giving me updates (making me think it won't get lost).
Mar 22 2021 06:13 AM
Apr 10 2021 01:47 AM
Apr 10 2021 11:59 AM
Apr 12 2021 01:52 AM
@LawsonCulverthanks for reverting! I am facing the issue too, and wanted to check if they are still working on debugging it.
Apr 22 2021 07:42 AM
@MattPetersen i have the same issue. Teams keeps on looking for a volume that doesn't exist anymore. Tried to reinstall teams entirely - no effect. A few months ago it tried to mount it once, now I have to wait until THREE timeouts before I can use Teams - very frustrating
Apr 22 2021 09:35 PM
@Ronald_Lange: the 1->3 transition is something I experienced too: when I installed teams, I had no remote drives mounted, all was fine. Once I mounted a remote drive, I started getting this timeout once while launching (I don't remember if it would wait while quitting too). Now, I have to wait for three timeouts before teams launches. I have not tried uninstall / reinstall, an "annoying but limping along" installation of teams currently holds more value than not having teams at all.