Error: "..target machine actively refused it"

[dusadus]

It seems obvious to me that i get this error message when the GBPVRrecording program crashes. When it is listed in the processes of my taskmanager GBPVR works fine. However, after scheduling recording, this application is no longer listed in taskmanager. When I hit restart recorder program, the command dialog box opens and the process appears again in the taskmanager but only for a second, then it disappears. So it seems to load, then unload or crash immediately.

Anyone help me trouble shoot?

[sub]

It sounds like you've go something setup wrong in your capture source settings, which causes it to crash when it starts a recording.

[dusadus]

i can record while watching live tv just fine, and time shifting seems to work without a hitch. It is only when I schedule a recording that it screws up. Also when my computer goes to standby, gb-pvr will not work upon waking.

[GSpanFan]

I seem to be having the same problem...

I recently bought a Hauppauge PVR-150, after seeing GB-PVR in action, and briefly used the program and recording service without a problem. I noticed a few skipping problems when watch live tv, and so decided it might be worthwhile to update the drivers.

I then installed new drivers for the card and completely removed and reinstalled GB-PVR. Now the recording sevice doesn't start when timed, a 0 byte file is created, but nothing recorded. Also it says in the recording/pending menu that the file is recording when in fact it is not. Additionally it continues to say it is recording the program outside of the show's actual time slot. Any suggestions? See my recording service log below... I suspect the problem has something to do with the "ConnectPins failed!" line. Thanks for any help.

19:29:03.480 INFO Log started
19:29:03.480 VERBOSE ConexantRecorder::StartRecording(1, 1, 55, 0)
19:29:03.490 VERBOSE Capture Device is based on BlackBird architecture
19:29:03.490 VERBOSE Capture Device is using Conexant (derived) drivers
19:29:03.490 VERBOSE Loading filter names
19:29:03.490 VERBOSE Found names:
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II Crossbar
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II Capture
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II TvTuner
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II TvAudio
19:29:03.530 VERBOSE ConnectPins: 'Analog Audio' to 'TVAudio In'
19:29:03.770 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In'
19:29:03.770 VERBOSE Looking for encoder filter
19:29:03.780 VERBOSE - Hauppauge WinTV PVR PCI II Encoder
19:29:03.800 VERBOSE ConnectPins: '656' to '656'
19:29:04.061 VERBOSE ConnectPins failed!
19:29:04.101 VERBOSE put_Mode(AMTUNER_MODE_TV)
19:29:04.261 VERBOSE put_CountryCode(1)
19:29:04.411 VERBOSE put_TuningSpace(1)
19:29:04.411 VERBOSE put_InputType(0, 0)
19:29:04.561 VERBOSE put_ConnectInput(0)
19:29:04.712 VERBOSE put_Channel(55, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)
19:29:04.862 VERBOSE get_VideoFrequency() returns 409250000
19:29:04.862 VERBOSE get_CountryCode() returns 1
19:29:04.862 VERBOSE About to query available formats
19:29:04.872 VERBOSE Recorder::SetConfigurationECP()
19:29:04.882 INFO Firmware Version 2.5.32

Audio Firmware Version <<can't read now>>

Model 26032 Rev C182
Serial No: 7934486
Tuner: 82
Decoder: 28
AudioIC: 35
IR

Input Map: C= 0x000f, S= 0x0003

19:29:04.992 VERBOSE FindFilterByName failed to locate filter: GB-PVR WST SRT Analog
19:29:05.032 VERBOSE getSetting(ListGraphFilters)
19:29:05.042 VERBOSE Graph contains the following filters:
19:29:05.042 VERBOSE - GB-PVR Writer
19:29:05.042 VERBOSE - Encoder
19:29:05.042 VERBOSE - Capture
19:29:05.042 VERBOSE - Hauppauge WinTV PVR PCI II Crossbar
19:29:05.042 VERBOSE - TV Audio
19:29:05.042 VERBOSE - TV Tuner
19:29:05.042 VERBOSE getSetting(SaveGraphFiles)
19:29:05.052 VERBOSE ConexantRecorder::StartRecording() done

[dusadus]

I seem to be having the same problem...

I recently bought a Hauppauge PVR-150, after seeing GB-PVR in action, and briefly used the program and recording service without a problem. I noticed a few skipping problems when watch live tv, and so decided it might be worthwhile to update the drivers.

I then installed new drivers for the card and completely removed and reinstalled GB-PVR. Now the recording sevice doesn't start when timed, a 0 byte file is created, but nothing recorded. Also it says in the recording/pending menu that the file is recording when in fact it is not. Additionally it continues to say it is recording the program outside of the show's actual time slot. Any suggestions? See my recording service log below... I suspect the problem has something to do with the "ConnectPins failed!" line. Thanks for any help.

