2009-09-06, 01:56 AM
I had the same issue, 1/1/0001 conflicts (that don't really conflict) and odd issues trying to remove them.
Turned out, in my case, that they resulted from my having removed a channel but was still getting the scheduling information from schedulesdirect. When I tried to record a program it couldn't find the associated channel and caused this error.
I had to manually scan to find the channel (which brings up another "bug" as the manual scan never quits on its own, and will add tons of entries listed by frequency rather than channel number into the results).
Turned out, in my case, that they resulted from my having removed a channel but was still getting the scheduling information from schedulesdirect. When I tried to record a program it couldn't find the associated channel and caused this error.
I had to manually scan to find the channel (which brings up another "bug" as the manual scan never quits on its own, and will add tons of entries listed by frequency rather than channel number into the results).