Originally Posted by Robert Simandl
I sure wish somebody with more tech knowledge than myself would write a guide like this for the TV Server. The documentation and videos for setting up SQL Server and TV Server appear to be a version or two out of date. Screens and choices appear in the process that aren't mentioned in the documentation or videos. I've tried getting through them with trial and error, but since nothing works I guess it's been all error so far.
Specifically, when I start up TV Server Configuration, the SQL Server User ID and Password I had set up earlier don't work... "Connection failed! Login failed for user 'sa'"... and I can't go anywhere from there............
I am not at all familiar with what it is you are setting up in terms of this TV server as I myself have not touched it, but I do work with SQL a lot for my rl job. From what I have seen so far, it sounds as though you setup the sa account in your TV Server setup. My guess is the service is trying to use this configured account to authenticate with SQL. So, the question back to you is, how is your sa account configured on your SQL server? When you installed SQL, it at some point prompts you to enter a password for the sa account. If you didn't do this, then the pw is either empty or defaulted to 'sa' (most likely defaulted to sa)
You can test this by opening SQL Management Studio and try to login using SQL Authentication and the sa account credentials you configured in your TV Server. If it fails then you need to either reconfigure your TV server with the blank p/w (or sa), or, login with a different known SQL account and change the sa password under the Security > Logins section using the pw you configured in the TV Server. (Try windows authentication if you don't know of any other SQL logins)
In all actuality, using the sa account to run a service/application is not a good idea. I would suggest you setup a separate account with only the necessary read/write permissions on the database that this service requires and use that. sa is a whole-system super super admin account that leaves your system vulnerable if there are any points in the application that are susceptible to intrusion. People who write applications that use sa are, in my opinion, just too lazy to take the time to set things up properly since sa pretty much lets you do anything out of the box. Sure, it makes it easy to configure, but at what cost? Some might say its not that big of a deal since the data being used is non-critical, but SQL is more powerful than just giving the ability to read and write data, and in the wrong hands, can wreak havoc on a much larger scale than most people realize.
But I digress...give the a-fore mentioned hints above a try and let us know how it goes.