Recording Service Crash: FATAL UNHANDLED EXCEPTION

[dwpoet]

I recently upgraded from 09612 to 09713 to 09808, and converted to SQL.

Whenever a change is made in the recording schedule, on Exit from GBPVR, Recording Service crashes with the exact same error code as in v0.98.8 Survival Guide post #2.

I do NOT have NOD32, Panda Antivirus, Net Limiter, McAfee, nor any other anti-virus running that I'm aware of. In Windows Security Center, Firewall is Off, and Virus Protection is Not Monitored.

Can anyone help?

[XP Home, PVR-350]

[sub]

It will be the same cause. You have something installed on your machine that is hooked into your networking for the purposes of monitoring traffic, but it is not correctly handling the overlapped IO that is performed by .NET remoting.

Can you see if there are any GB-PVR Recording Service errors listed in the Windows Event Viewer? This will sometimes give clues that help find exactly what software you have installed that is causing this problem.

[dwpoet]

From Event Viewer:

.NET Runtime 2.0 Error

Description:
Faulting application gbpvrrecordingservice.exe, version 1.0.2445.14611,
stamp 00000038, faulting module sliplsp.dll, version 5.0.0.0, stamp
4468ed42, debug? 0, fault address 0x00004220.

Tried repairing .NET 2.0 and deleting and reinstalling GBPVR. It still crashes.

[sub]

Search the hard drive for a file called "sliplsp.dll", then view the properties of the file to see who the manufacturer is.

[sub]

Google indicates its from some app called 'SlipStream Internet Accelerator Server'. This app is causing the problem.

[dwpoet]

"sliplsp.dll" is part of Webrunner Accelerator that I've been using. Exiting that app did not help. Tried renaming sliplsp.dll and G-PVR Recording Service fails to start.

Event Viewer description (part):
Service cannot be started. System.Net.Sockets.SocketException: The requested service provider could not be loaded or initialized at System.Net.Sockets.Socket.ctor(AddressFamily addressFamily, ...........
(and much more)

[will have to follow up on this later. I'm out of time for now]

[sub]

This error is pretty clear cut, and the Windows has specifically identied sliplsp.dll as the problem module in the event view message, so is definitely the cause

Tried renaming sliplsp.dll and G-PVR Recording Service fails to start.

Event Viewer description (part):
Service cannot be started. System.Net.Sockets.SocketException: The requested service provider could not be loaded or initialized at System.Net.Sockets.Socket.ctor(AddressFamily addressFamily, ...........
(and much more)

[will have to follow up on this later. I'm out of time for now]

I'm not familiar with the specific app, but obviously renaming sliplsp.dll is not the right way to do this (and leaves you with broken networking). You'd probably need to uninstall it, or set some exclusion for the GB-PVR processes.

Exiting the app is often not enough. This type of layered service provider hook DLL will often be loaded anyway.

[dwpoet]

This is the reponse from customer service re: Webrunner:

"From the text of your email, I have surmised that webrunner functions, and
that this issue did not occur before you installed GBPVR. We do not support
third party software (referring to GBPVR) nor do we guarantee that webrunner
will work with other applications. Sorry but we cannot assist you with this
issue. you may want to try uninstalling GBPVR, if you do not wish to do so,
contact the manufacturer of that software for advice."

Could the problem be related to the switch to SQL and/or .NET 2.0?

[sub]

Its caused by these few applications that monitor/intercept network traffic not correctly handling the overlapped I/O used with .NET 2.0 remoting. There is plenty of discussion on the net about this incompatibility, and the problem affects any app that uses .NET 2.0 remote with one of these apps installed (ie, so lots more apps than just GB-PVR).

There is a lot of other utilities of this type that do not have the same problem.

All I can suggest is uninstalling webrunner. There is nothing I can do to work around the problem from my end.

[sub]

It seems Microsoft now have a patch that may help: http://support.microsoft.com/kb/923028/en-us

SYMPTOMS
When you run a Microsoft .NET Framework 2.0 Remoting application, you may receive the following error message:

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Additionally, this problem may occur in .NET Framework 2.0 Remoting applications on a computer that is running certain types of driver software or antivirus programs.