No connection could be made...

[frankmcg]

Anyone seen this error before:

"System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it" ?

I think it's to do with my box not coming out of standby properly or something like that? Basically was trying to record a programme called "Extras" and happened to be home when it was starting. Computer switched itself on OK but then didn't seem to be recording. That's when I saw that I was getting the above error in the logs, and if I tried to go to LiveTV I got something similar. Any ideas?

Have attached the relevant log zipped up.

[HtV]

Anyone seen this error before:
"System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it" ?

http://forums.gbpvr.com/search.php?searchid=578944

For anyone to give any kind of solution, you really need to give more info/specs and more logs.

[sub]

Its most likely either:

1) you've got some firewall software getting in the way of communication between components, or

2) it relates post #2 from the sticky 'v0.98.13 survival guide' thread: http://forums.nextpvr.com/showthread.php?t=19525

[frankmcg]

Thanks Sub but it can't be either of those as I have no anti virus, firewall or anything else running on my HTPC as it sits safely behind a hardware firewall on my router.

Re HtV's post - I can't replicate the problem unfortunately (it only happens maybe once a week) and the log I attached above was the only one which seemed relevant as the rest have now been overwritten. I'm running MCE on a A64 3500+ and a hauppauge nova-t pci card.

As I mentioned, it seems to be something to do with coming out of standby - perhaps the XP bug whereby coming out of standby too many times eventually messes things up and needs a full reboot?

[sub]

At the time you get this error, is GBPVRRecordingService.exe shown in the task list?

Reproduce the problem, then zip and attached the logs and I'll take a look. (a full set of logs)

[frankmcg]

Took a couple of weeks but it's just happened again (of course just when it was a program I was really looking forward to watching!).

Full logs attached. Program in question was set for 21:00 tonight on BBC1 called "The State Within" - referenced at the bottom of the GBPVRRecordingService.exe log attached. You'll see that the computer has woken up several times without a problem in the last few days to record various things without a problem, and I'm pretty sure it woke up for this recording too, just couldn't start the record.

Also getting the "Error: No connection could be made because the target machine actively refused it" if I try to watch livetv now. GBPVRRecordingService.exe isn't currently in the task manager processes list.

Thanks for any help!

[sub]

It looks like it died starting the BDA device, but doesnt really provide any clues why.

Is there any crash info in the Windows Event Viewer?

[frankmcg]

Yes there is, at 20:59 ie just before the prog was due to start I get the following application error:


0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 47 42 50 ure GBP
0018: 56 52 52 65 63 6f 72 64 VRRecord
0020: 69 6e 67 53 65 72 76 69 ingServi
0028: 63 65 2e 65 78 65 20 31 ce.exe 1
0030: 2e 30 2e 32 33 37 39 2e .0.2379.
0038: 32 36 33 39 33 20 69 6e 26393 in
0040: 20 4d 70 67 4d 75 78 2e MpgMux.
0048: 61 78 20 35 2e 30 2e 30 ax 5.0.0
0050: 2e 37 32 37 20 61 74 20 .727 at
0058: 6f 66 66 73 65 74 20 30 offset 0
0060: 30 30 31 38 66 63 63 0018fcc

[sub]

0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 47 42 50 ure GBP
0018: 56 52 52 65 63 6f 72 64 VRRecord
0020: 69 6e 67 53 65 72 76 69 ingServi
0028: 63 65 2e 65 78 65 20 31 ce.exe 1
0030: 2e 30 2e 32 33 37 39 2e .0.2379.
0038: 32 36 33 39 33 20 69 6e 26393 in
0040: 20 4d 70 67 4d 75 78 2e MpgMux.
0048: 61 78 20 35 2e 30 2e 30 ax 5.0.0
0050: 2e 37 32 37 20 61 74 20 .727 at
0058: 6f 66 66 73 65 74 20 30 offset 0
0060: 30 30 31 38 66 63 63 0018fcc

Thats good, the answer is right there. Its crashing in the Cyberlink MPEG Mux. A couple of people have had this problem in the past. They corrected it by changing versions of the Cyberlink mux.

[frankmcg]

Great thanks Sub, always good to hear someone has had the problem before and even better that there's a solution! I'll get digging for a different version of the mux - off the top of your head any particular version that's recommended?