- August 2, 2007
- 39
- 0
- Home Country
-
United States of America
I upgraded from 1.0.1.0 to 1.0.2.0.
I upgraded the Schedules Direct client as well. I am getting the TV line-up and schedules with no problem.
I can no longer access my recorded TV items. Our cable provider just re-mapping all the cable channels. I suspect this might have something to do with it. I had to delete all the channels and download the new line-up.
I sure hope the re-mapping of channels has NOTHING to do with what I have recorded - although I suspect it is the problem. Why any programmer would link a recorded media to a channel mapping is beyond me. Doesn't make sense.
How do I fix this?
Furthermore, a MODAL window pops up with the same error message while running MP.
OK, I figured it out.
The column idChannel in the recording table must match an entry in the channel table.
Piss-poor database implementation. Relating non-volatile data (recording) to volatile data (channel) is bad practice. A person will loose all their recording if they change their channel line-up. For example: Cable company changes the line-up or, you move, or you switch from cable to satellite or vice-versa.
I upgraded the Schedules Direct client as well. I am getting the TV line-up and schedules with no problem.
I can no longer access my recorded TV items. Our cable provider just re-mapping all the cable channels. I suspect this might have something to do with it. I had to delete all the channels and download the new line-up.
I sure hope the re-mapping of channels has NOTHING to do with what I have recorded - although I suspect it is the problem. Why any programmer would link a recorded media to a channel mapping is beyond me. Doesn't make sense.
How do I fix this?
MediaPortal.Log said:2009-08-17 18:25:28.405600 [Warn.][MPMain]: TVRecorded: Error building item from recording C:\Media\TV\Recordings\Mickey Mouse Clubhouse - 61 DISN - 2008-10-18.ts
Error: UnexpectedRowCountUnclassified
Gentle.Common.GentleException: The number of returned rows 0 did not match the expected count of 1.
If concurrency control is enabled this may indicate that the record was updated or deleted by another process.
at Gentle.Common.Check.FailWith(Severity severity, Error error, Exception e, String msg)
at Gentle.Common.Check.Fail(Exception e, Error error, Object[] args)
at Gentle.Common.Check.Verify(Boolean condition, Error error, Object[] args)
at Gentle.Framework.ObjectFactory.GetInstance(Type type, SqlResult sr, Key key)
at Gentle.Framework.PersistenceBroker.RetrieveInstance(Type type, Key key, IDbConnection conn, IDbTransaction tr)
at Gentle.Framework.PersistenceBroker.RetrieveInstance[T](Key key)
at Gentle.Framework.Broker.RetrieveInstance[T](Key key)
at TvDatabase.Channel.Retrieve(Int32 id)
at TvDatabase.Recording.ReferencedChannel()
at TvPlugin.TvRecorded.BuildItemFromRecording(Recording aRecording)
2009-08-17 18:25:28.406600 [Warn.][MPMain]: TVRecorded: Error building item from recording C:\Media\TV\Recordings\Mickey Mouse Clubhouse - 61 DISN - 2008-10-18_1.ts
Error: UnexpectedRowCountUnclassified
Gentle.Common.GentleException: The number of returned rows 0 did not match the expected count of 1.
If concurrency control is enabled this may indicate that the record was updated or deleted by another process.
at Gentle.Common.Check.FailWith(Severity severity, Error error, Exception e, String msg)
at Gentle.Common.Check.Fail(Exception e, Error error, Object[] args)
at Gentle.Common.Check.Verify(Boolean condition, Error error, Object[] args)
at Gentle.Framework.ObjectFactory.GetInstance(Type type, SqlResult sr, Key key)
at Gentle.Framework.PersistenceBroker.RetrieveInstance(Type type, Key key, IDbConnection conn, IDbTransaction tr)
at Gentle.Framework.PersistenceBroker.RetrieveInstance[T](Key key)
at Gentle.Framework.Broker.RetrieveInstance[T](Key key)
at TvDatabase.Channel.Retrieve(Int32 id)
at TvDatabase.Recording.ReferencedChannel()
at TvPlugin.TvRecorded.BuildItemFromRecording(Recording aRecording)
Furthermore, a MODAL window pops up with the same error message while running MP.
OK, I figured it out.
The column idChannel in the recording table must match an entry in the channel table.
Piss-poor database implementation. Relating non-volatile data (recording) to volatile data (channel) is bad practice. A person will loose all their recording if they change their channel line-up. For example: Cable company changes the line-up or, you move, or you switch from cable to satellite or vice-versa.