March 15, 2011 at 6:27 am
Hello,
I hope somebody can help me, I cannot start the SQL Agent (SQL 2005 Ent SP3), I try to change the account in SQL Config Manager but it times out, in the event log I get the following message:
Event Type:Error
Event Source:SQLAgent$InstanceName
Event Category:Service Control
Event ID:103
Date:15/03/2011
Time:11:59:22
User:N/A
Computer:ComputerName
Description:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
The account also runs the SQL Service, and is part of the local admins group. The account is also a part of the sysadmin role. In SSMS the Agent XPs show as disabled, and if I try to run:
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
RECONFIGURE
GO
I get the following error message:
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
Msg 15123, Level 16, State 1, Procedure sp_configure, Line 51
The configuration option 'Agent XPs' does not exist, or it may be an advanced option.
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process
The account does have 'lock pages in memory' privilage, should something else also have this privilage for this to work?
I hope I have supplied enough information, but will provide more if needed. What am I missing? Do I need to repair the agent install?
Any help is most appreciated.
Regards,
D.
March 15, 2011 at 7:18 am
Sounds like a simple security setting. Go to the SQl Server Configuration Manager and ensure that the SQL Agent service is running with an appropriate login. I'd suggest using an Active Directory login that has appropriate access to the server and file systems. another option is to run it under the same login as the SQL Server service is running under.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 15, 2011 at 8:03 am
Hey, thanks for getting back. I just worked out what was wrong, I added the SQL service account to the 'lock pages in memory' priv and it all worked out.
Thanks again,
Paul.
March 7, 2012 at 8:51 am
I'm having this same problem. I'm not using AWE, but tried giving the service account the "lock pages is memory" rights just to rule it out as a cause.
It's for sure set to run as a domain account that has both sysadmin rights in SQL server, and local admin rights on the server itself. It's also the same account that is used for running SQL server itself (which starts and runs fine).
I've run this (below), but can't think of anything else to try. Any suggestions?
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
RECONFIGURE
GO
The Redneck DBA
June 26, 2013 at 1:08 am
After configuring SQL server service account with 'lock pages in memory' permission you have to restart SQL server service.
Than try to restart the SQL agent service it should come up
June 26, 2013 at 1:30 am
Jason
Did you use SQL Server Configuration Manager to set the service account? Please will you post the content of SQLAGENT.OUT.
John
Edit - just realised that this thread is over a year old. Hope Jason has got it sorted out by now!
June 26, 2013 at 3:22 am
HA! I've done that so many times!!
D.
November 28, 2015 at 3:50 pm
Hi,
I had the same problem, but a different scenario:
I converted a physical machine to VM, and the number of the CPU wasn't the same:
16 on physical and 8 on the new VM.
I had the same error in the event log, but different source of problem..
and guess what works for me?
The affinity of the CPU in the SQL properties - go to processors, and check mark the automatic CPU and automatic affinity.
than the agent started..
hope it helped someone..
M.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply