SOLVED

Teams Room System Unable to Fetch Calendar after the update to 4.3.21.0

%3CLINGO-SUB%20id%3D%22lingo-sub-1063862%22%20slang%3D%22en-US%22%3ETeams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1063862%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20starting%20to%20get%20an%20issue%20after%20the%20Teams%20Room%20System%20Update%204.3.21.0.%20error%20on%20the%20display%20cannot%20fetch%20calendar%20(skype%20sign%20in%20is%20fine)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20did%20a%20trace%20and%20we%20don't%20see%20anything%20block%20from%20our%20environment%20to%20Microsoft.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20experiencing%20the%20same%20issue%3F%26nbsp%3B%20pretty%20sure%20because%20of%20the%20update%2C%20the%20rest%20of%20our%20teams%20room%20system%20with%20the%20older%20version%20is%20fine.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F161568i4864F9124BB5DE5F%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1063862%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%20Room%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERoom%20System%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20Room%20Systems%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1064987%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1064987%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295912%22%20target%3D%22_blank%22%3E%40AlexJr%3C%2FA%3E%26nbsp%3BWe%20have%20the%20same%20issue%20at%20a%20Government%20customer%20in%20Sweden%20after%20upgrade%20to%20version%204.3.21.0.%20Hope%20that%20Microsoft%20addresses%20this%20issue%20immediately%20or%20give%20us%20a%20workaround.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20customer%20uses%20Skype%20for%20Business%20Server%202015%20and%202019%20On-Premise%20as%20well%20as%20Exchange%20Server%202016%20On-Premise%20and%20everything%20worked%20fine%20until%20yesterday.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1066125%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1066125%22%20slang%3D%22en-US%22%3EThanks%2C%20let%20me%20know%20if%20you've%20any%20update%20from%20Microsoft.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1066522%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1066522%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295912%22%20target%3D%22_blank%22%3E%40AlexJr%3C%2FA%3E%26nbsp%3BI%20haven%E2%80%99t%20seen%20this%20on%20any%20of%20my%20units%2C%20but%20you%20mention%20that%20Skype%20signs%20in%20fine.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EDoes%20that%20mean%20that%20you%20are%20using%20the%20setting%20of%20Skype%20only%3F%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20my%20units%20I%20am%20complete%20O365%20for%20Teams%20(obviously)%2C%20Skype%20and%20Exchange.%20%26nbsp%3BStrange%20that%20it%20only%20happens%20since%20the%20update%2C%20but%20there%20are%20some%20things%20you%20can%20try.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20check%20your%20audit%20logs%20on%20the%20account%20and%20see%20if%20there%20might%20be%20an%20exception%20for%20authentication%20on%20the%20account%20that%20might%20help%20you%20track%20it%20down%20as%20well.%20%26nbsp%3BI%E2%80%99ve%20encountered%20it%20a%20few%20times%20and%20wrote%20some%20of%20the%20common%20causes%20about%20it%20%3CA%20href%3D%22https%3A%2F%2Fmedium.com%2F%40vaughanjamesr%2Fmicrosoft-teams-rooms-cannot-fetch-calendar-39f682666636%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EHere%3C%2FA%3E%26nbsp%3B.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20actually%20bring%20down%20the%20meeting%20info%20or%20does%20it%20just%20display%20the%20error%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068243%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068243%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295912%22%20target%3D%22_blank%22%3E%40AlexJr%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFixed%20in%20version%204.3.23.0%20that%20has%20gotten%20pushed%20to%20our%20devices.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068290%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068290%22%20slang%3D%22en-US%22%3EThank%20you%2C%20you%20are%20even%20faster%20than%20Microsoft%20itself%20in%20relaying%20the%20info%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3EGoing%20to%20check%20it%20out.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068295%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068295%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20insight.%20Our%20older%20devices%20are%20fine%2C%20the%20issue%20only%20affecting%20devices%20with%20latest%20version%204.3.21.%20It%20seems%20that%20Microsoft%20releasing%20a%20hot%20fix%20to%20address%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069410%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069410%22%20slang%3D%22en-US%22%3Ethe%204.3.23.0%20confirmed%20fixed%20the%20issue%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107749%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107749%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295912%22%20target%3D%22_blank%22%3E%40AlexJr%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20setup%20a%20new%20teams%20room%20and%20device%20and%20getting%20the%20same%20fetch%20calendar%20issue%20with%204.3.23%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eany%20ideas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1117366%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1117366%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F248613%22%20target%3D%22_blank%22%3E%40bjones96%3C%2FA%3E%26nbsp%3BI%20don't%20have%20any%20issue%20with%20the%20newer%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20check%3A%3C%2FP%3E%3CUL%3E%3CLI%3Ethe%20room%20mailbox%20is%20in%20O365%20(if%20you%20don't%20use%20exchange%202016)%2C%20if%20you've%20another%20teams%20room%20system%20try%20to%20login%20the%20room%20account%20to%20that%20working%20teams%20room%20to%20make%20sure%20that%20there%20is%20no%20issue%20with%20the%20account.%3C%2FLI%3E%3CLI%3Eit%20could%20be%20a%20proxy%20issue%20as%20well%20if%20this%20your%20first%20device%20deployment%20it's%20good%20to%20go%20through%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Froom-systems%2Fsrs-v2-prep%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Epreparation%20check%3C%2FA%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1118073%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Room%20System%20Unable%20to%20Fetch%20Calendar%20after%20the%20update%20to%204.3.21.0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1118073%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F295912%22%20target%3D%22_blank%22%3E%40AlexJr%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%20I've%20looked%20over%20this%20and%20all%20should%20be%20good.%20One%20thing%20i%20noticed%20is%20that%20the%20%22Meeting%20Room%22%20license%20we%20have%20doesn't%20include%20any%20mention%20of%20Exchange%20which%20is%20required.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20using%20the%20wrong%20license%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We are starting to get an issue after the Teams Room System Update 4.3.21.0. error on the display cannot fetch calendar (skype sign in is fine)

 

