TV-Service starts before SQL-Server (3 Viewers)

infinite.loop

Retired Team Member
  • Premium Supporter
  • December 26, 2004
    16,163
    4,133
    127.0.0.1
    Home Country
    Austria Austria
    -Uninstall the TV-Server
    -restart the PC
    -install latest version of TV-Server
    -check that SQL server is started
    -launch the TV-Server
    -enter IP-ADRESS of the SQL server
    -enter correct password for the SA user
    -click TEST
     

    Patric

    Portal Pro
    August 27, 2004
    84
    2
    Home Country
    Germany Germany
    Hi Chris!

    -Uninstall the TV-Server
    -restart the PC
    -install latest version of TV-Server
    -check that SQL server is started
    -launch the TV-Server
    -enter IP-ADRESS of the SQL server
    -enter correct password for the SA user
    -click TEST

    Everything works fine doing what you suggest (as it did before).

    But after restarting (so that the SQL- and TV-Service start automatically) the same error as before appears (this time I explicitly chose the IP address instead of the machine name):
    Code:
    02.11.2006 21:25:12 !!!Controller:Unable to connect to database!!!
    02.11.2006 21:25:12 Controller: database connection string:Password=mediaportal;Persist Security Info=True;User ID=sa;Initial Catalog=TvLibrary;Data Source=192.168.100.13\SQLEXPRESS;
    02.11.2006 21:25:12 Sql error:The database backend (provider SQLServer) could not be reached.
    Check the connection string: Password=mediaportal;Persist Security Info=True;User ID=sa;Initial Catalog=TvLibrary;Data Source=192.168.100.13\SQLEXPRESS;

    Patric
     

    Marcusb

    Retired Team Member
  • Premium Supporter
  • February 16, 2005
    1,995
    29
    Melbourne
    Hi Patric,
    I think people are missing your point. It seems everything is set up correctly, as you can connect succesfuly as long as the SQL server starts a few seconds before th TV service and not straight before.
    It seems the TV Service tries to connect while the database is still starting, so is unable to make a connection and then fails (but doesn't stop, so "Auto Restart" will not work).

    Unfortunatlely I can't offer any help, but thought that restating your issue may point people in the right direction.
     

    Patric

    Portal Pro
    August 27, 2004
    84
    2
    Home Country
    Germany Germany
    Hi Marcus,

    at least you got my point :)

    Already thought I couldn't make myself clear...

    Patric
     

    infinite.loop

    Retired Team Member
  • Premium Supporter
  • December 26, 2004
    16,163
    4,133
    127.0.0.1
    Home Country
    Austria Austria
    It seems the TV Service tries to connect while the database is still starting, so is unable to make a connection and then fails (but doesn't stop, so "Auto Restart" will not work).
    Frodo knows about this issue and is working on a solution. :)
     

    Patric

    Portal Pro
    August 27, 2004
    84
    2
    Home Country
    Germany Germany
    Chris,

    great info and thx for letting me know.
    Best wishes to Erwin!

    Patric

    BTW: Was machst du um 6 Uhr schon wieder am Rechner? :)
     

    Patric

    Portal Pro
    August 27, 2004
    84
    2
    Home Country
    Germany Germany
    Just to popup this thread again.

    Because my harddisc is beginning to fail I decided to plugin a new one and do a complete reinstall of the system.
    I just installed WXP with all patches and the needed hardware drivers. The only software I threw in was MP (latest SVN), SQL Server Express and TV-Service.

    What should I say. The problem persists. The TV-Service still logs the same error message about not being able to connect to the SQL Server.

    But I also found two identical entries in the system log (both the same time):
    Code:
    Ereignistyp:	Fehler
    Ereignisquelle:	MSSQL$SQLEXPRESS
    Ereigniskategorie:	(4)
    Ereigniskennung:	17187
    Datum:		09.11.2006
    Zeit:		08:21:57
    Benutzer:		Nicht zutreffend
    Computer:	DIGN
    Beschreibung:
    SQL Server ist nicht zum Annehmen neuer Clientverbindungen bereit. Die Verbindung wurde geschlossen. Warten Sie vor dem Wiederholen des Vorgangs einige Minuten. Falls Sie über Zugriff auf das Fehlerprotokoll verfügen, suchen Sie vor einem erneuten Verbindungsversuch die Informationsmeldung, die besagt, dass SQL Server bereit ist. [CLIENT: <local machine>]
    
    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.

    If a translation is needed I'll provide one.
    Hope there's a fix in the near future for this...

    Patric
     

    varesino

    Portal Member
    January 18, 2005
    38
    0
    Europe
    Is it possible that you have a delay getting the IP Address on your network card?

    Remember that the connection between SQL Server DB and TV server is done via TCP-IP, if you are using a DHCP server and your network card delay in initialization no communication can be done.

    Try with a fixed ip address.

    Regards
    Varesino
     

    patrick

    Portal Pro
    April 20, 2005
    608
    45
    Southeast
    Home Country
    United States of America United States of America
    Hi,

    I guess a work-around would be to set the tv server service to manual
    and run a batch file @ in startup with a sleep timer of say 2 minutes and
    then launch the tvserver service from the the batch file command line.


    HTH,
    patrick
     

    Patric

    Portal Pro
    August 27, 2004
    84
    2
    Home Country
    Germany Germany
    varesino
    Just tried your suggestion even though I didn't think it had to do with because the SQL Server seems to respond but denies the connection (see post above).
    But setting a fixed IP didn't solve the problem either.

    patrick
    Just thought about something like starting the service via FireDaemon or something similar where you can set a delay for starting. We'll see...
     

    Users who are viewing this thread

    Top Bottom