SOLVED

SRS Calendar Issues

%3CLINGO-SUB%20id%3D%22lingo-sub-164899%22%20slang%3D%22en-US%22%3ESRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-164899%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I'm%20wondering%20if%20anyone%20else%20has%20run%20into%20the%20%22cannot%20fetch%20calendar%22%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20just%20got%20a%20Logitech%20Smartdock%20and%20everything%20works%20fine%20except%20that%20you%20cant%20see%20the%20meetings%20on%20the%20dock.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-164899%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConferencing-Meeting%20Join%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301466%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301466%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20working%20on%20this%20issue%20for%20a%20number%20of%20weeks%20and%20found%20a%20specific%20cause%20and%20solution%20in%20my%20case.%26nbsp%3B%20From%20experience%20working%20on%20this%20error%20I%20think%20it's%20important%20to%20note%20that%20%22Cannot%20fetch%20calendar%22%20seems%20to%20be%20a%20generic%20%22catch%20all%22%20error.%26nbsp%3B%20SRSv2%20is%20telling%20you%20it%20can't%20get%20the%20calendar%20information%20and%20the%20cause%20can%20be%20any%20number%20of%20different%20things%26nbsp%3Blike%20Autodiscover%20or%20account%20config%20as%20you%20can%20read%20in%20other%20posts%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20case%2C%20the%20network%20team%20at%20my%20company%20figured%20out%20that%20the%20problem%20was%20in%20ADFS.%26nbsp%3B%20They%20fixed%20it%2C%20but%20did%20not%20provide%20specifics%2C%20so%20one%20place%20that%20I%20suggest%20looking%20in%20ADFS%20logs%20for%20errors.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20software%20build%20we%20are%20using%20is%204.0.51.0%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282840%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282840%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EModifying%20a%20local%20HOSTS%20file%20should%20not%20be%20necessary%20and%20is%20not%20the%20ideal%26nbsp%3Bconfiguration.%26nbsp%3B%20Do%20you%20know%20why%20the%20SRS%20was%20attempting%20to%20connect%20to%20an%20external%20host%3F%26nbsp%3B%20If%20you%20are%20only%20using%20Exchange%20Server%20(and%20not%20in%20an%20Exchange%20Hybrid%20model)%20then%20it%20appears%20you%20have%20an%20incorrect%20DNS%20configuration.%26nbsp%3B%20Is%20the%20SRS%20using%20an%20external%20DNS%20resolver%20by%20chance%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282776%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282776%22%20slang%3D%22en-US%22%3EThat%20is%20correct%2C%20just%20depends%20on%20your%20exact%20DNS%20setup%20etc.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-282435%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282435%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Graham%2C%20would%20the%20FQDN%20look%20like%20this%3A%20%5B%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3Eautodiscover.%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%20font-style%3A%20italic%3B%22%3Edomain%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-weight%3A%20bold%3B%22%3E.com%3C%2FSPAN%3E%5D%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-281895%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-281895%22%20slang%3D%22en-US%22%3EFor%20the%20host%20record%2C%20you%20would%20add%20your%20local%20exchnge%20server%20IP%20address%20and%20then%20the%20FQDN.%20Save%20and%20reboot.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-278363%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-278363%22%20slang%3D%22en-US%22%3E%3CP%3Ewhat%20host%20record%20did%20you%20add%20please%20%3F%20we%20have%20the%20exact%20same%20issue%20all%20of%20a%20sudden%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-275505%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-275505%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F122627%22%20target%3D%22_blank%22%3EGr%C3%BCner%3C%2FA%3E%2C%20glad%20you%20got%20it%20working.%26nbsp%3B%20Do%20you%20mind%20to%20tell%20us%20what%20was%20the%20line%20you%20added%20to%20your%20hosts%20file%3F%26nbsp%3B%20Thanks%2C%20Tim%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F122627%22%20target%3D%22_blank%22%3E%40Elias%20Gr%C3%BCner%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EI%20finally%20figured%20it%20out.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3Ethe%20problem%20was%20that%20the%20smartdock%20tried%20to%20get%20the%20calendar%20from%20an%20external%20site%20in%20the%20cloud%20instead%20of%20our%20own%20onprem%20site.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20simply%20went%20to%26nbsp%3BC%3A%5CWindows%5CSystem32%5Cdrivers%5Cetc%5Chots%20and%20added%20our%20onprem%20IP%20to%20tell%20the%20smartdock%20where%20to%20look%20instead.%26nbsp%3B%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176707%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176707%22%20slang%3D%22en-US%22%3E%3CP%3ELogitech%20Smart%20Dock%20SRS%20v3.1%20-%20I%20am%20having%20the%20same%20%22Cannot%20fetch%20calendar%22%20issue%20with%20Office%20365%20(no%20on-premises%20services).%26nbsp%3B%20I've%20followed%20the%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt790557.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%22Skype%20for%20Business%20Room%20Systems%20v2%3A%20Deploy%20with%20Office%20365%22%3C%2FA%3E%26nbsp%3Bsuccessfully%20and%20checked%20settings%20and%20they%20all%20look%20correct.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20tested%20the%20room%20account%20on%20a%20desktop%20and%20it%20works%20perfectly%20-%20The%20Exchange%20Calendar%20Auto-Accepts%20requested%20meetings%20and%20works%20as%20it%20should%20-%20Skype%20for%20Business%20client%20shows%20%22upcoming%20meetings%22%20in%20the%20client%2C%20etc.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20suspecting%20this%20may%20be%20something%20to%20do%20with%20default%20Smart%20Dock%20local%20account%20('Skype')%20that%20it%20uses%20to%20auto-login%20and%20start%20up%20the%20SRS.%26nbsp%3B%20Are%20there%20any%20additional%20steps%20I%20may%20need%20to%20perform%20to%20get%20the%20account%20added%20and%20authenticated%20correctly%20with%20Azure%20AD%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-169745%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169745%22%20slang%3D%22en-US%22%3E%3CP%3EI%20finally%20figured%20it%20out.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3Ethe%20problem%20was%20that%20the%20smartdock%20tried%20to%20get%20tha%20calendar%20from%20an%20external%20site%20in%20the%20cloud%20instead%20of%20our%20own%20onprem%20site.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20simply%20went%20to%26nbsp%3BC%3A%5CWindows%5CSystem32%5Cdrivers%5Cetc%5Chots%20and%20added%20our%20onprem%20IP%20to%20tell%20the%20smartdock%20where%20to%20look%20instead.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168697%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168697%22%20slang%3D%22en-US%22%3EIf%20you%20sign%20into%20a%20Windows%20client%20with%20the%20same%20SRS%20credentials%2C%20so%20they%20show%20up%20correctly%20in%20the%20SfB%20client%3F%20IM%2C%20voice%2Fvideo%20and%20meetings%20all%20working%20ok%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165031%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165031%22%20slang%3D%22en-US%22%3E%3CP%3Ewe're%20using%20on-prem%20exchange%20server%202016%20and%20it's%20a%20resource%20mailbox%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-164981%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Calendar%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-164981%22%20slang%3D%22en-US%22%3E%3CP%3EPotentially%20an%20autodiscover%20issue.%26nbsp%3B%20Are%20you%20signing%20into%20Exchange%20Server%20or%20Online%3F%26nbsp%3B%20Is%20the%20account%20setup%20with%20a%20resource%20mailbox%20or%20a%26nbsp%3Bregular%20user%20mailbox%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20using%20Skype%20for%20Business%20Online%20I%26nbsp%3Bsuggest%20making%20sure%20you%20have%20the%20account%20configured%20correctly%3A%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fblog.schertz.name%2F2017%2F01%2Fskype-for-business-online-meeting-room-accounts%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fblog.schertz.name%2F2017%2F01%2Fskype-for-business-online-meeting-room-accounts%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Hi, I'm wondering if anyone else has run into the "cannot fetch calendar" issue.

