Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Kristen
Test
22859 Posts |
Posted - 2005-09-06 : 11:41:10
|
| A client of mine said their trusted connections (i.e. from client applications) stopped working when they rebooted their server (SBS) today.We tried a variety of stuff, and in the end changing SQL service to logon as local system fixed the problem. We reckon it used to be set up to use "local system", but aren't sure. I cannot for the life of me work out why that would have made a difference.The server was recently upgraded with SQL SP4 (but has been rebooted since then)We also have a vague recollection that seom SBS release notes said to install SQL as local system.Any ideas?ThanksKristen |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-06 : 13:44:49
|
| I'm confused. So was the problem that the service (MSSQLSERVER) wouldn't start or that the clients couldn't connect to SQL Server?Tara |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-09-06 : 14:06:12
|
MSSQLSERVER and SQL Agent were running OK. SQL Agent was configured to use a Domain AccountClients (using trusted connection) could not connect.Connecting from a Client using a SQL Login (e.g. sa) was OKChanging SQL Service Agent to logon as local system, rather than a domain account, fixed the problem [but that bit I find scary!]Kristen |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-06 : 14:49:23
|
| I have a feeling that changing it to the Local System Account did not in fact fix your problem. Probably restarting the MSSQLSERVER service is what fixed it.Tara |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-09-07 : 02:00:49
|
| just my 2 cents...check if both of the services run on a domain accountnow that the server is running on a domain, the netadmin must check if users are not restricted to connect to this machine(firewall issues, authentication policies, probably an Active Directory policy of some sort)HTH--------------------keeping it simple... |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-09-07 : 02:29:32
|
| Sorry, typo above (which I've now fixed). It was only the SQL Agent that had been set to a Domain Account, and was changed back to Local System.Kristen |
 |
|
|
|
|
|