TheGreenButton - Windows Media Center Forums

OK, so today is March 12. I've been checking the guide for a resurgence of the problem and it doesn't seem like I can update the guide beyond March 18th. This time both systems are effected since neither will go beyond the 18th which is less then a full 6 days of guide data. Also, this time it's for all channels not just missing guide data for select network channels.

Keep in mind that one system has the workaround in place and the other doesn't.

I'm going to try and get past the weekend before attempting to fix this so maybe on Monday but I would like to have a plan of action in place before then.

[Moderator note: topic merged]

Interesting! My guide(s) data has worked fine for months now, however I recently discovered that none of my 4 machines have updated my guide past 7 PM on March 18th. When manually requesting a Guide update, WMC comes back after about 30 seconds and states "successful", but the WMC download icon on the taskbar say it "downloaded with errors". Anyone have any suggestions?

Gary

this is happening to everyone, and it's a regular occurrence around the time of DST switch.

If things aren't worked out by Tuesday morning, then I'll panic. Until then it's business as usual.

It's that time of the year (maybe) and my Guide Data has six days left. Everything updates normally (guide error no nettv every time on every machine) but no new data has been added the last week.

Anyone else check their guide data (easy check is to go to Add Recording/Search/Title and the days of Guide Data will appear in the lower part of the screen).

Location: Los Angeles Time Warner Cable, West Valley.

John

Yup, we know...
https://connect.microsoft.com/site1145/ ... ls/2452803

John, we had a topic going on the subject that I have nuked by accident
I'd like to suggest we continue the discussion here.
I will edit your title a bit to assist.

I was wondering where that thread went!! Thanks!

There we go.

Yeah, there it went

STC wrote:John, we had a topic going on the subject that I have nuked by accident
I'd like to suggest we continue the discussion here.
I will edit your title a bit to assist.

Huh, I was wondering where my thread had gone to.

[ That's alright, these things happen to Homer Simpson from time-to-time. D'oh! ]

Typically, Microsoft has the guide data DST issue resolved by the Monday after the transition. (That's why I haven't raised too much of a ruckus this time around.) That said, if they don't have new data by Wednesday morning, we're all going to be scrambling to get EPG123 installed and configured before our guide data runs out. (Someone may want to give garyan2 a heads up to get a good stable release published for this inevitable scramble, should MS drop the ball completely.)

As soon as anyone sees new EPG data (post-DST transition, that is), please post a note here.

<gesture fingers-crossed="true" />

Edit: Added hyperlink for EPG123.

I had been tracking the end date of guide data, which was March 19th for me, and was initially excited to wake up today and see a message in Media Center about detecting an issue with guide data and it was going to update. I thought all would be well... Anyway, we went most of the day without guide data - as in, even today and the days leading up to the 19th were now gone. Guide data is now back, but still through the 19th, but it is worse again, like the early days after the Rovi switch. Incorrect entries, images don't match shows, etc... Ooof.

stupid question: that link from Microsoft seems to be not found when I click on it, despite logging in with my MS ID. can anyone post an alternate link or a screenshot of the article mentioned?

I posted about this earlier today but the thread I started has vanished. At least I now know it isn't just me...

Ladislaus wrote:
Typically, Microsoft has the guide data DST issue resolved by the Monday after the transition. (That's why I haven't raised too much of a ruckus this time around.) That said, if they don't have new data by Wednesday morning, we're all going to be scrambling to get EPG123 installed and configured before our guide data runs out

You seem to be taking it well.

I just reciently got guide data working again before this issue cropped up so this is really frustrating. Still your suggestion of EPG123 is a good one IMO. At the very least it gives us some recourse and some sense of control in this unfortunate situation.

Hopefully it will be working again in the morning since DST has passed. If not, then I think it is time for EPG 123.

Still ends 3/18.

Broken here, ends 3/19 on mine. Logs say "EPGListings are already up to date" and no new data downloads

Hopefully someone can contact Microsoft to make them aware. They don't seem to be monitoring this forum anymore....

Based on the Windows 7 Community thread the last couple years, there is now _one_ user named Barb, who has _one_ relevant contact at MS, who can contact the appropriate team within MS. Thus far she claims radio silence from MS. I don't know if the connection is really that tenuous, but it's the same impression I got last year at this time. And this was definitely a factor in me fleeing to epg123 as soon as it became available.

The thing that's odd is that last year, the MS response was actually apologetic. It sounded like they intended to keep guide data coming for a while, and they were embarrassed by how slow it took them to notice/fix it.

Thread in question: http://answers.microsoft.com/en-us/wind ... 7961419365

This morning she claims to have tried 3 times to reach out to previous contacts, to no avail.

Honestly, I didn't hold hope for updates this morning. If none this evening by manual update, or next morning by automatic, then I think garyans2's code is going production a little sooner than expected...

Just checked this morning, Mine ends on March 19 too.

My wife is not pleased as we cannot schedule things occurring later than this week. Time to switch to EPG123? How's that coming along? Is it pretty stable? I'm seeing things about database not being updated and the Schedules Direct data not being correct now too.