Forum Discussion
MS team room : Teams is currently experiencing an error
Our Microsoft team room update to window 11 IOT version. And some of the room show the error "Teams is currently experiencing an error. If the problem persists, please try restarting your device or talk to your administrator". It need to restart two times to resolve the issue. This is the first time we see this error, and have no such information can be search. May I know if other people is facing the same issue as us?
#Microsoft Teams room, #Activity, #Analytics
- I got the same error message after I imaged a new MTR PC to replace a current MTR PC! But I hit Settings on that error message screen on the new MTR PC and it stated "No room license found" under Room Licenses in About menu.
But this is something i never experienced or had to do and I have reimaged many MTR PCs and unenrolled licenses/readded licenses. But i tried this and it worked for me.
Go to Microsoft Teams admin center
Select Teams Rooms on Windows
I found the Teams Pro license not attached to the new PC
But found the Teams Pro license still assigned to the old MTR PC
I clicked on old MTR PC/Display name and removed the attached devices
I waited for couple minutes and restarted the new MTR PC and the Teams Pro license automatically got reassigned to the new MTR PC and logged me in.- On my side i had the same error and i believe this come from wrong credentials. I corrected the username of the account used and it connected well. The error message is too generic as we all seem to have different root causes.
- I also have this issue on both unit.
Tried to rerun the teams update didnt help.. Is the only way to rollback to windows 10? any other suggestion? When the firewall team went over the logs again... they found that the encryption was 1 way only.... they made it 2 ways and all was solved.
- <a href="https://www.siniyah-island-uae.com/"> Sobha Siniya Island</a> got it fixed and network is working correctly.
TimmyLeung0405 What worked for me was to set the network settings to private network, this allows the apps to communicate with the device in a private network. Try that and let me know!
- Also have this issue 8/20/24. Crestron UC with Dell 7080. All fw up to date. Only happens when logging in with the clients login credentials. ie-i can use another account and all is well.
Unit will reboot, login succeeds with client credentials, then crashes with this error after 3-5 minutes.- Did you solve it? I'm also having the same issue with Dell 7080
Not very helpful but ours fixed themselves after a couple of updates.
- Hello,
We are having the same issue in our org. Which is crazy its doesn't matter what Teams version or OS its on we are still seeing the same issue. Tried to update to the latest OS for both Teams & Windows no luck. Reinstalled Teams, remove/re-add to the domain no luck. Working with MS on this still no luck. Anyone have any luck with resolving? - I'm having the same issue on 4.19.X,
reboot done, firewall check done (nothing is being blocked), windows update done, account validation done, mfa not enable done....search done...
nothing so far. Hello, I am experiencing the same issue 04/01/24. it is random and occurs at different conference rooms
Did you or anyone find a resolution?
Thank You - Glenn
Arnoldas5 Maybe someone switched on a new conditional access rule for all accounts and forgot to exclude the "exclude list" (we did that once)
Or turned on MFA for everybody (we caught that faster)
Or Microsoft is reorganising security certificates in the background again (let's hope not...)
The sign-in errors died down eventually. Sign-in logs were not really helpful for us.
I found that resetting the password resolved the issue. In User sign-ins (non-interactive) I could see a number of failures as below. The password hadn't expired or been changed.
Sign-in error code50173Failure reasonThe provided grant has expired due to it being revoked, a fresh auth token is needed. The user might have changed or reset their password. The grant was issued on '{authTime}' and the TokensValidFrom date (before which tokens are not valid) for this user is '{validate}'.
