Home

New Team Room..."Cannot Fetch Calendar" (Logitech Kit)

%3CLINGO-SUB%20id%3D%22lingo-sub-807525%22%20slang%3D%22en-US%22%3ENew%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-807525%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20finished%20setup%20of%20a%20new%20Teams%20Room%20using%20the%20Logitech%20Large%20Room%20system%20for%20teams%20(kit%20with%20Rally%20camera%2C%20TAP%20touch%20display%20and%20prebuilt%20PC).%20I%20followed%20exclusively%20the%20Microsoft%20deployment%20directions%20for%20office365%20online%20only%20(no%20on%20premise%20or%20hybrid%20exchange).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMeetings%2C%20calls%2C%20sharing%20ect%20all%20is%20working....with%20one%20exception.%20On%20the%20TAP%20display%20(connected%20to%20the%20teams%20room%20computer)%20it%20displays%20a%20cannot%20fetch%20calendar%20error%20after%20it%20logs%20into%20the%20team%20room%20account.%20However%20I%20do%20know%20the%20calendar%20works%20because%20if%20I%20sign%20into%20desktop%20teams%20on%20my%20own%20computer%20using%20the%20meeting%20room%20credentials%20it%20all%20work%2C%20I%20can%20see%20the%20room%20calendar%20entries%20ect.%20In%20addition%20it%20is%20auto%20accepting%20invites%20sent%20to%20it%20from%20organization%20users%20and%20I%20can%20see%20the%20room%20calendar%20in%20my%20outlook%20along%20with%20busy%20times%20ect.%20It%20simply%20cannot%20fetch%20calendar%20when%20logged%20in%20on%20the%20meeting%20room%20PC.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-807525%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-825597%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825597%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F393182%22%20target%3D%22_blank%22%3E%40cbot%3C%2FA%3EI%20have%20the%20same%20'Cannot%20Fetch%20Calendar'%20error.%26nbsp%3B%26nbsp%3B%20First%20some%20history....I%20was%20part%20of%20the%20SrSv2%20TAP%20and%20early%20on%20with%20Skype%20and%20Exchange%20on-prem...I%20also%20had%20the%20same%20calendar%20fetch%20issue.%26nbsp%3B%20It%20turned%20out%20back%20then%20that%20MSFT%20assumed%20that%20the%20SIP%20and%20UPN%20was%20the%20same%20but%20in%20our%20environment%20it%20isnt.%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Now%20fast%20fwd%20to%20the%20most%20recent%20calendar%20fetch%20issue.%26nbsp%3B%26nbsp%3B%20This%20issue%20reappeared%20after%20migrating%20the%20resource%20mbx%20to%20O365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20Im%20curious...does%20your%20SIP%20and%20UPN%20for%20the%20user%20account%20match%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDave%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-830327%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-830327%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F10291%22%20target%3D%22_blank%22%3E%40David%20Christensen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20as%20it%20turns%20out%20our%20problem%20was%20autodiscovery%20wasn't%20working.%20We%20had%20recently%20migrated%20our%20DNS%20management%20to%20s%20new%20service%20and%20actually%20all%20of%20the%20required%20DNS%20records%20for%20Office365%20were%20missing%20other%20than%20the%20MX%20records.%20After%20we%20setup%20the%20DNS%20records%20(which%20include%20autodiscovery%20service)%20the%20calendar%20started%20working%20working%20as%20expected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-839962%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-839962%22%20slang%3D%22en-US%22%3EI%20just%20set%20up%20our%20first%20Logitech%20Smart%20Dock%20Teams%20console%20and%20I%20followed%20the%20account%20creation%20instructions%20and%20everything%20is%20working%20except%20I%20too%20am%20getting%20the%20Cannot%20fetch%20calendar%20error.%20I%20have%20nothing%20on%20premises.%20Everything%20is%20in%20the%20cloud.%20How%20did%20you%20know%20it%20was%20a%20auto%20discover%20issue%3F%20If%20I%20do%20a%20nslookup%20on%20the%20console%20for%20the%20auto%20discover%20record%20for%20my%20domain%20it%20seems%20to%20resolve%20it%20just%20fine.%20I%20have%20noticed%20that%20it%20seems%20to%20return%20the%20ipv6%20address%20first%20before%20the%20ipv4%20is%20address%2C%20do%20you%20think%20this%20is%20a%20problem%3F%20Really%20frustrating.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1102411%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1102411%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8254%22%20target%3D%22_blank%22%3E%40Ricky%20Isbell%3C%2FA%3E%26nbsp%3Bwe%20are%20having%20the%20same%20issue.%20how%20did%20you%20resolve%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1102757%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1102757%22%20slang%3D%22en-US%22%3EYou%20have%20to%20make%20sure%20the%20account%20you%20are%20using%20for%20the%20room%20still%20has%20basic%20authentication%20enabled%20for%20the%20account.%20Before%20I%20installed%20this%20room%2C%20I%20had%20basic%20authentication%20turned%20off%20by%20default%20and%20was%20using%20modern%20authentication%20for%20all%20of%20my%20users.%20Apparently%20the%20teams%20room%20software%20will%20only%20use%20basic%20authentication%20for%20connection%20to%20the%20mailbox%20of%20the%20room.%20So%20check%20to%20make%20sure%20that%20basic%20authentication%20is%20turned%20on%20for%20your%20room%20mailbox%20account.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1102761%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1102761%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20info.%20How%20do%20I%20go%20about%20changing%20this%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20your%20help!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1105721%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1105721%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8254%22%20target%3D%22_blank%22%3E%40Ricky%20Isbell%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%20for%20the%20info.%20How%20do%20I%20go%20about%20changing%20this%3F%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EThanks%20for%20your%20help!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1105725%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1105725%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%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fpdhewaju.com.np%2F2018%2F10%2F31%2Fenabling-basic-authentication-on-exchange-online%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpdhewaju.com.np%2F2018%2F10%2F31%2Fenabling-basic-authentication-on-exchange-online%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1105818%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1105818%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8254%22%20target%3D%22_blank%22%3E%40Ricky%20Isbell%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERicky%20thanks%20for%20this...i%20have%20done%20this%20and%20get%20the%20message%20from%20Powershell%3A%20%22The%20command%20completed%20successfully%20but%20no%20settings%20of%20'MM%20Board%20Room'%20have%20been%20modified.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20doing%20something%20wrong%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107964%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107964%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20faced%20same%20issue%20originally%2C%20but%20resolved%20after%20enabling%20basic%20auth%20for%20exchange%20just%20like%20you%20mentioned.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20now%2C%20devices%20showing%20same%20%22cannot%20fetch%20calendar%22%20message%20randomly%20on%20devices%3B%20sometimes%20device%20restart%20clears%20the%20message%20and%20able%20to%20get%20meeting%20invited%2C%20but%20it%20again%20appears%20randomly%20after%20some%20time%20(%20or%20after%20few%20days%20in%20some%20cases).%3C%2FP%3E%3CP%3EAny%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1199197%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1199197%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20experiencing%20the%20same%20issue%20on%20HP%20Elite%20Slice%20systems%20using%20the%20Teams%20(Skype%3F)%20Room%20System.%3C%2FP%3E%3CP%3EPer%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8254%22%20target%3D%22_blank%22%3E%40Ricky%20Isbell%3C%2FA%3E%20's%20suggestion%2C%20I%20created%20an%20Authentication%20Policy%20in%20Exchange%20Online%20that%20allows%20for%20all%20forms%20of%20Basic%20Authentication%20and%20I'm%20still%20having%20the%20problem.%3C%2FP%3E%3CP%3EAm%20I%20enabling%20Basic%20Authentication%20the%20right%20way%20or%20doing%20something%20wrong%3F%20I'd%20be%20happy%20to%20help%20any%20way%20that%20I%20can.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1199219%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1199219%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386399%22%20target%3D%22_blank%22%3E%40rodgcw%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20fought%20with%20this%20and%20messed%20around%20with%20crazy%20auth%20policies%20and%20made%20no%20difference.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eyou%20will%20need%20to%20jump%20over%20to%20the%20admin%20side%20of%20the%20MTR%2FSRS%20device%20and%20change%20the%20DNS%20on%20the%20network%20adapters%20to%20an%20alternate%20DNS.%20easiest%20to%20use%20googles.%208.8.8.8.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethis%20is%20the%20thread%20that%20helped%20me.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fskype-for-business-it-pro%2Fteams-room-quot-cannot-fetch-calendar-quot%2Fm-p%2F1183063%23M5847%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fskype-for-business-it-pro%2Fteams-room-quot-cannot-fetch-calendar-quot%2Fm-p%2F1183063%23M5847%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethat%20worked%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1199450%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1199450%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%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20quick%20reply%2C%20man!%3C%2FP%3E%3CP%3EDid%20that%2C%20still%20no%20dice.%20Also%20noticed%20that%20Hyper-V%20was%20enabled%20for%20some%20reason%3F%20Disabled%20that%20feature%20and%20still%20receiving%20the%20same%20error%20message...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1200642%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1200642%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386399%22%20target%3D%22_blank%22%3E%40rodgcw%3C%2FA%3E%26nbsp%3Bso%20you%20set%20the%20dns%20as%208.8.8.8%3F%20what%20liscence%20are%20you%20using%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ealso%20what%20user%20name%20are%20you%20using%20to%20get%20in%3F%20also%20make%20sure%20MFA%20is%20disabled%20and%20your%20not%20using%20an%20app%20password.%20all%20you%20should%20have%20in%20the%20MTR%20setting%20is%20a%20user%20name%20and%20password%20the%20domain%20etc%20should%20be%20blank.(this%20worked%20for%20us)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1201313%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1201313%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%3EYes.%20Using%20the%20Microsoft%20Teams%20Room%20License.%3C%2FP%3E%3CUL%3E%3CLI%3ENo%20MFA.%3C%2FLI%3E%3CLI%3EUsername%20and%20email%20is%20the%20account's%20UPN.%3C%2FLI%3E%3CLI%3ETested%20with%20the%20domain%20blank%20and%20with%20it%20filled%20in.%20Unsuccessful%20both%20ways.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1201315%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1201315%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F386399%22%20target%3D%22_blank%22%3E%40rodgcw%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Edid%20you%20create%20the%20room%20etc%20via%20powershell%20or%20admin%20centre%20online%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1204695%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1204695%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%3EThey%20were%20migrated%20from%20our%20on-prem%20Exchange%20Server%20to%20Exchange%20Online.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205128%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205128%22%20slang%3D%22en-US%22%3EI%20would%20be%20inclined%20to%20recreate%20them%20to%20be%20sure%20that%20nothing%20was%20missed%20in%20the%20flip%20over.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1218049%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Team%20Room...%22Cannot%20Fetch%20Calendar%22%20(Logitech%20Kit)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1218049%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%3ESolved.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETurns%20out%20it%20wasn't%20my%20configuration%20of%20the%20accts%20or%20the%20device%2C%20but%20that%20the%20autodiscover%20was%20improperly%20configured%20by%20one%20of%20our%20sys%20admins.%20They've%20reconfigured%20it%20and%20we're%20up%20and%20running.%20Thanks%20for%20your%20help!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

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.

