SQL Issuses (1 Viewer)

burr

MP Donator
  • Premium Supporter
  • May 13, 2006
    175
    47
    Home Country
    Sweden Sweden
    Look inside MediaPortal.xml and search for the parameter "hostname" and look for the value?

    /Mathias
    OK - a trawl through MediaPortal.xml in \Documents and Settings\All Users\Application Data\Team MediaPortal\MediaPortal comes up with:

    <section name="tvservice">
    <entry name="hostname">192.168.2.210</entry>
    <entry name="preferac3">no</entry>
    <entry name="preferAudioTypeOverLang">yes</entry>
    <entry name="dvbbitmapsubtitles">no</entry>
    <entry name="dvbttxtsubtitles">no</entry>
    <entry name="audiodualmono">no</entry>
    <entry name="preferredaudiolanguages">
    </entry>
    <entry name="preferredsublanguages">
    </entry>
    </section>

    This is the same as the working clients....any other idea's? Like I said I am sure the problem is at the DB connectivity level, not MP itself.

    Regards
    //copperwave

    Please look inside Program Files\Team MediaPortal\MediaPortal also. Here is a little program that you can try to connect to the database i used User ID "sa" and Password "MediaPortal". Please send me the Gentle.config in Program Files\Team MediaPortal\MediaPortal if it's possible.
     

    copperwave

    Portal Member
    June 7, 2007
    8
    0
    Home Country
    United Kingdom United Kingdom
    Hi burr many thanks for this. Not sure what the valid test cases should be but here are my results.
    Note that I too had installed the TVServer DB with sa/MediaPortal.

    Test #1: Run from the ..\Media Portal dir on the TVServer itself:

    Write the Client to connect to...
    192.16.2.210
    An error has occurred while establishing a connection to the server. When conne
    cting to SQL Server 2005, this failure may be caused by the fact that under the
    default settings SQL Server does not allow remote connections. (provider: SQL Ne
    twork Interfaces, error: 26 - Error Locating Server/Instance Specified)
    The connection didn't succeed

    Test #2: Again from the TVServer itself but this time using the PC's hostname: htpc

    Write the Client to connect to...
    htpc
    Cannot open database "TvLibrary" requested by the login. The login failed.
    Login failed for user 'sa'.
    The connection didn't succeed

    Press a key to end the program.....

    Test # 3 - From the "client" PC that doesn't work - with htpc as the hostname:

    Write the Client to connect to...
    htpc
    An error has occurred while establishing a connection to the server. When conne
    cting to SQL Server 2005, this failure may be caused by the fact that under the
    default settings SQL Server does not allow remote connections. (provider: SQL Ne
    twork Interfaces, error: 26 - Error Locating Server/Instance Specified)
    The connection didn't succeed

    Test #4: Again from the failing PC but this time with the IP address:

    Write the Client to connect to...
    192.168.2.210
    Cannot open database "TvLibrary" requested by the login. The login failed.
    Login failed for user 'sa'.
    The connection didn't succeed

    I would have thought at the very least running this in the TVServer would have run OK...like I say it is very weird :(


    Thanks
    //copperwave
     

    burr

    MP Donator
  • Premium Supporter
  • May 13, 2006
    175
    47
    Home Country
    Sweden Sweden
    Hello

    I think the problem is you have to change the following TV-Server/Configuration/SQL-Server - MediaPortal Wiki Documentation
    If think if you look in the Mediaportal.xml inside Program Files\Team MediaPortal\MediaPortal and hostname then you will find HTPC instead of an Ip-adress.
    Test #4 shoud have worked but i saw in the log that you have a different name on your database "MpTvDbRC1" i have TVLibrary.
    I have changed the to "MpTvDbRC1" in the attached file if i'm wrong with the things mentioned above please test the new program.

    /Mathias
     

    copperwave

    Portal Member
    June 7, 2007
    8
    0
    Home Country
    United Kingdom United Kingdom
    Hi Burr

    so - in the meantime I had also upgraded to RC2 to see if that made any difference. It looks as if the DB has changed its name again. This time to MyTvDbRc2. However, to check that the SQL comms were OK, I renamed the DB back to both TvLibrary (your original sqlconnect) and to MyTvDbRc1 (the latest version). The good thing is that if I use the IP address then I get a connection - on both the working and non-working clients. If I use a host name I don't.

    To try back tracking I have also uninstalled MP from the server and gone back to RC1 to see if standardising on "TVLibrary" made things any more productive. Strangely, I get my host pc's name inserted into Mediaportal.xml. If I manually edit the xml file and change <hostname> to the servers IP address, MP as a LAN client eventually loads - but selecting TV just causes the GUI to go non-responsive.

    WRT to your pointer in the wiki - I have done / made the appropriate changes to SQL to allow remote connections.

    Thanks
    //copperwave
     

    CieNeSDi

    MP Donator
  • Premium Supporter
  • December 18, 2007
    53
    16
    Oetwil a.d. Limmat
    Home Country
    Switzerland Switzerland
    hi copperwave,

    The good thing is that if I use the IP address then I get a connection - on both the working and non-working clients. If I use a host name I don't.

    for me this sounds like you have a DNS/hostname resolution problem. try the following:

    open a command prompt and type in:

    ping "hostname"

    if you don't get an answer thats your problem.

    make the following:

    go to C:\Windows\system32\drivers\etc -> open the file hosts -> type in: "IP Adress of the TVServer" (tab) "hostname of the TVServer"

    example:

    192.168.1.1 <there should be a tab here> TVServer

    this should be the last line in this file.

    hope this helps a little bit :)
     

    copperwave

    Portal Member
    June 7, 2007
    8
    0
    Home Country
    United Kingdom United Kingdom
    Thanks Guys - this is fixed....though not quite the way I imagined. The DNS pointer was the clue. Unknown to me, the TVServer and the PC client that wouldn't work were set to use the "Primary DNS suffix" in the Network Identification / More dialogue. Not sure why I had set this but the effect was that "htpc" was resolving to my external static IP address. I've turned this off (on both the server and the client and hey presto I'm back in business.

    Great stuff and thanks for the suggestions :)

    Later
    //copperwave
     

    Users who are viewing this thread

    Top Bottom