Skype Room System - Cannot fetch calendar

%3CLINGO-SUB%20id%3D%22lingo-sub-307915%22%20slang%3D%22en-US%22%3ESkype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-307915%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20about%20a%20dozen%20Skype%20Room%20System%20units%20(both%20the%20Surface%20and%20Lenovo%20Hub%20500)%20deployed%20in%20our%20environment%2C%20installed%20with%20SRS%20version%204.0.64.0%2C%20Windows%20version%2010.0.16299.785%20and%20they%20all%20have%20the%20error%20message%20%22cannot%20fetch%20calendar%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ESome%20background%20history%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EThis%20message%20appeared%20during%20a%20Exchange%20on-prem%20-%26gt%3B%20cloud%20migration%2C%20and%20was%20expected%20because%20of%20our%20autodiscover%20records%20still%20pointing%20to%20the%20on-prem%20server.%20It%20was%20also%20expected%20that%20it%20would%20be%20fixed%20by%20itself%20once%20we%20updated%20our%20autodiscover%20records%20to%20point%20to%20the%20cloud%2C%20but%20unfortunately%20this%20did%20not%20solve%20the%20problem.%20We%20are%20currently%20running%20on%20a%20Skype%20for%20Business%202013%20server%20on-prem%2C%20and%20Exchange%20Online%20(hybrid)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ETroubleshooting%3A%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3EI%20first%20thought%20this%20was%20autodiscover%20related%2C%20because%20of%20what%20i%20mentioned%20above.%20I%20have%20tried%20to%20manually%20add%20the%20cloud%20autodiscover%20server%20to%20the%20hosts%20file%20a%20few%20of%20the%20systems%2C%20that%20did%20not%20help.%26nbsp%3B%3C%2FLI%3E%3CLI%3EFurther%20step%20was%20checking%20that%20the%20licensing%20in%20Office%20365%20is%20ok%2C%20all%20accounts%20have%20E3%20license.%26nbsp%3B%3C%2FLI%3E%3CLI%3EInstalled%20Office%20365%20proplus%20on%20a%20few%20of%20the%20systems%2C%20to%20check%20if%20sign-in%20to%20to%20a%20normal%20desktop%20version%20of%20SFB%20worked%20and%20it%20did.%20The%20SFB%20client%20read%20the%20calendar%20and%20everything%20worked%20as%20it%20should.%26nbsp%3B%3C%2FLI%3E%3CLI%3ECreated%20a%20new%20meeting%20room%20account%20in%20the%20cloud%3C%2FLI%3E%3CLI%3ERe-installed%20one%20of%20the%20systems%20(worth%20a%20shot)%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3CP%3ENow%2C%20if%20i%20try%20with%20a%20room%20mailbox%20account%20only%20existing%20on%20our%20on-prem%20server%2C%20it%20works.%20I%20have%20looked%20through%20many%20SRS%20articles%20here%20with%20the%20same%20problem%2C%20and%20i%20noticed%20someone%20mentioned%20that%20it%20was%20ADFS%20related%2C%20but%20i%20am%20not%20sure%20where%20to%20look.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20this%20point%20i%20am%20lost%2C%20and%20am%20hoping%20one%20of%20you%20brilliant%20people%20could%20help%20me%20out.%20Also%2C%20happy%20new%20year!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-307915%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20Room%20Systems%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394634%22%20slang%3D%22en-US%22%3ERE%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394634%22%20slang%3D%22en-US%22%3Eperhaps%20caused%20by%20the%20proxy%3F%20take%20a%20look%20at%20this%20documentation%20under%20proxy%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fplan-your-deployment%2Fclients-and-devices%2Fsrs-v2-prep%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fplan-your-deployment%2Fclients-and-devices%2Fsrs-v2-prep%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394597%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394597%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F210603%22%20target%3D%22_blank%22%3E%40Knut%20Martin%20Gabrielsen%3C%2FA%3E%26nbsp%3BSorry%20for%20the%20late%20response.%20Not%20in%20any%20other%20way%20than%20creating%20new%20meeting%20rooms%2C%20per%20now%20there%20is%20no%20way%20to%20re-use%20our%20old%20ones.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-376788%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-376788%22%20slang%3D%22en-US%22%3EDid%20you%20manage%20to%20solve%20the%20calendar%20problem%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331737%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331737%22%20slang%3D%22en-US%22%3EWe%20did%20configure%20SFB%20hybrid%20and%20moved%20one%20of%20the%20SRS%20meeting%20room%20accounts%20to%20the%20cloud%2C%20and%20that%20have%20brought%20the%20Join%20meetings%20button%20back.%20However%2C%20it%20is%20greyed%20out%20and%20there%20is%20a%20constant%20%22Sign-in%22%20circle%20spinning%20on%20the%20screen%2C%20so%20we%20are%20not%20100%25%20operational%20again.%20Will%20post%20an%20update%20here%20when%20i%20have%20one%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331735%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331735%22%20slang%3D%22en-US%22%3ESame%20here%2C%20please%20post%20if%20you%20find%20a%20solution%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737613%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737613%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F259470%22%20target%3D%22_blank%22%3E%40MarcusMoen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20find%20a%20solution%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20use%20a%20Logitech%20SMARTDOCK%20with%20a%20Surface%206%20Pro.%3C%2FP%3E%3CP%3EWin1803%20and%20SRS%20v2%20Version%204.0.0.85%20April%202019%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Exchange%20hybrid%3C%2FP%3E%3CP%3E-%20Skype%20f.%20Business%20onPremise%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESIP%20works%2C%20but%20they%20don%20t%20fetch%20the%20calendar.%3C%2FP%3E%3CP%3EWe%20have%20use%203%20different%20Accounts%3C%2FP%3E%3CP%3E-%20Exchange%20onPremise%3C%2FP%3E%3CP%3E-%20Exchange%20Online%20User%20Account%3C%2FP%3E%3CP%3E-%20Exchange%20Online%20Ressource%20Account%20with%20license%20for%20the%20Room%20System%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20i%20log%20on%20the%20local%20Admin%20Account%20and%20install%20a%20Offfice%20365%2C%20all%20works%20fine%20(Skype%20f%20Business%20login%20and%20Outlook)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20have%20also%20installed%20the%20srs%20v2%20system%20on%20the%20local%20Account%20on%20srs%20%2C%20but%20it%20have%20the%20same%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20that%20a%20modern%20authentication%20problem%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20Regards%3C%2FP%3E%3CP%3EStefan%3C%2FP%3E%3CP%3E%26nbsp%3B%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-968803%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-968803%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270567%22%20target%3D%22_blank%22%3E%40Stefan_Koch_AEB%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20us%2C%20it%20was%20the%20modern%20authentication.%20Once%20we%20allowed%20basic%20auth%2C%20it%20works!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-982865%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-982865%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI%20did%20find%20that%20configuring%20DHCP%20option%20252%20(Web%20Proxy%20Auto%20Discover%2C%20WPAD)%20with%20the%20full%20URL%20to%20my%20organisation's%20Proxy%20Auto-Config%20(PAC)%20file%20resolved%20this%20in%20our%20case.%20Since%20we're%20using%20a%20local%2C%20non-domain%20account%20on%20the%20SRS%2FMTR%20device%2C%20it%20would%20have%20been%20too%20difficult%20to%20configure%20the%20PAC%20through%20another%20method%20such%20as%20a%20script.%20Conveniently%2C%20our%20cloud%20proxy%20provider%20supports%20forwarding%20requests%20to%20Office%20365%2FExchange%20Online%20without%20authentication%20so%20using%20the%20local%20account%20didn't%20pose%20any%20issue%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E(Copied%20my%20reply%20from%20a%20post%20on%20another%20conversation)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1004222%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004222%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F259470%22%20target%3D%22_blank%22%3E%40MarcusMoen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Marcus%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20a%20similiar%20issue%20and%20found%20that%20the%20on-prem%20user%20object%20password%20had%20expired.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETry%20setting%20a%20new%20password%20and%20setting%20the%20password%20to%20never%20expire.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ergds%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBrenton%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107950%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20-%20Cannot%20fetch%20calendar%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107950%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20using%20Skype%20for%20business%20online%2C%20with%20)365%20online%2C%20accounts%20are%20sync%20with%20local%20AD%20(%20and%20using%20Okta%20).%20We%20had%20hard-on%20%22cannot%20fetch%20calendar%22%20message%20at%20the%20beginning%2C%20but%20it%20was%20cleared%20after%20enabling%20basic%20Auth%20for%20exchange%20(%20we%20had%20basic%20auth%20disabled%20for%20our%20tenant).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20now%20all%20devices%20showing%20%22cannot%20fetch%20calendar%22%20message%20intermittently.%20Upon%20device%20restart%20%2C%20massage%20go%20away%20(sometime)%2C%20but%20appears%20randomly%20again.%3C%2FP%3E%3CP%3EWe%20have%20direct%20connection%20to%20internet%20(%20no%20proxy)%20via%20firewall.%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20thought%20%3F%3C%2FP%3E%3CP%3EThanks%2C%20Nick.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

