Forum Discussion
New Team Room..."Cannot Fetch Calendar" (Logitech Kit)
Just finished setup of a new Teams Room using the Logitech Large Room system for teams (kit with Rally camera, TAP touch display and prebuilt PC). I followed exclusively the Microsoft deployment directions for office365 online only (no on premise or hybrid exchange).
Meetings, calls, sharing ect all is working....with one exception. On the TAP display (connected to the teams room computer) it displays a cannot fetch calendar error after it logs into the team room account. However I do know the calendar works because if I sign into desktop teams on my own computer using the meeting room credentials it all work, I can see the room calendar entries ect. In addition it is auto accepting invites sent to it from organization users and I can see the room calendar in my outlook along with busy times ect. It simply cannot fetch calendar when logged in on the meeting room PC.
It was a simple fix for us. We had to go to the Teams Room tablet device, go to settings, then under settings there was a small toggle switch to enable Modern Authentication, turned that on and restarted and it just worked.
Hello, we have 2 Logitech Rally + Tap rooms connected to a Exchange on-premise server for at least 2 years.
The rooms use modern authentication. Logitech software is up-to-date.
The "cannot fetch calendar" appeared this week.
I deactivated the modern authentication and it resolved the problem for both rooms.
It's strange that I had to deactivate modern authentication that worked for more than 2 years, and that rooms in other companies need to activate modern authentication to resolve the problem.- techfortune thank you for this simple fix! i have been sprawling and looking all over this community to get the simple fixed answer.
And to anyone marking content as the best answer, this is sort of the best answer and the fix for the simple "catch fetch Calendar" issue
I am experiencing the same issue on HP Elite Slice systems using the Teams (Skype?) Room System.
Perrickyisbell 's suggestion, I created an Authentication Policy in Exchange Online that allows for all forms of Basic Authentication and I'm still having the problem.
Am I enabling Basic Authentication the right way or doing something wrong? I'd be happy to help any way that I can.
i fought with this and messed around with crazy auth policies and made no difference.
you will need to jump over to the admin side of the MTR/SRS device and change the DNS on the network adapters to an alternate DNS. easiest to use googles. 8.8.8.8.
this is the thread that helped me. https://techcommunity.microsoft.com/t5/skype-for-business-it-pro/teams-room-quot-cannot-fetch-calendar-quot/m-p/1183063#M5847
that worked for me.
cbotI have the same 'Cannot Fetch Calendar' error. First some history....I was part of the SrSv2 TAP and early on with Skype and Exchange on-prem...I also had the same calendar fetch issue. It turned out back then that MSFT assumed that the SIP and UPN was the same but in our environment it isnt. Now fast fwd to the most recent calendar fetch issue. This issue reappeared after migrating the resource mbx to O365.
So Im curious...does your SIP and UPN for the user account match?
Dave
So as it turns out our problem was autodiscovery wasn't working. We had recently migrated our DNS management to s new service and actually all of the required DNS records for Office365 were missing other than the MX records. After we setup the DNS records (which include autodiscovery service) the calendar started working working as expected.
- I just set up our first Logitech Smart Dock Teams console and I followed the account creation instructions and everything is working except I too am getting the Cannot fetch calendar error. I have nothing on premises. Everything is in the cloud. How did you know it was a auto discover issue? If I do a nslookup on the console for the auto discover record for my domain it seems to resolve it just fine. I have noticed that it seems to return the ipv6 address first before the ipv4 is address, do you think this is a problem? Really frustrating.
