February 17, 2011 at 9:54 am
Hello,
I have a problem that is driving me nuts.
I installed MSSQL 2008 EE 64BIT on a Win2008 Server, and for the service account I used my domain ID.
Today I finally got a service account that is the one who is suppose to run the services, however when I change the service account, I can start SQL Engine but not the SQL Agent.
This is what I did:
0- Add the new service account as a login to SQL and add it to the SYSADMIN role.
1- Go to Sql Server Configuration Manager
2- Stop SQL Browser, SQL Server Agent, SQL Server RS, and SQL Server
3- Change the logon as info on SQL Server, started the service
4- Do the same on SQL Agent, and it fails to start. Error says "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details"
5- If I try to start it from services.msc (I know I shouldn't) it starts but then it stops immediately.
6- Nothing noteworthy on Event Viewer log or SQL logs.
7- The does start under my domain credentials.
The privs for the service account are:
Log on as a service (SeServiceLogonRight)1
Act as part of Operating System
Log on as a batch job
Lock Pages in Memory
Back up files and directories
Perform Maintenance Volume Task
Am I missing something?
Where would I go to see what the error is?
I've done this on three other servers and facing the same problem.
Thank you for your help
February 17, 2011 at 10:38 am
Is there anything in the agent error log or windows system log? You may want to even check the SQL Server error log
February 17, 2011 at 12:39 pm
That's what so weird and challenging about this issue.
the Last thing that the system log records is that the SQL Agent entered stopped state.
The Application log shows that it stopped successfully, and then the SQL Agent starts. however no errors.
The SQL Errorlog doesn't list anything. This is not production, so it is pretty easy to read.
The SQL Agent log is not logging anything because... well the SQL agent is not running.
February 17, 2011 at 12:41 pm
And nothing in the windows system or application log?
February 17, 2011 at 12:57 pm
no Henry, nothing on Apps logs or Systems log or event viewer
February 18, 2011 at 2:13 am
Do you get any errors if you run SQLAGENT.exe from the command prompt? This exe is usually located at C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
February 18, 2011 at 3:33 pm
Adiga,
Thank you for your suggestion, but I resolved the problem before reading your post, so I didn't try it.
I resolved the issue by adding the Service Account to the Administrators Group (while preventing from logging in interactively).
Later on the day I was on a call with MS Support about an unrelated issue, and I asked about this, and I was told that:
"The account running the SQL Server Agent needs to be able to reads and write to the windows folder where SQL is installed and a registry key hive"
(I'm posting this while MS is researching some stuff, so I don't have the magic registry key setting yet).
Miguel
March 22, 2011 at 9:57 am
For those finding this thread on google, I'm going to post the follow up.
Microsoft was wrong, it wasn't a permission to the folders or registry... it was something else.
The account running the SQL Agent Service needs to be able to query the status of the Windows Event Log.
how do we do that?
You can do that by modifying the Group Policies, using this article:
How To Configure Group Policies to Set Security for System Services
http://support.microsoft.com/kb/256345
( it says Windows 2000, but it's the same for 2008)
or you can install SubInAcl.exe from Microsoft and run the following command:
Subinacl /service eventlog /grant=DOMAIN\svc_acct_name=S
More info on SubInAcl here:
http://support.microsoft.com/kb/288129
PS: If you found the thread in google, and aren't a memeber of SQLServerCentral, you should join. This site ROCKS!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply