No comunication with Recording Service and too many tuners

[Vambo]

I installed GB-PVR about 6 weeks ago with one tuner card(PVR350), then added a second (PVR150). Most things worked ok ,I never got the PVR150s IR blaster to work but everthing else was fine. Then two days ago I started getting "No comunication with Recording Service" errors when scheduling new or manual recordings or live TV. Also the Recording Service status shows that I have got six Tuners installed not two. If I restart the Recording Service it seems to record the scheduled programs. I tried the remadies in other posts, checked all capture source settings , installed GB_PVR after dot net etc. I also remove GB_PVR, deleted gbprv folder and did a complete new install but with no improvment. I'd be greatfull if anybody can give me an pointers to a fix.

Asus - K8N-E Delux MB
Ahlon 64 3000+
1G Ram
PVR350
PVR150

[sub]

Then two days ago I started getting "No comunication with Recording Service" errors when scheduling new or manual recordings or live TV. Also the Recording Service status shows that I have got six Tuners installed not two.

Both of these indicate the client application (gbpvr.exe) is unable to talk to the recording service. It sounds like you have firewall software getting in the way (or possibly antivirus software).

[Vambo]

Thank you for the fast response, you were right. Norton Antivirus had decided to block access to the recording service after a virus update.
Many thanks.

[funkybro_uk]

Up until this morning GB-PVR was communicating fine with the recording service, and my MediaMVP, even with Windows Firewall running. Then, somebody suggested to me it might help me get my FTP server running if i disabled windows firewall and let the router take charge of firewall things.

Now I get the behaviour described in this thread (Recording Service -> Show Status indicating six capture tuners), and MVP just sits on the five squares bootup sequence doing nothing.

Needless to say, restoring Windows Firewall does not fix this. Somebody help me please, my girlfriend is about to kill me if she can't watch X-Factor!

funkybro

[funkybro_uk]

After reinstalling GBPVR this is still happening. What have I done wrong here, everything was working so well! here are the logs, thx

[funkybro_uk]

One further piece of information, I noticed the recording service was not running, when browsing the Services menu. I tried to start it, and got the message

"The GB-PVR Recording Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

[bgowland]

The zip file seems to be corrupt, I can't open it with WinZip or the default XP compressed folder system.

Have you checked your application/system logs with Event Viewer to see if there are any entries relating to why the service isn't starting - this, I presume, is obviously the root of the problem.

Cheers,
Brian

[funkybro_uk]

Really? I can open it ok.

I suspect this snippet from GBPVR.exe.log may indicate a problem:
01/10/2005 19:55:03.265 VERBOSE [2] About to connect to remote recording service
01/10/2005 19:55:03.265 VERBOSE [2] getValue() loading new key/value into cache: /settings/RecordingServiceLocation
01/10/2005 19:55:03.265 VERBOSE [2] getValue: /settings/RecordingServiceLocation : tcp://localhost:7968/RecordingRemote
01/10/2005 19:55:03.281 ERROR [2] Unable to find node: /settings/SpecialElements/SpecialElement[@name="MenuType"]

[funkybro_uk]

Aha!

Event viewer gives:

Service cannot be started. System.TypeInitializationException: The type initializer for "System.Net.IPAddress" threw an exception. ---> System.TypeInitializationException: The type initializer for "System.Net.Sockets.Socket" threw an exception. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
at System.Net.Sockets.Socket.InitializeSockets()
at System.Net.Sockets.Socket..cctor()
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.InitializeSockets()
at System.Net.IPAddress..cctor()
--- End of inner exception stack trace ---
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(Int32 port)
at GBPVR.RecordingService.RecordingService.OnStart(String[] xf18a926310372520)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

[sub]

It sounds like something is wrong with the TCPIP setup on you machine.

If you google for "System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full" you'll find a few hits, and discussions about protocol bindings on your machine.