Sage did itself in?

[null_pointer_us]

This computer has been working fine as a Sage TV server for many, many months. Never missed a recording, crashed, or anything else. In the past week, however, we've had nothing but trouble with this server. No software of any kind was updated, except perhaps some of Windows' auto updates.

The trouble began when Sage's US cable listing database erased my cable provider and introduced a bunch of wierd names. Instead of Comcast and Comcast Digital, there's now the following:

• Comcast Classic Cable Lineup
• Comcast Classic Digital Lineup
• Comcast Classic Nonrebuild Digital
• Comcast Classic Nonrebuild Lineup

This was really irritating because no guide data means no recordings. Also, I had to spend some time figuring out it was the guide because Sage did not tell me what the problem was.



Anyway, after some trial and error, and some more missed recordings, I discovered that the last service is the correct one. So I deleted all four video sources (a pair of Hauppauge PVR-500 cards) and set them up again with the new cable listing information. Everything appeared to work fine...at first. The guide data filled in like normal, and I could watch TV.



However, the Sage TV service periodically locks up when trying to tune live TV or even access the guide. I mean: the little whirling busy logo comes up indefinitely; the service control app stops responding, etc. Killing and starting the service anew makes everything work fine.

I have no idea what has caused this problem. Inability to tune live TV and view the guide are definitely linked, because one of them always disables the other until the service is restarted. I cannot isolate the problem because it happens sporadically. I can flip channels just fine, give the remote to someone else, and get called five minutes later because "the TV has crashed."



Looking through the Windows Management Console logs, I see only perfmon warnings about slow disk access (which seem to occur only when restarting the computer) and of course the timeout events caused by Sage trying to access its service after the service has already locked up.

Good suggestions would be appreciated. Specifically, I could use some advice for wiping and reinstalling the Sage TV Server software without losing my list of recorded TV shows. Ways to kill the existing guide data might help. (I've followed the directions for refreshing the guide data, but the problem persists.)

Sometimes I think computers were invented to cure happiness.

[GKusnick]

Originally Posted by null_pointer_us

Looking through the Windows Management Console logs...

Sage keeps its own debug log in a separate file. See the FAQ for more info.

You should probably also submit a formal support request for any crashing/lockup issues.

[stanger89]

Originally Posted by null_pointer_us

...except perhaps some of Windows' auto updates.

Those are really really dangerous, IMO, much more dangerous than any potential vulnerabilities they may address.

If you think you need these updates, install them manually.