We did a trace and we don't see anything block from our environment to Microsoft. 

 

Anyone else experiencing the same issue?  pretty sure because of the update, the rest of our teams room system with the older version is fine. 

 

clipboard_image_0.png

10 Replies
Highlighted

@AlexJr We have the same issue at a Government customer in Sweden after upgrade to version 4.3.21.0. Hope that Microsoft addresses this issue immediately or give us a workaround.

This customer uses Skype for Business Server 2015 and 2019 On-Premise as well as Exchange Server 2016 On-Premise and everything worked fine until yesterday.

Highlighted
Thanks, let me know if you've any update from Microsoft.
Highlighted

@AlexJr I haven’t seen this on any of my units, but you mention that Skype signs in fine.  


Does that mean that you are using the setting of Skype only?  

 

For my units I am complete O365 for Teams (obviously), Skype and Exchange.  Strange that it only happens since the update, but there are some things you can try.

 

Maybe check your audit logs on the account and see if there might be an exception for authentication on the account that might help you track it down as well.  I’ve encountered it a few times and wrote some of the common causes about it Here .

 

Does it actually bring down the meeting info or does it just display the error?

 

 

 

Highlighted
Best Response confirmed by AlexJr (Occasional Contributor)
Solution

@AlexJr 

Fixed in version 4.3.23.0 that has gotten pushed to our devices.

 

Highlighted
Thank you, you are even faster than Microsoft itself in relaying the info :)

Going to check it out.
Highlighted
Thanks for the insight. Our older devices are fine, the issue only affecting devices with latest version 4.3.21. It seems that Microsoft releasing a hot fix to address this.
Highlighted
the 4.3.23.0 confirmed fixed the issue
Highlighted

@AlexJr 

I just setup a new teams room and device and getting the same fetch calendar issue with 4.3.23

 

any ideas

Highlighted

@bjones96 I don't have any issue with the newer version.

 

Please check:

  • the room mailbox is in O365 (if you don't use exchange 2016), if you've another teams room system try to login the room account to that working teams room to make sure that there is no issue with the account.
  • it could be a proxy issue as well if this your first device deployment it's good to go through the preparation check
Highlighted

@AlexJr 

Thanks. I've looked over this and all should be good. One thing i noticed is that the "Meeting Room" license we have doesn't include any mention of Exchange which is required.

 

Am I using the wrong license?