.97 recording service error
|
2006-05-23, 01:16 AM
Recenlty, after the new release, Ive been having to restart the recording service sometime after a recording, in order to watch Live TV, be cause i get the "no connection could be made because the target machine actively refused it" message. anything obvious that I'm doing wrong?
2006-05-23, 01:20 AM
Are you running NOD32, Panda Antivirus or Net limiter? These can cause the recording service to crash.
Check the Windows Event Viewer for any reported service crashes.
2006-05-23, 01:25 AM
Im not running any of those,
The GB-PVR Recording Service service terminated unexpectedly. It has done this 1 time(s). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. This happened at 9:02:53
2006-05-23, 01:35 AM
Does it give you any more detail? Quite often they'll say the offending module. For example, when it was crashing in NOD32, it says imon.dll.
2006-05-23, 01:44 AM
nope, no listed dll or exe or any reference to an offending module. Al it says is that the sourec is "Source: Service Control Module"
Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7034 Date: 5/22/2006 Time: 9:02:53 PM User: N/A Computer: ERIC Description: The GB-PVR Recording Service service terminated unexpectedly. It has done this 1 time(s). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Thtas the full event report
2006-05-23, 02:39 AM
Unfortunately that doesnt give me much to go on. Can you please post your GBPVRRecordingService.exe.log next time it fails.
2006-05-23, 02:54 AM
I have a question about that though, i looked at the recording service log, awhile back, to see if i could find anything, and the last entry was that it was running Postprocessing.bat, then crashed. Currently, Postprocessing.bat is blank, should there be anything in it? i dont use any archiver or other recording plugins.
2006-05-23, 03:06 AM
Ah, there is a bug that has been fixed for whenever I do a maintenance release.
You cant have an existing but empty (or bad) PostProcessing.bat/ParallelProcessing.bat/UpdateEpg.bat/PostUpdateEpg.bat. This can cause a crash. The next release protects against this difference between .net 1.1 and .net 2.0 I forgot about this, so good thing you mentioned it.
2006-05-23, 03:15 AM
Quote:You cant have an existing but empty (or bad) PostProcessing.bat/ParallelProcessing.bat/UpdateEpg.bat/PostUpdateEpg.bat. This can cause a crash. The next release protects against this difference between .net 1.1 and .net 2.0 Wow, that's interesting. A big leap forward for M$oft. Does "empty" also include one that has rem lines (i.e. nothing runs) or must it be COMPLETELY empty (or bad) for a failure? k.
2006-05-23, 03:27 AM
I'm not sure. I havnt tested a very wide set of conditions. Having seen the one scenario was enough to cause me to check all the batch files I call, and add protection to them all.
The problem was spotted by another user that RenameRecording.exe in the file, which hasnt been updated for v0.97.7 compatibility yet, so he deleted the line leaving an empty file. Under .net 1.1 this would not cause an error. Under .net 2.0 it'll throw an exception, which isnt a huge problem as long as you know to expect it. |
|
|
