Playback Exception errors are back - ugh

[Grasshopper]

For a long time, I'd been getting intermittent playback exception errors on my Client box, telling me to install the latest version of DirectX. Of course, I'd already done this. These would happen when playback started -- sometimes of a recorded show, sometimes a (local) DVD. And I only got them on the client box; I have an MVP client running, and it never got them. So I was pretty sure that it was something wrong with the client box. Reinstalling Sage didn't work, reinstalling the video card drivers didn't work, reinstalling the decoders didn't work. Finally, out of ideas, I wiped the hard drive and reinstalled Windows and Sage Client, and the playback exceptions went away. So whatever caused them, I was fairly sure that it was something wrong with the client box.

Until today. I was accepted into the Windows Home Server beta and installed it on my Sage server; it's basically a stripped version of Windows Server 2003. Installed Sage without a hiccup. And the occasional playback exception errors on the client are back.

Is it just a coincidence? Is information passed between client and server when beginning playback on the client, even when I'm starting a DVD that's in the client box? Is it possible that networking issues would cause this error? I'll likely file a tech support request with George, but was hoping to find others who had encountered and solved this problem first.

[Narflex]

This doesn't sound familiar at all but it looks like a problem outside of SageTV that's manifesting itself in SageTV. It very well could be a hardware problem on the server. Definitely do a hard disk scan and a memtest to rule those out.

If that's not it then send in a log file to support so we can find out more specifically where the error is occuring at.

[Grasshopper]

So it's possible that it's a problem on the server, then -- even if I get the error playing a dvd on the client?