Recording service crash

[pastro]

A while back I posted a couple items on the wishlist because my recording service was crashing. In reality I think it was never starting after running config.

I think I have it isolated to having two machines connected to the same recordingservicelocation.
This extra connection occured because the second machine was a client at one point and the recordingservicelocation didn't update when I changed the machine back to standalone. I have since changed the second machine to point to localhost for the recordingservicelocation and haven't had any hiccups since.

I'm not really asking for help, just posting info.

Anyway here is the error event

Event Type: Error

Event Source: GB-PVR Recording Service
Event Category: None
Event ID: 0
Date: 3/2/2007
Time: 2:22:11 PM
User: N/A
Computer: ASTROTV
Description:
Service cannot be started. System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port)
is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.TcpListener.Start(Int32 backlog)
at System.Net.Sockets.TcpListener.Start()
at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(Int32 port)
at GBPVR.RecordingService.x116139cea0d00aa9.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

[sub]

That error is just saying the port is already in use, so GB-PVR cant listen on it. This most likely occurred because either (1) the software is already running, or (2) the port is being held open by something (either a stale connection, or firewall).

[pastro]

That error is just saying the port is already in use, so GB-PVR cant listen on it. This most likely occurred because either (1) the software is already running, or (2) the port is being held open by something (either a stale connection, or firewall).

hmmm - probably not the issue then. From what you are saying, I was restarting a service that was running and that caused the error event.
Thanks for the info.