Any one using MSDE or SQL2005Express?

[Urbansk]

OK, I've fixed this one - not quite in the way you're suggesting, but it should do the job.

If you can tell me exactly what is wrong, or as much detail about this specific problem as you can, then I'll also try to correct this one. I wont be installing MSDE or SQL2005 Express to test this, so you'll need to give me all the information.

Here goes!

When trying to schedule a reoccurring recording all seems to work but not for Record Season (all episodes this channel). I get an error in gbpvr.exe.log and no appearence in Recordings/Reoccuring. In the enclosed zip i will se two documents with the contents of the two tables in use(my guess) and gbpvr.exe.log for each type of recording.
gbpvr.exe.1.zip (all episodes this channel)
gbpvr.exe.2.zip (all in this weakly timeslot, this channel)
gbpvr.exe.3.zip (all in this daily timeslot, this channel)

For the first log you will se a cast error wich will not occourr in the others.

A feature request would be to be able to se in Recordings/Reoccuring what kind of scheduletype it is.

[sub]

I dont think this error is caused by the date time field you've identified in the first page of this thread. I suspect it doesnt like the character set used by the filename or something similar.

[spyork]

I dont think this error is caused by the date time field you've identified in the first page of this thread. I suspect it doesnt like the character set used by the filename or something similar.

When you are referring to the character set of the filename, are you referring to letters with accents for example? I have tried using the same recording option with the show Seinfeld and had the same problem as Urbansk.

[sub]

I was really just saying that I dont think its the date time field - I've had a good look at these this morning, and there isnt really anything I could be doing wrong (or differently) with them. I dont format them into character strings myself - thats all done behind the scenes in ADO.NET and the DB provider. The integer fields should be fine, so that leaves the filename field.

[Urbansk]

I was really just saying that I dont think its the date time field - I've had a good look at these this morning, and there isnt really anything I could be doing wrong (or differently) with them. I dont format them into character strings myself - thats all done behind the scenes in ADO.NET and the DB provider. The integer fields should be fine, so that leaves the filename field.

SUB, There must be a differens in the way you handle scheduled reoccuring recordings.

How can I see in the DB that i have a scheduled recording (all episodes this channel). What am I suposed to look for. How does that differ from the other two types of reoccuring recordings.

There must be a differens in the way you handle the data between these types of recordings.

Can you show in some pseudocode how you acomplish this?

RecordingFactory.save()
Save(): Inserted new scheduled recording
RecordingFactory.save()
Save(): Inserted new reoccuring extras record

[Urbansk]

I was really just saying that I dont think its the date time field - I've had a good look at these this morning, and there isnt really anything I could be doing wrong (or differently) with them. I dont format them into character strings myself - thats all done behind the scenes in ADO.NET and the DB provider. The integer fields should be fine, so that leaves the filename field.

I have looked at traces from the various schedule types.

exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level,
pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(6),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12
int',813,1,N'Martha',0,6,0,25,'Jun 27 2006 1:15:00:000PM','Jun 27 2006 2:05:00:000PM',1,1,2

exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level,
pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(6),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12
int',191,1,N'L word',0,5,0,22,'Jun 26 2006 10:50:00:000PM','Jun 26 2006 11:55:00:000PM',1,1,2


exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level,
pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(11),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12
int',508,1,N'Kameleonten',0,4,0,30,'Jun 27 2006 3:10:00:000PM','Jun 27 2006 4:05:00:000PM',1,1,2



The declaration of P3 varies. In the first two it is a nvarchar(6) in the last nvarchar(11).

The first two is of a schedule type that works the last is from a schedule type that won´t work.

Any closer? I do not know perhaps another dead end.

[sub]

What datatype is used for the filename column in your RECORDING_SCHEDULE table?

[Urbansk]

What datatype is used for the filename column in your RECORDING_SCHEDULE table?

It is nvarchar(255).

[sub]

Both of those strings should happily fit in there.

exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level,
pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P1 2)',N'@P1 int,@P2 int,@P3 nvarchar(6),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12
int',813,1,N'Martha',0,6,0,25,'Jun 27 2006 1:15:00:000PM','Jun 27 2006 2:05:00:000PM',1,1,2

exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level,
pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P1 2)',N'@P1 int,@P2 int,@P3 nvarchar(6),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12
int',191,1,N'L word',0,5,0,22,'Jun 26 2006 10:50:00:000PM','Jun 26 2006 11:55:00:000PM',1,1,2


exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level,
pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P1 2)',N'@P1 int,@P2 int,@P3 nvarchar(11),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12
int',508,1,N'Kameleonten',0,4,0,30,'Jun 27 2006 3:10:00:000PM','Jun 27 2006 4:05:00:000PM',1,1,2

These all use the exact same function to insert this data, the only difference being the integer values for the status, recording_group, recording_type columns, but these shouldnt be causing any problems. Its got to be something to do with the filename.

[Urbansk]

Both of those strings should happily fit in there.

These all use the exact same function to insert this data, the only difference being the integer values for the status, recording_group, recording_type columns, but these shouldnt be causing any problems. Its got to be something to do with the filename.

I can take the exact same show with various schedule type. It will work for all but (all episodes this channel). In the example above there is no special caracters in the filename 'kamelonten'.

If it where the filename I should experience the same problem in the other types of scheduled recordings. It is allways (all episodes this channel) that will not work.


I can se a differens in the chain of events in profiler.

The working types:

1. A insert statement sets the recording type to 5 and specifies a recording group.
exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level, pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(6),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12 int',813,2,N'Martha',4,6,5,25,''2006-06-27 11:45:00:000'',''2006-06-27 14:45:00:000'',1,1,2

2. A select statement
exec sp_executesql N'select * from PROGRAMME p where channel_oid=25 and name=@P1 and start_time > @P2 and not exists (select * from RECORDING_SCHEDULE rs where rs.programme_oid = p.oid and (recording_type <> 5))',N'@P1 nvarchar(6),@P2 datetime',N'Martha',''2006-06-26 21:51:06:000''

3. A insert statement
exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level, pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(6),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12 int',813,1,N'Martha',0,6,0,25,''2006-06-27 13:15:00:000'',''2006-06-27 14:05:00:000'',1,1,2

In the non working schedule types there is another chain.

1. A select statement
exec sp_executesql N'select * from PROGRAMME p where channel_oid=30 and name=@P1 and start_time > @P2 and not exists (select * from RECORDING_SCHEDULE rs where rs.programme_oid = p.oid and (recording_type <> 5))',N'@P1 nvarchar(11),@P2 datetime',N'Kameleonten',''2006-06-26 21:50:06:000''

2.A insert statement first show
exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level, pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(11),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12 int',501,1,N'Kameleonten',0,4,0,30,''2006-06-27 10:15:00:000'',''2006-06-27 11:10:00:000'',1,1,2

3. A insert statement second show
exec sp_executesql N'insert into RECORDING_SCHEDULE (programme_oid, capture_source_oid, filename, status, recording_group, recording_type, manual_channel_oid, manual_start_time, manual_end_time, quality_level, pre_pad_minutes, post_pad_minutes) values (@P1,@P2,@P3,@P4,@P5,@P6,@P7,@P8,@P9,@P10,@P11,@P12)',N'@P1 int,@P2 int,@P3 nvarchar(11),@P4 int,@P5 int,@P6 int,@P7 int,@P8 datetime,@P9 datetime,@P10 int,@P11 int,@P12 int',508,1,N'Kameleonten',0,4,0,30,''2006-06-27 15:10:00:000'',''2006-06-27 16:05:00:000'',1,1,2


There is never an insert that specifies recording_type=5? for the failing schedule. Perhaps the correct function. I am just grasping for a thin straw
(old Swedish saying).