September 10, 2005 at 2:37 pm
If I reboot the server with the sql engine startup using "local account", then sql server and the sql agent start just fine. But if I use a Windows domain account (that is a member of local Admins group on that box) to start sql server, then reboot the server, the sql engine refuses to start. If I then go to Sql service manager and start the sql engine manually, it starts withtout incident. It's just that the user account don't seem to have the permissions(?) to autostart the sql engine. And the "Autostart" option in the sql server manager is checked for both the sql engine and the sql agent.
Any ideas much appreciated!
TIA,
Bill
September 11, 2005 at 10:17 am
Bill,
1. What are error messages in all 3 Event Logs; Application, Security and System for the startup process?
2. Is Network / Domain Controller available to verify Domain User credentials on startup (startup sequence ???) When you log in and start the service manually it is obvious that the network already available by then.
3. Did you login as this domain users to the server at least once so the profile will be created fand credentials cached or this Domain User on this server? I did see this cases when you have to login to the machine one time before you can fully use this account in the processes when no one logged in.
Regards,Yelena Varsha
September 12, 2005 at 1:27 am
Couple of things here. When you say local account do you mean a local machine account or the 'local system account' which is one of the options presented during the install of sql server? The 'local system acount' is a member of local admin group and this could be why its working when you use this one.
Also how did you change the account that sql server and the agent will use to start? You must do this via Enterprise Manager or several registry and file level permissions are not set correctly.
Derek
September 12, 2005 at 11:26 pm
Rookie,
Good questions. I meant "local system account" but I didn't relaize that that account belongs to the local admins group.
I went into Control Panel, Services, and changed the startup account for MSSQL to a domain account. I did not attempt to change the sql Server agent account -- I left it at its default setting. I assumed I could change the two accounts (MSSQQL and Agent) independenlty of each other. Is this incorrect?
TIA,
Bill
September 13, 2005 at 12:41 am
Local system account is a local admin.
You should avoid using the method you did for altering the service account. Go into Enterprise manager and change the service account here instead, this sets a number of privileges and sets registry rights correctly.
Yes you can use different accounts for the agent and for sql server services, but I wouldn't. I have had issues and so have many others when doing this. in some cases it appears to be the level of privileges that the sql server service account has which can cause errors. One error is where you are prevented from starting jobs, viewing jobs etc with an error that indicates the agent serverice is not running (when it clearly is). Also the account which starts the agent service needs certain privileges depending on what you want the agent service to do. If you want sql agent mail or jobs which are scheduled go beyond the local server (run cmdexec or access other servers in a domain then the agent account must be a domain account,i.e not local machine and not local system.
Derek
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply