SQLAGENT CAN't START

Question

SQLAGENT CAN't START

this log:

 

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).

 

Answer 1

Which account is the service running with ?

HTH, Jens K. Suessmeyer.

---
http://www.sqlserver2005.de
---

Answer 2

it's run administrator account.

I tested in local and domain administrator .

I also tested in local system

D. schmitt

Answer 3

I am receiving the same error.  For some odd reason my sqlserveragent will not start.  I am using a domain accoutn that does have access to sysadmin on sql server 2005.  were you able to get this running.

Answer 4

check sql server agent error log...post the error..

 

Madhu

Answer 5

In the event viewer we have the following error:

Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date:  3/1/2007
Time:  10:16:30 AM
User:  N/A
Computer: MyServer
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).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Answer 6

the error is self descriptive... your startup account is not having enough permission. Add this particular startup (preferably Domain user) to sysadmin role

 

Madhu

Answer 7

Yes, but the problems is because the user is in the sysadmin role on the SQL Server, and I tried the user as a local administrator.  but it still doesn't work...

 

Answer 8

I fixed it...

I found that the Agent XPs wasn't enabled...

So I enabled it using this script:

sp_configure 'show advanced options', 1;
GO
 RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
 RECONFIGURE
GO

Answer 9

 

I cant run this script as the sql agent is nor running. I get somme errors

Answer 10

One follow up to this.  If you are using AWE, you need to make sure the service account for the SQL Server service has been granted the "Lock pages in memory" privilege.  I was having the same issue as the original poster, and when I ran the Agent XPs script, I received a message that:

 

"Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process."

 

My service account for the SQL Server Agent had been granted this privilege, but my service account for the SQL Server service had NOT been granted this privilege.

 

I granted the privilege to the SQL Server service account and restarted the SQL Server service.  Then I was able to run the Agent XPs script and get my SQL Server Agent started.

 

One additional note about ANY SQL Server 2005 service: ALWAYS use the SQL Server Configuration Manager to start, stop and configure SQL Server 2005 services.  The Configuration Manager takes care of assigning the correct permissions to the service accounts.

Answer 11

Thanks guys.

I had these errors in my application log:

5845 MSSQL$

Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.

103 SQLAgent$

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).

 

But after I applied 'lock pages in memory' permission to my sqlaccount and gave it ‘sysadmin role’ in SQL, errors are gone and SQLAgent starts and works successfully.

 

Thanks a lot!

 

Answer 12

I'm running into the same problem trying to enable AWE on a SQL Server 2005 64-bit cluster. 

 

How did you apply 'lock pages in memory' permission to the SQLAgent ?   

 

Answer 13

I just answered my own question:

 

To enable the lock pages in memory option

1. On the Start menu, click Run; in the Open box, type gpedit.msc.

   The Group Policy dialog box opens.

2. On the Group Policy console, expand Computer Configuration, and then expand Windows Settings.

3. Expand Security Settings, and then expand Local Policies.

4. Select the User Rights Assignment folder.

   The policies will be displayed in the details pane.

 

Answer 14

I my case resetting the sa password was sufficient.

SQLServerAgent apparently uses the sa account to logon.

 

cheers,

Peter

 

Answer 15

 

I was stumped - and this worked like a charm. Thanks to you Ken and the folks below with the gpedit.msc posting.

 

Answer 16

This just worked for me as well. Note that the SQL Server Agent still would not start until I restarted the SQL Server service.

Answer 17

Thanks sqlmikesql...

Your post did the magic for me. I was stuck on this for 2 days...!!!!

Answer 18

I tried this

 

Run your SQL Server and Agent on local system account.

Then run following command 

sp_configure 'show advanced options', 1;
GO
 RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
 RECONFIGURE
GO

Answer 19

Hi,

we had the same error after a P2V with the VMware Converter.

At the P2V we decided to use only two CPUs and not four as in our physical server.

And that was the big problem.

Solution:
Give your VM the same CPUs as your physical one have.
(We think this error occur, because MSSQL is licenced on CPUs)

Answer 20

Worked for me...

Answer 21

But I dont understand why is the below query dependent on Locking pages in Memory for a sql server service account?


sp_configure 'show advanced options', 1;
GO
 RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
 RECONFIGURE
GO

Answer 22

I'm having this issue this morning all of a sudden.  I've verified the AD user is a sysadmin and a local admin on the server and I'm not using AWE.  

Just for fun though I ran the script below and enabled the "allow lock pages in memory" group policy setting for the login.

Interestingly, the SQL service itself starts and run fine while using that same service account.

sp_configure 'show advanced options', 1;
GO
 RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
 RECONFIGURE
GO

Any other suggestions of things to try?

Answer 23

Hello,

You will need first to allow the service account to Lock Memory Page from gpedit.msc -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment -> {Lock Pages in Memory}.

Then try to restart the agent services services.

BR,

Abdurrahman Gori