We just got a Logitech Smartdock and everything works fine except that you cant see the meetings on the dock. 

12 Replies

Potentially an autodiscover issue.  Are you signing into Exchange Server or Online?  Is the account setup with a resource mailbox or a regular user mailbox?

 

If you are using Skype for Business Online I suggest making sure you have the account configured correctly: http://blog.schertz.name/2017/01/skype-for-business-online-meeting-room-accounts/

we're using on-prem exchange server 2016 and it's a resource mailbox

If you sign into a Windows client with the same SRS credentials, so they show up correctly in the SfB client? IM, voice/video and meetings all working ok?
Best Response
Solution

I finally figured it out. 

the problem was that the smartdock tried to get tha calendar from an external site in the cloud instead of our own onprem site. 

I simply went to C:\Windows\System32\drivers\etc\hots and added our onprem IP to tell the smartdock where to look instead. 

Logitech Smart Dock SRS v3.1 - I am having the same "Cannot fetch calendar" issue with Office 365 (no on-premises services).  I've followed the "Skype for Business Room Systems v2: Deploy with Office 365" successfully and checked settings and they all look correct. 

 

I tested the room account on a desktop and it works perfectly - The Exchange Calendar Auto-Accepts requested meetings and works as it should - Skype for Business client shows "upcoming meetings" in the client, etc.

 

I am suspecting this may be something to do with default Smart Dock local account ('Skype') that it uses to auto-login and start up the SRS.  Are there any additional steps I may need to perform to get the account added and authenticated correctly with Azure AD?

Hi Grüner, glad you got it working.  Do you mind to tell us what was the line you added to your hosts file?  Thanks, Tim

 


@Deleted wrote:

I finally figured it out. 

the problem was that the smartdock tried to get the calendar from an external site in the cloud instead of our own onprem site. 

I simply went to C:\Windows\System32\drivers\etc\hots and added our onprem IP to tell the smartdock where to look instead. 


 

what host record did you add please ? we have the exact same issue all of a sudden?

For the host record, you would add your local exchnge server IP address and then the FQDN. Save and reboot.

Thanks Graham, would the FQDN look like this: [autodiscover.domain.com] ?

That is correct, just depends on your exact DNS setup etc.

Modifying a local HOSTS file should not be necessary and is not the ideal configuration.  Do you know why the SRS was attempting to connect to an external host?  If you are only using Exchange Server (and not in an Exchange Hybrid model) then it appears you have an incorrect DNS configuration.  Is the SRS using an external DNS resolver by chance?

I have been working on this issue for a number of weeks and found a specific cause and solution in my case.  From experience working on this error I think it's important to note that "Cannot fetch calendar" seems to be a generic "catch all" error.  SRSv2 is telling you it can't get the calendar information and the cause can be any number of different things like Autodiscover or account config as you can read in other posts here.

 

In my case, the network team at my company figured out that the problem was in ADFS.  They fixed it, but did not provide specifics, so one place that I suggest looking in ADFS logs for errors.

 

The software build we are using is 4.0.51.0