We have a about a dozen Skype Room System units (both the Surface and Lenovo Hub 500) deployed in our environment, installed with SRS version 4.0.64.0, Windows version 10.0.16299.785 and they all have the error message "cannot fetch calendar".

 

Some background history:

This message appeared during a Exchange on-prem -> cloud migration, and was expected because of our autodiscover records still pointing to the on-prem server. It was also expected that it would be fixed by itself once we updated our autodiscover records to point to the cloud, but unfortunately this did not solve the problem. We are currently running on a Skype for Business 2013 server on-prem, and Exchange Online (hybrid)

 

Troubleshooting: 

  • I first thought this was autodiscover related, because of what i mentioned above. I have tried to manually add the cloud autodiscover server to the hosts file a few of the systems, that did not help. 
  • Further step was checking that the licensing in Office 365 is ok, all accounts have E3 license. 
  • Installed Office 365 proplus on a few of the systems, to check if sign-in to to a normal desktop version of SFB worked and it did. The SFB client read the calendar and everything worked as it should. 
  • Created a new meeting room account in the cloud
  • Re-installed one of the systems (worth a shot) 

Now, if i try with a room mailbox account only existing on our on-prem server, it works. I have looked through many SRS articles here with the same problem, and i noticed someone mentioned that it was ADFS related, but i am not sure where to look.

 

