| Author |
Topic |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
 Posted - 2006-05-05 : 04:38:35
|
| interesting, i came upon this situation (lots of test servers to play around with) that the sqlserveragent is dependent on the builtin\administrator being present if localsystemaccount is usedif the said account is present, you can run sqlserveragent using localsystemaccount otherwise noalso, you can run mssqlserver services using the localsystemaccount without the builtin\administrator and if you want to run the sqlserveragent, you will need to specify either a local user (just plain local user) or domain accountthe service accounts do not even need to have local administrative rightsany thoughts?--------------------keeping it simple... |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2006-05-05 : 07:58:21
|
please post sample data and expected results  would this be of any help to you?http://support.microsoft.com/kb/283811/en-usGo with the flow & have fun! Else fight the flow  Blog thingie: [URL="http://weblogs.sqlteam.com/mladenp"] |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-05 : 09:18:23
|
you sound like... , it's not really a problem more of a discussionbut i'll try the registry and windows user rights, see if it makes any difference, then post my findingsthanks for the link--------------------keeping it simple... |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-05-05 : 09:24:40
|
| You could probably get around it on a mixed instance by changing sql agent to connect as SA ;)-------Moo. :) |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-05 : 09:27:01
|
| yeah i tried that too, but it doesn't accept the sa to run the service account (you mean from EM right?)--------------------keeping it simple... |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-05-05 : 09:29:31
|
| I was meaning from within EM on the connection properties for sql server agent. (Whilst leavign the service account as local system.)-------Moo. :) |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-05 : 10:49:32
|
| yep, tried that too, mind you this is without the builtin\administratorwere you able to run the sqlserveragent using the settings you described?--------------------keeping it simple... |
|
|
|
mr_mist
Grunnio
1870 Posts |
Posted - 2006-05-08 : 04:21:24
|
quote:
Originally posted by jenwere you able to run the sqlserveragent using the settings you described?
Yep. I took out builtin\administrators and left sql agent as "local system" account, but changed its connection to sa. restarted sql server just to make sure. Agent started no problem. The key does seem to be the "connection" tab. If I switch that back to windows authentication instead of connecting as SA, then I see the login failed for user NT AUTHORITY\SYSTEM. For some reason you have to specifically add in this user for agent to connect, but not for sql server itself to start. odd.-------Moo. :) |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-08 : 05:28:13
|
| i used SA and mine says, logon failure: unknown username or bad passwordhmm... i'll test this tomorrow, no time today--------------------keeping it simple... |
|
|
|
|
interesting service behavior