Guide2J & TVGuide Errors (but CDK OK)

[CaptainVideo]

Right now I can only schedule using XRecording's advanced scheduler with CDKScheduler and priorityrecordings. It works really well, but it isn't good for those snap decisions where you see something you HAVE to record.

In TVGuide I always get this error when I try to add or delete a scheduled recording: "No connection could be made because the target machie actively refused it"

In Guide2J I now always get the error: "No connection could be made because the target machine actively refulsed it".

Restarting doesn't help.

Anyone know how these two errors may be related? What log do I need to look at? I don't see any errors on the most recently updated ones: rectracker.log, rectracker.exe.log, archive.log, gbpvrrecordingservice.exe.log,

Thanks for your help!

[KingArgyle]

Is this happening on an MVP or PC?

[CaptainVideo]

Is this happening on an MVP or PC?

PC. I DO have the priorityrecording list pretty loaded up (41 entries), but I don't think that should make any difference. Unless my database is hosed.

One important note: The changes I make DO appear to take most of the time. I just have to "ok" out of the error.

However, while the error in Guide2J doesn't seem to have any ill effects, when I come across it in TV Guide, the recording service freezes on whatever program it is recording and never moves on to the next one.

I don't know if this is related, but today and one other day, my gbpvr.exe.log file baloons to over 100Mb in size. Every 6 seconds there's a complete listing of [VERBOSE] followed by "loading" something. I loaded it up in to Word an there are 16,445 pages for just one day! Restarting the recording service gets things back under control.

[jorm]

> "No connection could be made because the target machie actively refused it"

This error typically means the recording service is not running. Can you check that in your task manager.

[CaptainVideo]

> "No connection could be made because the target machie actively refused it"

This error typically means the recording service is not running. Can you check that in your task manager.

I checked, it was running, but froze after the error. However, the program did show up red after "OK"ing out of the error and restarting the recording service.