United States of America
Can anyone tell me how to configure MP to have TVservice log into the database after it has started running with MpTVdb? I have added dependencies to TVservice, in the windows registry, for it to start after the For The Record core services only to have that dependency disappear after the next reboot. I currently have to manually re-start TVservice in order to watch live TV after a reboot. I have added extra timeouts to the gentle config file but didn't work. I am using MSSQL instead of MY SQL because corrupt databases with MY SQL. Log files are attached.
Configuring TVservice to wait for the database to start before login (2 Viewers)
- Thread starter dpmcrae
- Start date
I've been using Windows 7's "Automatic (Delayed)" startup type for TV-Server. It's simple-minded and not the slickest solution, but it has avoided the problem you describe: TV-Server starting up before the database is running.
Sasha
Sasha
Very true. Did anything happen during the reboot that could have caused a fallback to an alternate control set and subsequent loss of the dependency?
I added a dependency like this:
Note that SQLBrowser and Netman were TVService's pre-existing dependencies. Unfortunately this didn't produced the desired result, and instead led to the dreaded "The database backend (provider SQLServer) could not be reached" error. While the system event log indicates that SQL Server was indeed launched before TVServer, I suspect that what's going on here is a race condition in the sense that SQL Server reports that it is "started" to the Service Control Manager (the only prerequisite introduced by the dependency) before it is ready to accept client requests for the MPTvDb database.
Back to the drawing board--maybe it's time for a script. Sigh.
Sasha
I added a dependency like this:
Code:
sc config TvService depend= SQLBrowser/Netman/MSSQLSERVERNote that SQLBrowser and Netman were TVService's pre-existing dependencies. Unfortunately this didn't produced the desired result, and instead led to the dreaded "The database backend (provider SQLServer) could not be reached" error. While the system event log indicates that SQL Server was indeed launched before TVServer, I suspect that what's going on here is a race condition in the sense that SQL Server reports that it is "started" to the Service Control Manager (the only prerequisite introduced by the dependency) before it is ready to accept client requests for the MPTvDb database.
Back to the drawing board--maybe it's time for a script. Sigh.
Sasha
- Thread starter
- #5
I added the dependency through command line and direct insertion in the registry so that it started after For The Record since 4TR is the last thing to come on line and it sees to work after that until after the second reboot. I can't find a cause for it to revert back to the original key in the registry. Even if you change the timeouts in the gentle config file it still doesn't work as it should. I have had other issues with MP but just realized that TVservice starting too soon was causing the problems.
Does anyone know if the timmoore firewire drivers will work with Win 7 32 Bit? If it does then it would an incentive to change the OS but only if no one else is having an issue with multiple capture and TV cards with firewire channel change.
Does anyone know if the timmoore firewire drivers will work with Win 7 32 Bit? If it does then it would an incentive to change the OS but only if no one else is having an issue with multiple capture and TV cards with firewire channel change.
That surely must be slow network startup related, are you singleseat or multiseat, if the first, then I would seriously consider the MSLoopback adapter, or if second, try setting up fixed ip address with dhcp disabled.
- Thread starter
- #8
So the loopback didn't work for me, TVservice still started before the database and I kept getting log in failure on SA. So I decided to give Win 7 32bit a try to see if can control the TVservice start up better with delayed start up.
