Detached tuners still show up on TV Server Configuration (1 Viewer)

[risu]

I have two dual tuner (DVB-T) USB sticks. If I stop TVservice.exe, take one off and restart tv service again I still see detached tuner listed with TV Server Configuration. It tells tuner type is Unknown (instead of DVB-T). I can remove the devices from list with Remove-button but when I restart TV service again, detached tuners shows on list again. So there's some database issue there. I'm using Vista 32bit with MSSQL installed automatically by RC1 refesh.

 

[Paranoid Delusion]

Hi risu

Chances are there are associations with epg, recordings etc, that cannot be deleted, when you remove the card.

Only thing to do is delete db and start again (export channels first).

 

[risu]

I've already figured out that fresh database works but it still doesn't change the fact that this still is a bug It's better than before though: when TV Server setup got into endless loop when device was removed, huge thanks for the dev who fixed that.

Why I'm reporting this is that it if there's a button to remove device and button doesn't do what it's supposed to do, it should be corrected. User shouldn't need to clear dependancies on database before getting rid of device? Or at least if there's some stuff that need to be dealt with before device can be removed, IMHO configuration app should do that for user.

I probably have had at least scheduled recordings on removed device.

 

[Bram]

Even without associations with the epg the card stays present in the tuner cards overview.

 

[SciDoctor]

The recursive error that accompanies this 'bug' (unless you dissable the removed tuner in TVSETUP) as the TVSERVICE keeps trying to 'find' the missing tuner/s.

2008-05-21 19:14:01.264191 [4]: TVController:ValidateTvControllerParams - incorrect parameters used! cardId 1 _cards.ContainsKey(cardId) == False CardPresent False
2008-05-21 19:14:01.279816 [4]: at TvService.TVController.ValidateTvControllerParams(Int32 cardId, Boolean checkCardPresent)
at TvService.TVController.GetUsersForCard(Int32 cardId)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(IMessage reqMsg)
at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)
at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[] args)
at System.Runtime.Remoting.Channels.ChannelServices.DispatchMessage(IServerChannelSinkStack sinkStack, IMessage msg, IMessage& replyMsg)
at System.Runtime.Remoting.Channels.DispatchChannelSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.SoapServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.Tcp.TcpServerTransportSink.ServiceRequest(Object state)
at System.Runtime.Remoting.Channels.SocketHandler.ProcessRequestNow()
at System.Runtime.Remoting.Channels.RequestQueue.ProcessNextRequest(SocketHandler sh)
at System.Runtime.Remoting.Channels.SocketHandler.BeginReadMessageCallback(IAsyncResult ar)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.CompleteCallback(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)


Soon will cause the error log to become super-large.