2010-08-29, 07:23 PM
johnsonx42 Wrote:That's a different issue Kendrak. The original issue related to a problem with the EPG reload - part of the recording service would have an updated recording schedule with new recording ID's, while the back-end part actually making the recordings would still have be using the old schedule with old recording ID's. So the two halves were never on the same page; the back-end would keep making recordings, but with different recording ID's than the database engine was expecting, so the database would keep thinking all the scheduled recordings were still pending and would eventually "fail" them when the recording schedule finally did get reloaded. That issue has absolutely been fixed.
I don't see how you can say that this is a completely different issue? What you describe exactly match my problem.
I will post the logs in the support forum next time it happens.