Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Cannot Start SQL Server Agent Expand / Collapse
Author
Message
Posted Tuesday, March 15, 2011 6:27 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 3:39 PM
Points: 393, Visits: 1,268
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.
Post #1078273
Posted Tuesday, March 15, 2011 7:18 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 4:56 AM
Points: 15,646, Visits: 28,028
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
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1078321
Posted Tuesday, March 15, 2011 8:03 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 3:39 PM
Points: 393, Visits: 1,268
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.
Post #1078354
Posted Wednesday, March 7, 2012 8:51 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 2:30 PM
Points: 1,507, Visits: 2,150
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


Jason Shadonix
MCTS, SQL 2005
Post #1263066
Posted Wednesday, June 26, 2013 1:08 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Saturday, June 7, 2014 11:12 AM
Points: 19, Visits: 167
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
Post #1467477
Posted Wednesday, June 26, 2013 1:30 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 8:36 AM
Points: 5,308, Visits: 9,700
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!
Post #1467487
Posted Wednesday, June 26, 2013 3:22 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 3:39 PM
Points: 393, Visits: 1,268
HA! I've done that so many times!!

D.
Post #1467528
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse