Reply to thread

Message

<blockquote data-quote="CyberSimian" data-source="post: 1103642" data-attributes="member: 141969">I am using MP 1.9.0 pre, with &quot;aMPed&quot; skin, on 32-bit Vista, with client and server on the same system.Last night I was watching live TV when the screen froze.&nbsp; Several seconds later an error message was displayed, saying that a TCP/IP error had occurred.&nbsp; I tried restarting live TV, but it failed with the same error.&nbsp; There were three recordings being made, but I could not determine whether they were still active, or whether TV Server had stopped.&nbsp; So I decided to reboot.&nbsp; After reboot, the recordings restarted, and live TV was available again.This morning I looked at the error logs, including the Windows Event Logs.&nbsp; For the first time ever, the Windows Event Log actually gave a useful explanation.&nbsp; I tried to cut-and-paste the explanation, but cut-and-paste does not work on the event-log panels, so I took a screen shot (see attachment).&nbsp; I hope that the text is legible.The explanation in the event log says that MP or TV Server was disconnecting and then reconnecting so rapidly that the system used up all available ports and no more were available (so the TCP/IP connection to the SQL server could not be established).&nbsp; Apparently, TCP/IP does not allow a port to be re-used unless a minimum amount of time has elapsed.So, do I need to increase the number of ports available on my system?&nbsp; If so, how do I do that?Or is the problem that my system is doing far too many disconnects/reconnects, possibly due to some incorrect setting for MP or TV Server?&nbsp; If so, which setting?I have included relevant logs in the zip file.&nbsp; Thank you.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1103642, member: 141969"] I am using MP 1.9.0 pre, with "aMPed" skin, on 32-bit Vista, with client and server on the same system. Last night I was watching live TV when the screen froze. Several seconds later an error message was displayed, saying that a TCP/IP error had occurred. I tried restarting live TV, but it failed with the same error. There were three recordings being made, but I could not determine whether they were still active, or whether TV Server had stopped. So I decided to reboot. After reboot, the recordings restarted, and live TV was available again. This morning I looked at the error logs, including the Windows Event Logs. For the first time ever, the Windows Event Log actually gave a useful explanation. I tried to cut-and-paste the explanation, but cut-and-paste does not work on the event-log panels, so I took a screen shot (see attachment). I hope that the text is legible. The explanation in the event log says that MP or TV Server was disconnecting and then reconnecting so rapidly that the system used up all available ports and no more were available (so the TCP/IP connection to the SQL server could not be established). Apparently, TCP/IP does not allow a port to be re-used unless a minimum amount of time has elapsed. So, do I need to increase the number of ports available on my system? If so, how do I do that? Or is the problem that my system is doing far too many disconnects/reconnects, possibly due to some incorrect setting for MP or TV Server? If so, which setting? I have included relevant logs in the zip file. Thank you. -- from CyberSimian in the UK [/QUOTE]

Verification