19:29:03.480 INFO Log started
19:29:03.480 VERBOSE ConexantRecorder::StartRecording(1, 1, 55, 0)
19:29:03.490 VERBOSE Capture Device is based on BlackBird architecture
19:29:03.490 VERBOSE Capture Device is using Conexant (derived) drivers
19:29:03.490 VERBOSE Loading filter names
19:29:03.490 VERBOSE Found names:
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II Crossbar
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II Capture
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II TvTuner
19:29:03.490 VERBOSE Hauppauge WinTV PVR PCI II TvAudio
19:29:03.530 VERBOSE ConnectPins: 'Analog Audio' to 'TVAudio In'
19:29:03.770 VERBOSE ConnectPins: 'Audio Decoder Out' to 'Analog Audio In'
19:29:03.770 VERBOSE Looking for encoder filter
19:29:03.780 VERBOSE - Hauppauge WinTV PVR PCI II Encoder
19:29:03.800 VERBOSE ConnectPins: '656' to '656'
19:29:04.061 VERBOSE ConnectPins failed!
19:29:04.101 VERBOSE put_Mode(AMTUNER_MODE_TV)
19:29:04.261 VERBOSE put_CountryCode(1)
19:29:04.411 VERBOSE put_TuningSpace(1)
19:29:04.411 VERBOSE put_InputType(0, 0)
19:29:04.561 VERBOSE put_ConnectInput(0)
19:29:04.712 VERBOSE put_Channel(55, AMTUNER_SUBCHAN_DEFAULT, AMTUNER_SUBCHAN_DEFAULT)
19:29:04.862 VERBOSE get_VideoFrequency() returns 409250000
19:29:04.862 VERBOSE get_CountryCode() returns 1
19:29:04.862 VERBOSE About to query available formats
19:29:04.872 VERBOSE Recorder::SetConfigurationECP()
19:29:04.882 INFO Firmware Version 2.5.32

Audio Firmware Version <<can't read now>>

Model 26032 Rev C182
Serial No: 7934486
Tuner: 82
Decoder: 28
AudioIC: 35
IR

Input Map: C= 0x000f, S= 0x0003

19:29:04.992 VERBOSE FindFilterByName failed to locate filter: GB-PVR WST SRT Analog
19:29:05.032 VERBOSE getSetting(ListGraphFilters)
19:29:05.042 VERBOSE Graph contains the following filters:
19:29:05.042 VERBOSE - GB-PVR Writer
19:29:05.042 VERBOSE - Encoder
19:29:05.042 VERBOSE - Capture
19:29:05.042 VERBOSE - Hauppauge WinTV PVR PCI II Crossbar
19:29:05.042 VERBOSE - TV Audio
19:29:05.042 VERBOSE - TV Tuner
19:29:05.042 VERBOSE getSetting(SaveGraphFiles)
19:29:05.052 VERBOSE ConexantRecorder::StartRecording() done

Yes that's exactly the problem I have, same capture card! How do you pull up the activity log? Anyone else care to help out a noob?

[GSpanFan]

There are log files created in your gbpvr directory for various functions, among them the recording service...

I putzed with it some more, reinstalling the GBPVR (and .net and the other MS thing required as I'm running Win2k). I got the manual record function to work with the recording service once, but then I could not get the recording service to record a program selected from the guide. Same ConnectPins error again... I wonder if its not the new drivers I installed for the PVR-150?

[mhenning]

Hi everyone!
First(ly), hats of the developer(s) of this. I decided to make the home-brew PVR plunge earlier this week, originally wanting to go with MythTV, but came across this and decided it would do the trick nicely. So far, I love it. So much easier to navigate and setup and seems to be just as customizable.

Now, for my only complaint, and I'm not one to usually do a "me too," but I too am seeing this same problem. Earlier, the only way I could get it to come back was to uninstall GB PVR, delete the directory, and reinstall. Now, I simply restart the Recording service and all seems to be well. Like the others, this happens when I try to schedule a recording (either through the TV Guide or the program search.) I've also installed the latest and greatest Hauppauge drivers and software (no beta however.) No other apps installed or running and not even connected to the Internet, except by modem when it dials out in the wee-hours to update the listings from Zap2It (DirecTV.) I know, dial-up, bleh. No broadband in my part of the state.

Tomorrow I'll try uninstalling all of the newer Hauppauge stuff and reinstall from the CD and report my findings here. I was relieved to see others with the same problem though. It means that this should be a traceable problem.

[Spartane]

Hi,

I too am a new user, and I ran into this problem last night where two shows failed to record.

I'd seen the symptom before so I decided to try and reproduce it. It's easy to reproduce it every time with "Live TV" - all I need to do is to run the GB-PVR configuration utility and then click "Cancel".

After this, "Live TV" will produce the message: "Error: No connection could be made because the target machine actively refused it". I'm assuming that the scheduled recording service will likely have similar issues. Simply running the config program and clicking "OK" instead of "Cancel" will restart things and correct the problem.

This looks like some sort of a bug in the configuration program to me.

I'm running what I believe to be the latest version of GB-PVR version-0.91.12.

[dusadus]

i went back and reinstalled everything, including the older hauppauge 150 drivers that came with the CD. This seems to have this problem. I scheduled a recording and it worked fine. I think the new Hauppauge drivers for the 150 maybe screwing something up w/ scheduled recordings.

However I now am not able to get the scheduled recording to stop at the time it is supposed to. I have posted this on another thread.

You guys can try to roll back to the older hauppauge drivers and see if this helps you.

[mhenning]

You guys can try to roll back to the older hauppauge drivers and see if this helps you.

I tried this earlier today as well, but since I did just purchase the 150 a few days ago, I may have a newer disk. Which version of the driver are you having success with?