TvCheckScheduleTask error 0x30020 since 3.0

[tivotal]

Subsequent to my SVR-2000 upgrading to 3.0 on Friday night (and possibly caused by my reinstalling TurboNet support), my TiVo will no longer record. When manually recording, or updating SeasonPass options I get the following error:

"There was an error

An internal error occurred while adding this program (or Season Pass) to the To Do List. If this is a recurring problem...[snip]

ConflictMgr DoRecordShowing: ProposeExplicitSelection returned err 0x30020"

ToDoList shows none scheduled despite Season Pass Upcoming Episodes indicating it intends to record Episodes.

/var/log/tvlog shows:

Jun 9 15:55:48 (none) Scheduler[132]: DataChanged:PROGRAM_GUIDE
Jun 9 15:55:51 (none) Scheduler[132]: Abr-- DataChanged:0x90009
Jun 9 15:55:55 (none) Recorder[130]: Adding check schedule task
Jun 9 15:56:15 (none) last message repeated 2 times
Jun 9 15:56:23 (none) Scheduler[132]: Mempool highwater 14436
Jun 9 15:56:23 (none) Scheduler[132]: DataChanged:PROGRAM_GUIDE
Jun 9 15:56:25 (none) Recorder[130]: Adding check schedule task
Jun 9 15:56:27 (none) Scheduler[132]: Abr-- reason changed from 'UI' to 'None'
Jun 9 15:56:27 (none) Scheduler[132]: Abr-- DataChanged:0x30020
Jun 9 15:56:35 (none) Recorder[130]: Adding check schedule task

/var/log/tverr shows:

Jun 9 16:31:38 (none) Recorder[130]: Error checking schedule: 0x30020
Jun 9 16:31:38 (none) TvCheckScheduleTask::Run[130]: error 0x30020

It looks to me like there has been some kind of corruption in the scheduler database. Any ideas to fix this short of a full reset (which will lose a lot of material being readied to archive onto SVCD)?

[tivotal]

For closure: problem fixed by doing a full system reset followed by guided setup. At least guided setup over broadband is nice and fast, and I didn't have to restore from backups.

[Scotty2]

I am having the exact same problem. I can't record anything, because of the error. I have a Tivo full of shows that I don't want to lose.

Does the full reset kill your shows? What is the full reset? Unfortunatly I didn't get a backup of 2.5.1 before I got 3.0.

[tivotal]

I spent several days pulling off tystreams onto my Linux box, and even then had to sacrifice some material. It may be that you can find a level of reset that doesn't wipe the shows; however, the full system reset (I don't have access to my TiVo while writing this) clears pretty much everything: recordings, season passes etc and makes you also do a guided setup. I'm not 100% sure of the name of the full reset option, but from memory it was right down the bottom of the list of reset options. I'll have a look when I get home tonight.

[SuperVHS]

Did you try a simple Guided Setup first?

[tivotal]

I've had another look at the System Reset page.

As the problem has to do with scheduling databases related to the To Do List, I think there is some chance that the "Clear Program Data & To Do List" will fix the problem, and it looks like this option will not remove recordings. I would suggest trying this option first before using the "Clear and delete everything" (which is what I used and you can be confident will work as a fallback). The downside of this fallback option is that it will delete all of your recordings.

[tivotal]

> Did you try a simple Guided Setup first?

Yes - sorry for not mentioning this before. I used the full delete method as I'd run out of time to try multiple efforts, and pulled off all that I wanted to archive. I think it is definitely worth trying the "Clear Program Data & To Do List" reset.

[Scotty2]

I fixed my problem without deleting my shows!! Use the clear program data & To Do List on the System Reset Menu. You lose your guide data and season passes, so write down your season passes and make another call after running the reset.

Your shows are intact, and now you can record.

By the way, this problem is caused by booting the old ver 2.5.1 software on the other partition after receiving 3.0. Ver 3.0 changes the database format, running 2.5.1 after the conversion corrupts it.

I had to remove the disk to edit the rc.sysinit file to reenable the bash prompt.

Hope this helps someone...

[keith721]

@!!!#$%&*?! Sony standalone did the same thing to me, after 3.0 update came in. had to restore a factory image backup of 2.5.1 to recover. it's been a week now, and the 3.0 update still hasn't come back down, yet. :rolleyes:

anyone think it might be a good idea to wipe the old 2.5.x kernel and root partitions, to prevent this sort of thing from happening?

just wondering. . . :confused: