Thanx for a workaround! I had a new install and after installing the entries in hosts I had to re-run live setup and it worked. Guess it wasn't a MS issue after alljasonl wrote:Appears to be a problem with one or more of the Akamai servers that host Microsoft's content. Exactly which server you get pointed at depends on your DNS server, which is why ....Save the file, then at the command prompt run:Code: Select all
65.55.186.115 data.tvdownload.microsoft.com 128.177.98.169 cdn.epg.tvdownload.microsoft.com
Then, force an update in WMC.Code: Select all
ipconfig /flushdns
Guide Download Issues Thread - Sept 2014
-
- Posts: 4
- Joined: Wed Sep 17, 2014 3:40 am
- Location:
- HTPC Specs:
-
- Posts: 5
- Joined: Wed Feb 05, 2014 2:04 am
- Location:
- HTPC Specs:
This seems to be happening in cities where i have read that they are changing the channel lineup and upgrading internet speed which in my city Simi Valley Ca. the process happened today 9-17-14 and I have the same issue with 2- 8.1 PC's / 2-win 7 Pc's
-
- Posts: 25
- Joined: Wed Mar 13, 2013 2:53 pm
- Location:
- HTPC Specs:
I've been working with techsupport at opendns seeing if they could shed some light. I sent them a pcap file. They could see a several MS sites being hit during the update but nothing appears to fail in the pcap file.STC wrote:Would anyone with some time and inclination like to wireshark their failing update process?
-
- Posts: 25
- Joined: Wed Mar 13, 2013 2:53 pm
- Location:
- HTPC Specs:
Success! This worked for me. Still using opendns ip addresses for DNS, modifying the the HOST file worked great.jasonl wrote:Appears to be a problem with one or more of the Akamai servers that host Microsoft's content. Exactly which server you get pointed at depends on your DNS server, which is why switching it sometimes works. But, since Google DNS is anycasted, using 8.8.8.8 will point to different physical servers depending on where you are in the world, and that may point you at different Akamai servers, including possibly pointing you right back at an inaccessible one.. Forcing WMC to use known-good servers by bypassing the DNS lookup appears to allow updates to complete, or at least did on both of my PCs that were having trouble. Open an elevated command prompt (search for cmd, right click, Run as Administrator) and run:Add the following lines at the bottom of the file:Code: Select all
notepad c:\windows\system32\drivers\etc\hosts
Save the file, then at the command prompt run:Code: Select all
65.55.186.115 data.tvdownload.microsoft.com 128.177.98.169 cdn.epg.tvdownload.microsoft.com
Then, force an update in WMC.Code: Select all
ipconfig /flushdns
Once Microsoft and Akamai figure it out, you'll want to reopen the file using the same process, and remove those 2 lines and save the file. Otherwise, a future server update could break things for you again.
-
- Posts: 14
- Joined: Thu Sep 18, 2014 2:37 am
- Location:
- HTPC Specs:
Changing the DNS Server to Google (8 8 8 8) did allow me to manually update the guide. However program details were incomplete meaning just the show names with very little episode info. It also slowed my internet speed from 109 Mbps to 67 Mbps. I am on Time Warner Redlands CA Digital Cable.
-
- Posts: 9
- Joined: Fri Jul 04, 2014 1:25 am
- Location:
- HTPC Specs:
Has anyone else found a solution to this aside from what was listed above? I've tried EVERYTHING! The hosts file change failed, so did using VPN while connecting to multiple countries as well as the Google DNS Servers. For the life of me, I cannot get ANY guide data. I've got a VERY PO'ed spouse who is threatening to kill me in my sleep because we have no idea when reruns of Law and Order: SVU come on! lol
I'm at my wits end here!
I'm at my wits end here!
-
- Posts: 4
- Joined: Wed Sep 17, 2014 3:40 am
- Location:
- HTPC Specs:
After making the DNS change in hosts I still wasn't getting the guide downloaded. I went to c:/programdata/microsoft/ehome and deleted the .db file and db folder and then ran Media Center and it forced me to go thru live setup and it worked after that. Mine was a new install and had never had the guide downloaded, but the addition of the entries and clearing the .db made it all better. Might give that try.Dsmevolution wrote:Has anyone else found a solution to this aside from what was listed above? I've tried EVERYTHING! The hosts file change failed, so did using VPN while connecting to multiple countries as well as the Google DNS Servers. For the life of me, I cannot get ANY guide data. I've got a VERY PO'ed spouse who is threatening to kill me in my sleep because we have no idea when reruns of Law and Order: SVU come on! lol
I'm at my wits end here!
-
- Posts: 19
- Joined: Mon Mar 17, 2014 10:49 pm
- Location:
- HTPC Specs:
They should. In Win 8, it requires a paid upgrade, unlike in Win 7 where it is bundled in all versions. (Not that there are any significant differences between the two.) My point is that folks with Win 8 and WMC specifically paid to get that functionality. If MSFT doesn't care about WMC any more, they will owe those people a refund.mech259 wrote:I just wonder if Micro$oft even cares about WMC anymore.
-
- Posts: 21
- Joined: Fri Sep 07, 2012 11:55 pm
- Location:
- HTPC Specs:
The host file fixed it for me.
-
- Posts: 22
- Joined: Wed Sep 17, 2014 8:13 pm
- Location:
- HTPC Specs:
This worked for me too. I just find myself wondering how we will know when it is time to remove the two added lines to the hosts file.jasonl wrote:Appears to be a problem with one or more of the Akamai servers that host Microsoft's content. Exactly which server you get pointed at depends on your DNS server, which is why switching it sometimes works. But, since Google DNS is anycasted, using 8.8.8.8 will point to different physical servers depending on where you are in the world, and that may point you at different Akamai servers, including possibly pointing you right back at an inaccessible one.. Forcing WMC to use known-good servers by bypassing the DNS lookup appears to allow updates to complete, or at least did on both of my PCs that were having trouble. Open an elevated command prompt (search for cmd, right click, Run as Administrator) and run:Add the following lines at the bottom of the file:Code: Select all
notepad c:\windows\system32\drivers\etc\hosts
Save the file, then at the command prompt run:Code: Select all
65.55.186.115 data.tvdownload.microsoft.com 128.177.98.169 cdn.epg.tvdownload.microsoft.com
Then, force an update in WMC.Code: Select all
ipconfig /flushdns
Once Microsoft and Akamai figure it out, you'll want to reopen the file using the same process, and remove those 2 lines and save the file. Otherwise, a future server update could break things for you again.
- STC
- Posts: 6808
- Joined: Mon Jun 06, 2011 4:58 pm
- Location:
- HTPC Specs:
^ if it stops working due to a change of servers. Otherwise it will be harmless. It's just a resolve override.Mountainbreeze wrote:...I just find myself wondering how we will know when it is time to remove the two added lines to the hosts file.
By the Community, for the Community. 100% Commercial Free.
Want decent guide data back? Check out EPG123
Want decent guide data back? Check out EPG123
-
- Posts: 1
- Joined: Thu Sep 18, 2014 10:00 pm
- Location:
- HTPC Specs:
Thank You Jason! This workaround resolved my download as well. I am a member of a few other forums and I shared a direct link to your posting.jasonl wrote:Appears to be a problem with one or more of the Akamai servers that host Microsoft's content. Exactly which server you get pointed at depends on your DNS server, which is why switching it sometimes works. But, since Google DNS is anycasted, using 8.8.8.8 will point to different physical servers depending on where you are in the world, and that may point you at different Akamai servers, including possibly pointing you right back at an inaccessible one.. Forcing WMC to use known-good servers by bypassing the DNS lookup appears to allow updates to complete, or at least did on both of my PCs that were having trouble. Open an elevated command prompt (search for cmd, right click, Run as Administrator) and run:Add the following lines at the bottom of the file:Code: Select all
notepad c:\windows\system32\drivers\etc\hosts
Save the file, then at the command prompt run:Code: Select all
65.55.186.115 data.tvdownload.microsoft.com 128.177.98.169 cdn.epg.tvdownload.microsoft.com
Then, force an update in WMC.Code: Select all
ipconfig /flushdns
Once Microsoft and Akamai figure it out, you'll want to reopen the file using the same process, and remove those 2 lines and save the file. Otherwise, a future server update could break things for you again.
- jfreiman
- Posts: 67
- Joined: Wed Jun 26, 2013 10:59 pm
- Location: San Francisco, California
- HTPC Specs:
Thank you, this worked for me too!jasonl wrote:Appears to be a problem with one or more of the Akamai servers that host Microsoft's content. Exactly which server you get pointed at depends on your DNS server, which is why switching it sometimes works. But, since Google DNS is anycasted, using 8.8.8.8 will point to different physical servers depending on where you are in the world, and that may point you at different Akamai servers, including possibly pointing you right back at an inaccessible one.. Forcing WMC to use known-good servers by bypassing the DNS lookup appears to allow updates to complete, or at least did on both of my PCs that were having trouble. Open an elevated command prompt (search for cmd, right click, Run as Administrator) and run:Add the following lines at the bottom of the file:Code: Select all
notepad c:\windows\system32\drivers\etc\hosts
Save the file, then at the command prompt run:Code: Select all
65.55.186.115 data.tvdownload.microsoft.com 128.177.98.169 cdn.epg.tvdownload.microsoft.com
Then, force an update in WMC.Code: Select all
ipconfig /flushdns
Once Microsoft and Akamai figure it out, you'll want to reopen the file using the same process, and remove those 2 lines and save the file. Otherwise, a future server update could break things for you again.
-
- Posts: 163
- Joined: Sun Dec 23, 2012 3:38 pm
- Location:
- HTPC Specs:
Thanks for the fix, awesome save.
-
- Posts: 786
- Joined: Fri Jul 20, 2012 7:23 pm
- Location:
- HTPC Specs:
When it gets fixed, the MS Connect page should change from ACTIVE to RESOLVED. At that point you can remove the pointers and run "get latest guide" from the guide (right click on any channel number and choose get latest guide) and verify that its working.STC wrote:^ if it stops working due to a change of servers. Otherwise it will be harmless. It's just a resolve override.Mountainbreeze wrote:...I just find myself wondering how we will know when it is time to remove the two added lines to the hosts file.
The problem with leaving it is MSFT could move the guide IP address and then your modified host file would fail. You never know what those backroom guys will do.
-
- Posts: 10
- Joined: Thu Jan 17, 2013 1:13 am
- Location:
- HTPC Specs:
Didn't work in SE Texas. Have a good copy of hosts file?jfreiman wrote:Thank you, this worked for me too!jasonl wrote:Appears to be a problem with one or more of the Akamai servers that host Microsoft's content. Exactly which server you get pointed at depends on your DNS server, which is why switching it sometimes works. But, since Google DNS is anycasted, using 8.8.8.8 will point to different physical servers depending on where you are in the world, and that may point you at different Akamai servers, including possibly pointing you right back at an inaccessible one.. Forcing WMC to use known-good servers by bypassing the DNS lookup appears to allow updates to complete, or at least did on both of my PCs that were having trouble. Open an elevated command prompt (search for cmd, right click, Run as Administrator) and run:Add the following lines at the bottom of the file:Code: Select all
notepad c:\windows\system32\drivers\etc\hosts
Save the file, then at the command prompt run:Code: Select all
65.55.186.115 data.tvdownload.microsoft.com 128.177.98.169 cdn.epg.tvdownload.microsoft.com
Then, force an update in WMC.Code: Select all
ipconfig /flushdns
Once Microsoft and Akamai figure it out, you'll want to reopen the file using the same process, and remove those 2 lines and save the file. Otherwise, a future server update could break things for you again.
-
- Posts: 9
- Joined: Fri Jul 04, 2014 1:25 am
- Location:
- HTPC Specs:
webguyz wrote:After making the DNS change in hosts I still wasn't getting the guide downloaded. I went to c:/programdata/microsoft/ehome and deleted the .db file and db folder and then ran Media Center and it forced me to go thru live setup and it worked after that. Mine was a new install and had never had the guide downloaded, but the addition of the entries and clearing the .db made it all better. Might give that try.Dsmevolution wrote:Has anyone else found a solution to this aside from what was listed above? I've tried EVERYTHING! The hosts file change failed, so did using VPN while connecting to multiple countries as well as the Google DNS Servers. For the life of me, I cannot get ANY guide data. I've got a VERY PO'ed spouse who is threatening to kill me in my sleep because we have no idea when reruns of Law and Order: SVU come on! lol
I'm at my wits end here!
No dice on this for me as well. I guess i'm just doomed to have no guide info. Worst of all, i'll have to go back to using a cable box from Time Warner. This has me so angry...
-
- Posts: 9
- Joined: Fri Jul 04, 2014 1:25 am
- Location:
- HTPC Specs:
Ok, and amendment to my previous statement. After rebooting it and attempting to setup my info, I noticed something odd. The setup said that it couldn't detect my TV signal as well. I performed the hosts file trick, deleting the .db files and the folders, then I had to remove my Ceton InfiniTV from the device manager, delete all the driver files and reinstall it. Once I came back up, it could detect the signal and actually downloaded guide data!Dsmevolution wrote:webguyz wrote:After making the DNS change in hosts I still wasn't getting the guide downloaded. I went to c:/programdata/microsoft/ehome and deleted the .db file and db folder and then ran Media Center and it forced me to go thru live setup and it worked after that. Mine was a new install and had never had the guide downloaded, but the addition of the entries and clearing the .db made it all better. Might give that try.Dsmevolution wrote:Has anyone else found a solution to this aside from what was listed above? I've tried EVERYTHING! The hosts file change failed, so did using VPN while connecting to multiple countries as well as the Google DNS Servers. For the life of me, I cannot get ANY guide data. I've got a VERY PO'ed spouse who is threatening to kill me in my sleep because we have no idea when reruns of Law and Order: SVU come on! lol
I'm at my wits end here!
No dice on this for me as well. I guess i'm just doomed to have no guide info. Worst of all, i'll have to go back to using a cable box from Time Warner. This has me so angry...
So Jason and Webguyz, thank you SO MUCH! I was about ready to strangle someone out of frustration!
-
- Posts: 445
- Joined: Tue May 28, 2013 11:56 pm
- Location: Stockton CA
- HTPC Specs:
Just playing around with trace route on this website yields different IP's than what are being given out here...
http://www.cogentco.com/en/network/looking-glass
cdn.epg.tvdownload.microsoft.com is coming out as
95.100.97.80/81 (depending on where you run it from)
data.tvdownload.microsoft.com is coming out as
65.55.186.113 west coast/east coast
65.55.5.170 central/southern us
http://www.cogentco.com/en/network/looking-glass
cdn.epg.tvdownload.microsoft.com is coming out as
95.100.97.80/81 (depending on where you run it from)
data.tvdownload.microsoft.com is coming out as
65.55.186.113 west coast/east coast
65.55.5.170 central/southern us
-
- Posts: 9
- Joined: Fri Jul 04, 2014 1:25 am
- Location:
- HTPC Specs:
tzr916 wrote:Just playing around with trace route on this website yields different IP's than what are being given out here...
http://www.cogentco.com/en/network/looking-glass
cdn.epg.tvdownload.microsoft.com is coming out as
95.100.97.80/81 (depending on where you run it from)
data.tvdownload.microsoft.com is coming out as
65.55.186.113 west coast/east coast
65.55.5.170 central/southern us
Makes sense, anything that's going to serve a large user based would have to be a clustered system serviced by a central load balancer. The problem is that from the behaviors i've seen described here, there appears to be a break in the path to one of the primary servers that the load balancer would be routing users to. And the problem with load balancing is that once you make a connection to one of the cluster nodes, you tend to get forwarded to that node for future request for data request. When the node becomes unreachable due to either server outage or network issues, the balancer will still send traffic there even if the node doesn't pick up the traffic.