home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
v1.2.0 Client Can Not View Live TV from v1.2.0 Server
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 794813" data-attributes="member: 82144"><p>Hi again Solas</p><p></p><p>*Thank you* for taking the time to do that - the logs are great. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>So based on what I see, I think there may be two different things happening here. First, the availability from the laptop issue, but also something strange and possibly completely unrelated going on in TV Server. The second thing is the thing that I spotted in your previous logs, but both are equally concerning.</p><p></p><p>On the first topic: in this set of MediaPortal client logs I see...</p><p></p><p>[COLLAPSE]2011-09-29 20:54:51.469800 [Info.][MPMain(1)]: OnMessage exception<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused :confused:" loading="lazy" data-shortname=":confused:" />ystem.Net.Sockets.SocketException: The requested name is valid, but no data of the requested type was found</p><p></p><p></p><p></p><p>Server stack trace: </p><p></p><p> at System.Net.Dns.GetAddrInfo(String name)</p><p></p><p> at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)</p><p></p><p> at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)</p><p></p><p> at System.Runtime.Remoting.Channels.RemoteConnection..ctor(SocketCache socketCache, String machineAndPort)</p><p></p><p> at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)</p><p></p><p> at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)</p><p></p><p> at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)</p><p></p><p> at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)</p><p></p><p></p><p></p><p>Exception rethrown at [0]: </p><p></p><p> at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)</p><p></p><p> at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)</p><p></p><p> at TvControl.IController.DeleteInvalidRecordings()</p><p></p><p> at TvPlugin.TvRecorded.OnPageLoad()</p><p></p><p> at MediaPortal.GUI.Library.GUIWindow.OnMessage(GUIMessage message)[/COLLAPSE]</p><p></p><p>My first instinct based on the "DNS" and "remoting" phrases is that there is some kind of networking issue - maybe DNS related. I note that you're using "192.168.1.75" as the address of the TV Server. I assume that this is the static IP address for the TV Server.</p><p></p><p>Have you tried using the TV Server hostname?</p><p>Also, have you checked whether disabling firewalls on the server and laptop make any difference?</p><p>Have you also disabled the IPv6 network protocol in the network adapter properties? (IPv6 can sometimes cause trouble)</p><p></p><p>Regarding the second error: it is like your TV Server is constantly trying to tune "WHIODT" for some reason, but it never gets past figuring out which tuners are available. Are you able to examine/query your TV Server database directly? I'm just wondering whether there is a "rogue" schedule in there somewhere that is causing this. Checking the database directly would be the best way to determine whether this is the case, otherwise you could check the schedules section in TV Server configuration for schedules on that channel...</p><p></p><p>I'm at work at the moment so I can't spend any further time examining the logs now, but I will of course attempt to do so over the weekend.</p><p></p><p>Best regards,</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 794813, member: 82144"] Hi again Solas *Thank you* for taking the time to do that - the logs are great. :thx: So based on what I see, I think there may be two different things happening here. First, the availability from the laptop issue, but also something strange and possibly completely unrelated going on in TV Server. The second thing is the thing that I spotted in your previous logs, but both are equally concerning. On the first topic: in this set of MediaPortal client logs I see... [COLLAPSE]2011-09-29 20:54:51.469800 [Info.][MPMain(1)]: OnMessage exception:System.Net.Sockets.SocketException: The requested name is valid, but no data of the requested type was found Server stack trace: at System.Net.Dns.GetAddrInfo(String name) at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6) at System.Net.Dns.GetHostAddresses(String hostNameOrAddress) at System.Runtime.Remoting.Channels.RemoteConnection..ctor(SocketCache socketCache, String machineAndPort) at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew) at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream) at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream) at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at TvControl.IController.DeleteInvalidRecordings() at TvPlugin.TvRecorded.OnPageLoad() at MediaPortal.GUI.Library.GUIWindow.OnMessage(GUIMessage message)[/COLLAPSE] My first instinct based on the "DNS" and "remoting" phrases is that there is some kind of networking issue - maybe DNS related. I note that you're using "192.168.1.75" as the address of the TV Server. I assume that this is the static IP address for the TV Server. Have you tried using the TV Server hostname? Also, have you checked whether disabling firewalls on the server and laptop make any difference? Have you also disabled the IPv6 network protocol in the network adapter properties? (IPv6 can sometimes cause trouble) Regarding the second error: it is like your TV Server is constantly trying to tune "WHIODT" for some reason, but it never gets past figuring out which tuners are available. Are you able to examine/query your TV Server database directly? I'm just wondering whether there is a "rogue" schedule in there somewhere that is causing this. Checking the database directly would be the best way to determine whether this is the case, otherwise you could check the schedules section in TV Server configuration for schedules on that channel... I'm at work at the moment so I can't spend any further time examining the logs now, but I will of course attempt to do so over the weekend. Best regards, mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
v1.2.0 Client Can Not View Live TV from v1.2.0 Server
Contact us
RSS
Top
Bottom