Teams Room "Cannot Fetch Calendar"

Brass Contributor

Good day,

 

I have just finished setting up our Lenovo ThinkSmart Hub500. Creating the room and users account as per MS instructions is all done and Teams Room is logged in. I can start a new meeting and project but no meetings are showing up. At the top it says "Cannot Fetch Calendar". 

 

What are we doing wrong?

 

Thanks.

46 Replies
This error usually appears when the new account hasn't fully replicated within O365. Has it worked now that 24hrs have passed?

This post might help too https://medium.com/@vaughanjamesr/microsoft-teams-rooms-cannot-fetch-calendar-39f682666636

@Graham Walsh 

 

A couple weeks have passed and no luck...how do i check to make sure my autodiscover is correct?

@bjones96 

You can check your DNS records in the M365 Admin center, under settings and then domains.

@bjones96 I use this PowerShell to test settings.  Just change line 2 with your domain name.

 

### Enter Domain Name below
$name='contoso.com'

### Exchange
Resolve-DnsName -Type A -Name autodiscover.$name
Resolve-DnsName -Type CNAME -Name autodiscover.$name
Resolve-DnsName -Type TXT -Name $name
Resolve-DnsName -Type MX -Name $name
Resolve-DnsName -Type A -Name mail.$name

### Skype for Business
Resolve-DnsName -Type SRV _sipfederationtls._tcp.$name
Resolve-DnsName -Type CNAME lyncdiscover.$name
Resolve-DnsName -Type CNAME sip.$name
Resolve-DnsName -Type A meet.$name

@Graham Walsh 

Here is my result. can you help me what i need to do to set the DNS up correctly?

 

Name : frsgrp.com
QueryType : MX
TTL : 3600
Section : Answer
NameExchange : mx2.emailsrvr.com
Preference : 20


Name : frsgrp.com
QueryType : MX
TTL : 3600
Section : Answer
NameExchange : mx1.emailsrvr.com
Preference : 10


Name : mx2.emailsrvr.com
QueryType : A
TTL : 79
Section : Additional
IP4Address : 173.203.187.2


Name : mx1.emailsrvr.com
QueryType : A
TTL : 40
Section : Additional
IP4Address : 173.203.187.1

