EPG Odd Behaviour

[LazyGun]

I'm sharing this on the off chance that someone else may run into this issue, and hopefully this could save them some time...

Last week I noticed that my Guide ran out of data on Saturday afternoon.
The EPG update seemed to be fine. I ran through all the troubleshooting steps
- adding a new channel to force an update
- removing the properties from the .properties file, etc

Nothing seemed to work.

I tried adding a new Channel lineup, and whenever I typed in my ZipCode I received an error saying that it could not connect to the SageTV Server, which was most odd.

I checked the firewall, I checked connectivity from my Sage box to the outside world, I checked DNS settings, blah blah. It all looked fine.

To resolve it, I had to enter a neighbouring zipcode to mine, and after trying 3 or 4, I found one that loaded a channel lineup.

It looked like Comcast had changed the name of the lineup, but then hadn't published one for a few zipcodes in my area. This is probably an edge case, but if typing this saves someone else from 30 minutes of hitting their head on the coffee table and swearing under their breath (on the off chance their children hears Mummy or Daddy saying the S-word or worse), then it is worth it.

Cheers

[KarylFStein]

Ugh, I had this issue last week trying out an upgrade to W10 and SageTV 9. I got to configuring the sources and it kept saying it couldn't connect. It was the final straw for me to revert back to my prior image after several hours of working on the upgrade . At least next time I play with this and get an error like that I have something to try...

Note that I hadn't even gotten to the Comcast lineups--I was just working on the OTA first.

[trallyus]

2 of us, myself and another had the EPG guide ending with V9 of sage TV - He fixed his by running sage tv as a service the same as me and fixed it by running the sage tv service as a user.

Thread I am referring to is at http://forums.sagetv.com/forums/showthread.php?t=62577