Schedules Direct US/Canadian/Mexico EPG Plugin (Updated August 2010) (6 Viewers)

Paul Jackson

Portal Member
May 15, 2015
31
18
58
Home Country
United States of America United States of America
I think I may try installing MediaPortal on another machine. the other machine doesn't have tuners but hopefully I would be able to get the TV service to start and then see if the schedule direct plugin will work on that machine.
 

2BitSculptor

Super Moderator
  • Team MediaPortal
  • January 23, 2008
    1,948
    498
    South Central Wisconsin
    Home Country
    United States of America United States of America
    I don't think SD will work independently of a tuner scan, as it takes the scanned channel info to grab SD schedules.

    That's why I like my HDHomerun tuners... any computer on the network can see them.
     

    Paul Jackson

    Portal Member
    May 15, 2015
    31
    18
    58
    Home Country
    United States of America United States of America
    it does call the web service on the other machine so I'm going to have to see what is different between the two different machines to attempt to resolve it. The log shows all the channels that it found from schedules direct without complaining.
     

    RonD

    Test Group
  • Team MediaPortal
  • December 20, 2011
    911
    278
    SillyValley CA
    Home Country
    United States of America United States of America
    @Paul Jackson I assume you've done the most basic "reboot" and/or "power cycle" during your battle with Schedules Direct. The error showing "The requested address is not valid in its context 127.0.0.1:50624" localhost/loopback (127.0.01) IP address seems very strange.

    As a test on a system that runs SC-plugin without problems I did a cmd.exe (command line) "ping webservices.schedulesdirect.tmsdatadirect.com" and see the following.

    Code:
    C:\>ping webservices.schedulesdirect.tmsdatadirect.com
    
    Pinging dd.schedulesdirect.org [54.85.117.227] with 32 bytes of data:
    Reply from 54.85.117.227: bytes=32 time=88ms TTL=52
    Reply from 54.85.117.227: bytes=32 time=92ms TTL=52
    Reply from 54.85.117.227: bytes=32 time=87ms TTL=52
    Reply from 54.85.117.227: bytes=32 time=89ms TTL=52
    
    Ping statistics for 54.85.117.227:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 87ms, Maximum = 92ms, Average = 89ms
     

    Paul Jackson

    Portal Member
    May 15, 2015
    31
    18
    58
    Home Country
    United States of America United States of America
    I found the tvservice error log reported the following. I think it ma be my problem. The scheduler direct works on a system that has no tuners, attatched to the same network. It does not have this error. Both servers are running the same WIN 7 64 bit. The one that is working is a slower sever (much slower) and basically a near fresh install of windows.

    Code:
    [2015-05-18 08:29:38,335] [Log    ] [4        ] [ERROR] - Exception   :System.Runtime.Remoting.RemotingException: Remoting configuration failed with the exception 'System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> 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.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(IDictionary properties, IServerChannelSinkProvider sinkProvider, IAuthorizeRemotingConnection authorizeCallback)
       at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary properties, IServerChannelSinkProvider sinkProvider)
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
       at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelFromConfigEntry(ChannelEntry entry)
       at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData, Boolean ensureSecurity)
       at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)'.
       at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)
       at System.Runtime.Remoting.RemotingConfigHandler.DoConfiguration(String filename, Boolean ensureSecurity)
       at System.Runtime.Remoting.RemotingConfiguration.Configure(String filename, Boolean ensureSecurity)
       at TvService.TvServiceThread..ctor()

    I would rather avoid doing a full fresh install on the server that doesn't work. There must be some sort of conflict somewhere. Any pointers and helping to figure out where the conflict is would be helpful. I have tried to uninstall completely media portal and make sure all remaining files have been removed. I'm not sure if anything lingers in the registry.

    here is an netstat -a without the TV service running
    Code:
    Active Connections
    
      Proto  Local Address          Foreign Address        State
      TCP    0.0.0.0:135            Jim-PC:0               LISTENING
      TCP    0.0.0.0:445            Jim-PC:0               LISTENING
      TCP    0.0.0.0:554            Jim-PC:0               LISTENING
      TCP    0.0.0.0:2869           Jim-PC:0               LISTENING
      TCP    0.0.0.0:3306           Jim-PC:0               LISTENING
      TCP    0.0.0.0:5357           Jim-PC:0               LISTENING
      TCP    0.0.0.0:10243          Jim-PC:0               LISTENING
      TCP    0.0.0.0:49152          Jim-PC:0               LISTENING
      TCP    0.0.0.0:49153          Jim-PC:0               LISTENING
      TCP    0.0.0.0:49154          Jim-PC:0               LISTENING
      TCP    0.0.0.0:49155          Jim-PC:0               LISTENING
      TCP    0.0.0.0:49188          Jim-PC:0               LISTENING
      TCP    0.0.0.0:50851          Jim-PC:0               LISTENING
      TCP    0.0.0.0:56756          Jim-PC:0               LISTENING
      TCP    127.0.0.1:1994         Jim-PC:0               LISTENING
      TCP    127.0.0.1:2869         Jim-PC:50791           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50798           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50802           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50808           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50812           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50815           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50833           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50834           ESTABLISHED
      TCP    127.0.0.1:2869         Jim-PC:50855           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50860           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50866           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50871           TIME_WAIT
      TCP    127.0.0.1:2869         Jim-PC:50875           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50793           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50794           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50822           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50846           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50847           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50849           TIME_WAIT
      TCP    127.0.0.1:5357         Jim-PC:50869           TIME_WAIT
      TCP    127.0.0.1:27015        Jim-PC:0               LISTENING
      TCP    127.0.0.1:50834        Jim-PC:icslap          ESTABLISHED
      TCP    127.0.0.1:59243        Jim-PC:0               LISTENING
      TCP    192.168.1.2:139        Jim-PC:0               LISTENING
      TCP    192.168.1.2:2869       192.168.1.1:50313      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50316      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50319      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50322      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50325      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50328      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50331      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50334      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50337      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50340      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50343      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50346      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50349      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50352      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50355      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50358      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50361      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50364      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50367      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50370      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50373      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50374      TIME_WAIT
      TCP    192.168.1.2:2869       192.168.1.1:50376      TIME_WAIT
      TCP    192.168.1.2:5357       192:49381              TIME_WAIT
      TCP    192.168.1.2:50765      Jim-PC:50763           TIME_WAIT
      TCP    192.168.1.2:50780      Jim-PC:50773           TIME_WAIT
      TCP    192.168.1.2:50783      a173-223-204-9:http    TIME_WAIT
      TCP    192.168.1.2:50785      a23-56-83-243:http     TIME_WAIT
      TCP    192.168.1.2:50788      Jim-PC:50781           TIME_WAIT
      TCP    192.168.1.2:50818      Jim-PC:50781           TIME_WAIT
      TCP    192.168.1.2:50819      192.168.1.1:5431       TIME_WAIT
      TCP    192.168.1.2:50823      a23-209-33-144:http    TIME_WAIT
      TCP    192.168.1.2:50824      Jim-PC:50820           TIME_WAIT
      TCP    192.168.1.2:50827      a23-67-242-65:http     TIME_WAIT
      TCP    192.168.1.2:50828      Jim-PC:50825           TIME_WAIT
      TCP    192.168.1.2:50829      a23-209-33-144:http    TIME_WAIT
      TCP    192.168.1.2:50830      a23-67-242-65:http     TIME_WAIT
      TCP    192.168.1.2:50838      192.168.1.1:1780       TIME_WAIT
      TCP    192.168.1.2:50839      192.168.1.1:1780       TIME_WAIT
      TCP    192.168.1.2:50850      Jim-PC:50842           TIME_WAIT
      TCP    192.168.1.2:50856      Jim-PC:50851           TIME_WAIT
      TCP    192.168.1.2:50857      a23-56-83-243:http     ESTABLISHED
      TCP    192.168.1.2:50858      a23-67-244-72:http     ESTABLISHED
      TCP    192.168.1.2:50863      192.168.1.1:5431       TIME_WAIT
      TCP    192.168.1.2:50867      192.168.1.1:5431       TIME_WAIT
      TCP    192.168.1.2:50868      192.168.1.1:5431       TIME_WAIT
      TCP    [::]:135               Jim-PC:0               LISTENING
      TCP    [::]:445               Jim-PC:0               LISTENING
      TCP    [::]:554               Jim-PC:0               LISTENING
      TCP    [::]:2869              Jim-PC:0               LISTENING
      TCP    [::]:3306              Jim-PC:0               LISTENING
      TCP    [::]:3587              Jim-PC:0               LISTENING
      TCP    [::]:5357              Jim-PC:0               LISTENING
      TCP    [::]:10243             Jim-PC:0               LISTENING
      TCP    [::]:49152             Jim-PC:0               LISTENING
      TCP    [::]:49153             Jim-PC:0               LISTENING
      TCP    [::]:49154             Jim-PC:0               LISTENING
      TCP    [::]:49155             Jim-PC:0               LISTENING
      TCP    [::]:49188             Jim-PC:0               LISTENING
      TCP    [::]:56756             Jim-PC:0               LISTENING
      TCP    [::1]:2869             Jim-PC:50912           ESTABLISHED
      TCP    [::1]:50912            Jim-PC:icslap          ESTABLISHED
      UDP    0.0.0.0:427            *:*
      UDP    0.0.0.0:500            *:*
      UDP    0.0.0.0:3544           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:3702           *:*
      UDP    0.0.0.0:4500           *:*
      UDP    0.0.0.0:5004           *:*
      UDP    0.0.0.0:5005           *:*
      UDP    0.0.0.0:5355           *:*
      UDP    0.0.0.0:49985          *:*
      UDP    0.0.0.0:54579          *:*
      UDP    0.0.0.0:56756          *:*
      UDP    0.0.0.0:56757          *:*
      UDP    0.0.0.0:62145          *:*
      UDP    0.0.0.0:62201          *:*
      UDP    127.0.0.1:1900         *:*
      UDP    127.0.0.1:63066        *:*
      UDP    127.0.0.1:63942        *:*
      UDP    127.0.0.1:63943        *:*
      UDP    192.168.1.2:137        *:*
      UDP    192.168.1.2:138        *:*
      UDP    192.168.1.2:427        *:*
      UDP    192.168.1.2:1900       *:*
      UDP    192.168.1.2:50223      *:*
      UDP    192.168.1.2:63065      *:*
      UDP    [::]:500               *:*
      UDP    [::]:3540              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:3702              *:*
      UDP    [::]:4500              *:*
      UDP    [::]:5004              *:*
      UDP    [::]:5005              *:*
      UDP    [::]:5355              *:*
      UDP    [::]:49986             *:*
      UDP    [::]:54580             *:*
      UDP    [::]:62146             *:*
      UDP    [::]:62202             *:*
      UDP    [::1]:1900             *:*
      UDP    [::1]:63064            *:*
      UDP    [fe80::4594:7cd3:b8d5:104e%36]:546  *:*
      UDP    [fe80::4594:7cd3:b8d5:104e%36]:1900  *:*
      UDP    [fe80::4594:7cd3:b8d5:104e%36]:63063  *:*

    Here is the output of the ping of the server that doesn't work for scheduled direct. It does reach the server. Therefore there must be something either running on the system that causes the conflict or possibly something in the install of my media portal. I am not sure what sort of information media portal puts in the registry that may be causing conflict. I have also gone through numerous reboots and follow the principle of when in doubt reboot.

    Code:
    C:\Windows\system32>ping webservices.schedulesdirect.tmsdatadirect.com
    
    Pinging docs.tms.tribune.com [54.85.117.227] with 32 bytes of data:
    Reply from 54.85.117.227: bytes=32 time=34ms TTL=52
    Reply from 54.85.117.227: bytes=32 time=31ms TTL=52
    Reply from 54.85.117.227: bytes=32 time=39ms TTL=52
    Reply from 54.85.117.227: bytes=32 time=34ms TTL=52
    
    Ping statistics for 54.85.117.227:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 31ms, Maximum = 39ms, Average = 34ms
     

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    I found the tvservice error log reported the following. I think it ma be my problem.
    Could you please attach the corresponding TV service log [in full]. Without the context, the error doesn't mean much to me.
     

    Paul Jackson

    Portal Member
    May 15, 2015
    31
    18
    58
    Home Country
    United States of America United States of America
    The three log files are attached. Thanks for the quick response.

    I have fully uninstalled media portal in the past and done a full uninstall including uninstalling the data files and also deleted the data from the program data directory. I don't know if something is just lingering in the registry that's causing this or some other process is attempting to use the same port. I don't know if there's a way to run some sort of clean program that cleans every remnants of media portal installed on the system.

    Schedules direct plug-in has never worked on this system. However as I previously mentioned, it works on a much slower fresh installed Windows 7 64-bit. Both systems are on the same network.

    On the system that doesn't work with the schedule with a scheduled direct plug-in, another tool that connects to the scheduled direct web service does successfully pull the data. That ultimately means to me there is no issue with communicating via the network to schedule direct web service inside the configuration of the network. I think there is either something in conflict the schedule direct plug-in or something screwy with my media portal install. Unfortunately I have not yet identified what that is. Any assistance would be appreciated.
     

    Attachments

    • TVService-Error.zip
      6.7 KB

    mm1352000

    Retired Team Member
  • Premium Supporter
  • September 1, 2008
    21,577
    8,224
    Home Country
    New Zealand New Zealand
    Paul, do you have any network security software (firewall, anti-spyware/malware/virus etc.) installed on the PC that isn't working? If so, have you tried temporarily disabling it all, then stopping and restarting the TV service?
     

    Paul Jackson

    Portal Member
    May 15, 2015
    31
    18
    58
    Home Country
    United States of America United States of America
    I disabled both the firewall, Windows firewall, and the antivirus, Microsoft security essentials. Unfortunately pretty much got the same results in it not working. It threw an exception when it was attempting to connect to the web service. There was nothing in the error log this time. Looking at the history there was only one time there was something in the error log so that particular error may not be of significance.

    The log files are attached.
     

    Attachments

    • TVService.zip
      6.2 KB

    Users who are viewing this thread

    Top Bottom