Resolve-DnsName : mail.frsgrp.com : DNS name does not exist
At line:8 char:1
+ Resolve-DnsName -Type A -Name mail.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (mail.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : _sipfederationtls._tcp.frsgrp.com : DNS name does not exist
At line:10 char:1
+ Resolve-DnsName -Type SRV _sipfederationtls._tcp.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (_sipfederationtls._tcp.frsgrp.com:String) [Resolve-DnsName], Win32
Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : lyncdiscover.frsgrp.com : DNS name does not exist
At line:11 char:1
+ Resolve-DnsName -Type CNAME lyncdiscover.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (lyncdiscover.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : sip.frsgrp.com : DNS name does not exist
At line:12 char:1
+ Resolve-DnsName -Type CNAME sip.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (sip.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : meet.frsgrp.com : DNS name does not exist
At line:13 char:1
+ Resolve-DnsName -Type A meet.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (meet.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Great script from Room System master @Graham Walsh .

 

@bjones96 I don't see the results from this, can you post taht?

Resolve-DnsName -Type CNAME -Name autodiscover.$name

 

Also it looks like you have an internal DNS with the zone frsgrp.com and that DNS server is missing the records you get a failure for. Can you add them in the zone and also check that you have a CNAME for autodiscover.frsgrp.com pointing to autodiscover.outlook.com

@Linus Cansby 

sorry, i have posted the full result below. in rackspace dns settings i have autodiscover cname pointing to autodiscover.outlook.com. see attached screen shot.

 

Resolve-DnsName : autodiscover.frsgrp.com : DNS name does not exist
At line:4 char:1
+ Resolve-DnsName -Type A -Name autodiscover.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (autodiscover.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : autodiscover.frsgrp.com : DNS name does not exist
At line:5 char:1
+ Resolve-DnsName -Type CNAME -Name autodiscover.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (autodiscover.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName


Name Type TTL Section PrimaryServer NameAdministrator SerialNumber
---- ---- --- ------- ------------- ----------------- ------------
frsgrp.com SOA 3600 Authority server.frscanada.local hostmaster.frscanada.local 8

Name : frsgrp.com
QueryType : MX
TTL : 3600
Section : Answer
NameExchange : mx2.emailsrvr.com
Preference : 20


Name : frsgrp.com
QueryType : MX
TTL : 3600
Section : Answer
NameExchange : mx1.emailsrvr.com
Preference : 10


Name : mx2.emailsrvr.com
QueryType : A
TTL : 79
Section : Additional
IP4Address : 173.203.187.2


Name : mx1.emailsrvr.com
QueryType : A
TTL : 40
Section : Additional
IP4Address : 173.203.187.1

Resolve-DnsName : mail.frsgrp.com : DNS name does not exist
At line:8 char:1
+ Resolve-DnsName -Type A -Name mail.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (mail.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : _sipfederationtls._tcp.frsgrp.com : DNS name does not exist
At line:10 char:1
+ Resolve-DnsName -Type SRV _sipfederationtls._tcp.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (_sipfederationtls._tcp.frsgrp.com:String) [Resolve-DnsName], Win32
Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : lyncdiscover.frsgrp.com : DNS name does not exist
At line:11 char:1
+ Resolve-DnsName -Type CNAME lyncdiscover.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (lyncdiscover.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : sip.frsgrp.com : DNS name does not exist
At line:12 char:1
+ Resolve-DnsName -Type CNAME sip.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (sip.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

Resolve-DnsName : meet.frsgrp.com : DNS name does not exist
At line:13 char:1
+ Resolve-DnsName -Type A meet.$name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (meet.frsgrp.com:String) [Resolve-DnsName], Win32Exception
+ FullyQualifiedErrorId : DNS_ERROR_RCODE_NAME_ERROR,Microsoft.DnsClient.Commands.ResolveDnsName

 

Should look like this.

 

Linus Cansby_0-1582140482286.png

Can you try:

Resolve-DnsName -Type CNAME -Name autodiscover.$name -Server DNS1.NAME-SERVICES.COM

@Linus Cansby 

below is what is get when doing Resolve-DnsName -Type CNAME -Name autodiscover.$name -Server DNS1.NAME-SERVICES.COM


Name Type TTL Section NameHost
---- ---- --- ------- --------
autodiscover.frsgrp.com CNAME 1608 Answer autodiscover.outlook.com

What you did with that command when you added the -Server parameter was to say to powershell not to use the DNS server configured in Windows, use this one instead (DNS1.NAME-SERVICES.COM).

 

So I guess there is something wrong with the DNS server you are using on your MTR (or computer you are running these tests from). 

 

So check the DNS settings in windows, just type ipconfig /all and you will see the settings and what DNS server you are using.

 

You could also test to use another public DNS server, like google DNS 8.8.8.8. Change this in Windows for your MTR or the machine you are testing from, this could give you other problems if you are using a domain joined machine but this is just for testing.

https://mspoweruser.com/make-use-custom-dns-windows-10/

@Linus Cansby 

Ok cool. thanks. because the MTR device is located behind a firewall/windows server the DNS is picking up FRSCANADA.local as DNS.

 

if i change the connection properties on the adminaccount side of the MTR device will it reflect on the skype user side?

 

thanks.

Then I guess then that those local DNS servers is not configured correctly for the frsgrp.com forwarding zone.

If you change connection properties in Windows when logged in as admin the MTR application will use those settings. MTR application uses DNS settings from Windows.
Yay... It's finally working. Thanks a ton guys. Sorry to be so dumb as to these things.
Glad you sorted it out. Have fun with it!
Great to hear

@bjones96 Great. If you changed the DNS settings locally on the MTR it is probably better that you get the DNS server updated with the correct names so that you can continue using DHCP and so that you don't get this much problems with the next devices.

@bjones96 Hello, how did you solve this, did you make changes to the MTR, changing the internal DNS of the company or did you change the DNS to 8.8.8.8, you can finally explain how you solved it

@Erick570 

i went in to the admin side on the MTR and changed the network adapters dns to 8.8.8.8 to get aorund our company dns 

@bjones96  i did the same but is not working....

The account was created using the microsoft guide SRS , using this  2 commands 
New-Mailbox -Name "Project-Rigel-01" -Alias ProjectRigel01 -Room -EnableRoomMailboxAccount $true
-MicrosoftOnlineServicesID ProjectRigel01@contoso.onmicrosoft.com -RoomMailboxPassword
(ConvertTo-SecureString -String 'P@$$W0rd5959' -AsPlainText -Force)

Set-CalendarProcessing -Identity "Project-Rigel-01" -AutomateProcessing AutoAccept -
AddOrganizerToSubject $false -DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
-AddAdditionalResponse $true -AdditionalResponse "This is a Skype Meeting room!"


and then assigning the license

Confirming we also had the same issue with one of our Crestron Teams Room device, and changing the DNS to public fixed it. Not too sure why.