19 Replies
Highlighted

@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

Highlighted

@David Christensen 

 

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.

Highlighted
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.
Highlighted

@Ricky Isbell we are having the same issue. how did you resolve it?

Highlighted
You have to make sure the account you are using for the room still has basic authentication enabled for the account. Before I installed this room, I had basic authentication turned off by default and was using modern authentication for all of my users. Apparently the teams room software will only use basic authentication for connection to the mailbox of the room. So check to make sure that basic authentication is turned on for your room mailbox account.
Highlighted
Thanks for the info. How do I go about changing this?

Thanks for your help!
Highlighted

@Ricky Isbell 

Thanks for the info. How do I go about changing this?

Thanks for your help!

Highlighted

@Ricky Isbell 

Ricky thanks for this...i have done this and get the message from Powershell: "The command completed successfully but no settings of 'MM Board Room' have been modified."

 

Am I doing something wrong?

 

Thanks again.

Highlighted

We faced same issue originally, but resolved after enabling basic auth for exchange just like you mentioned. 

 

But now, devices showing same "cannot fetch calendar" message randomly on devices; sometimes device restart clears the message and able to get meeting invited, but it again appears randomly after some time ( or after few days in some cases).

Any thoughts?

Highlighted

I am experiencing the same issue on HP Elite Slice systems using the Teams (Skype?) Room System.

Per@Ricky Isbell '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.

Highlighted

@rodgcw 

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-calend...

 

that worked for me.

Highlighted

@bjones96 

Thanks for the quick reply, man!

Did that, still no dice. Also noticed that Hyper-V was enabled for some reason? Disabled that feature and still receiving the same error message...

Highlighted

@rodgcw so you set the dns as 8.8.8.8? what liscence are you using?

 

also what user name are you using to get in? also make sure MFA is disabled and your not using an app password. all you should have in the MTR setting is a user name and password the domain etc should be blank.(this worked for us)

Highlighted

@bjones96Yes. Using the Microsoft Teams Room License.

  • No MFA.
  • Username and email is the account's UPN.
  • Tested with the domain blank and with it filled in. Unsuccessful both ways.
Highlighted

@rodgcw 

did you create the room etc via powershell or admin centre online?

Highlighted

@bjones96They were migrated from our on-prem Exchange Server to Exchange Online.

Highlighted
I would be inclined to recreate them to be sure that nothing was missed in the flip over.
Highlighted

@bjones96Solved.

 

Turns out it wasn't my configuration of the accts or the device, but that the autodiscover was improperly configured by one of our sys admins. They've reconfigured it and we're up and running. Thanks for your help!