Forum Discussion

MarcusMoen's avatar
MarcusMoen
Copper Contributor
Jan 02, 2019

Skype Room System - Cannot fetch calendar

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! 

Skype for Business
Skype Room Systems

10 Replies

  • bchatch's avatar
    bchatch
    Copper Contributor
    Nov 13, 2019

    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

    • NickK330's avatar
      NickK330
      Copper Contributor
      Jan 14, 2020

      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.

  • ahorvat's avatar
    ahorvat
    Copper Contributor
    Nov 05, 2019

    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)

  • AlexJr's avatar
    AlexJr
    Copper Contributor
    Apr 04, 2019
    perhaps caused by the proxy? take a look at this documentation under proxy https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/clients-and-devices/srs-v2-prep
    • MarcusMoen's avatar
      MarcusMoen
      Copper Contributor
      Feb 06, 2019
      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

Resources