At this point i am lost, and am hoping one of you brilliant people could help me out. Also, happy new year! 

10 Replies
Same here, please post if you find a solution
We did configure SFB hybrid and moved one of the SRS meeting room accounts to the cloud, and that have brought the Join meetings button back. However, it is greyed out and there is a constant "Sign-in" circle spinning on the screen, so we are not 100% operational again. Will post an update here when i have one
Did you manage to solve the calendar problem?

@Knut Martin Gabrielsen Sorry for the late response. Not in any other way than creating new meeting rooms, per now there is no way to re-use our old ones. 

@MarcusMoen 

Did you find a solution?

 

We use a Logitech SMARTDOCK with a Surface 6 Pro.

Win1803 and SRS v2 Version 4.0.0.85 April 2019

 

- Exchange hybrid

- Skype f. Business onPremise

 

SIP works, but they don t fetch the calendar.

We have use 3 different Accounts

- Exchange onPremise

- Exchange Online User Account

- Exchange Online Ressource Account with license for the Room System

 

When i log on the local Admin Account and install a Offfice 365, all works fine (Skype f Business login and Outlook)

 

i have also installed the srs v2 system on the local Account on srs , but it have the same problem.

 

Is that a modern authentication problem? 

 

Kind Regards

Stefan

 

 

 

 

@Stefan_Koch_AEB 

 

For us, it was the modern authentication. Once we allowed basic auth, it works!

I did find that configuring DHCP option 252 (Web Proxy Auto Discover, WPAD) with the full URL to my organisation's Proxy Auto-Config (PAC) file resolved this in our case. Since we're using a local, non-domain account on the SRS/MTR device, it would have been too difficult to configure the PAC through another method such as a script. Conveniently, our cloud proxy provider supports forwarding requests to Office 365/Exchange Online without authentication so using the local account didn't pose any issue

 

(Copied my reply from a post on another conversation)

@MarcusMoen 

 

Hi Marcus,

 

I had a similiar issue and found that the on-prem user object password had expired. 

 

Try setting a new password and setting the password to never expire.

 

rgds

 

Brenton

We are using Skype for business online, with )365 online, accounts are sync with local AD ( and using Okta ). We had hard-on "cannot fetch calendar" message at the beginning, but it was cleared after enabling basic Auth for exchange ( we had basic auth disabled for our tenant). 

 

But now all devices showing "cannot fetch calendar" message intermittently. Upon device restart , massage go away (sometime), but appears randomly again.

We have direct connection to internet ( no proxy) via firewall. 

Any thought ?

Thanks, Nick.