SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Problem with agent service accounts?


Problem with agent service accounts?

Author
Message
thepiecesfit
thepiecesfit
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 76
Jacob Wilkins (8/8/2013)
Two questions:

1) Does the SQL Server error log show a login failure for that login when you try to start the Agent?

2) The "Access Denied" error you received looks more like a file system permissions issue. Have you checked file systems permissions?

Cheers!


SQL error log shows nothing.

I have tried setting that local user full rights to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\SQLServerAgent - did nothing

I have tried setting D:\SQLData\data\MSSQL11.MSSQLSERVER\MSSQL\Log full rights to that local user - did nothing


For what its worth I have tried this on a second Server 2012 machine and it behaves the same. Is anyone here actually running this combo successfully ? Windows Server 2012 + SQL 2012 ? Something must have changed but I cant figure out what.
Jacob Wilkins
Jacob Wilkins
SSCertifiable
SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)SSCertifiable (7.6K reputation)

Group: General Forum Members
Points: 7584 Visits: 10177
I have some Windows server 2012 + SQL Server 2012 combinations both in the lab and in production, and they work without issues (well, without this issue :-D).

I actually just created a new local user on the lab machine, left it as a member only of the Users group, stopped the Agent, changed the Agent to use the new user, and started the Agent with no issues.

Just to make sure I'm clear on your situation:

1) You are currently only receiving the generic "Service failed to start in a timely fashion" error?

2) Does this occur no matter what account you specify for the Agent?

In the meantime I'll see if I can recreate your issue, but I've had no success so far.

Cheers!
thepiecesfit
thepiecesfit
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 76
Jacob Wilkins (8/9/2013)
I have some Windows server 2012 + SQL Server 2012 combinations both in the lab and in production, and they work without issues (well, without this issue :-D).

I actually just created a new local user on the lab machine, left it as a member only of the Users group, stopped the Agent, changed the Agent to use the new user, and started the Agent with no issues.

Just to make sure I'm clear on your situation:

1) You are currently only receiving the generic "Service failed to start in a timely fashion" error?

2) Does this occur no matter what account you specify for the Agent?

In the meantime I'll see if I can recreate your issue, but I've had no success so far.

Cheers!


1) Yes that is correct

2) Just created a user called testagent. Same issue . Service failed to start in a timely fashion.


I agree with you and Ive done this on many times on other servers. I don't know why its not working here. Argg.. But this is the first environment i work with thats 2012.
EdVassie
EdVassie
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14202 Visits: 3901
Using a domain user account for SQL Agent works fine in SQL 2012 (and SQL 2005, 2008, 2008R2, 2014), you just have to give it the correct rights.

It needs:
Act as part of the operating system
Adjust memory quotas for a process
Bypass traverse checking
Log on as a batch job
Log on as a service
Replace a process level token

It does not need to be a member of the windows Administrator group unless you enable the 'Automatically start SQL Server / SQL Agent if it fails'.

The Agent account will also need to be a Sysadmin account in SQL Server.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
thepiecesfit
thepiecesfit
Valued Member
Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)Valued Member (56 reputation)

Group: General Forum Members
Points: 56 Visits: 76
EdVassie (8/12/2013)
Using a domain user account for SQL Agent works fine in SQL 2012 (and SQL 2005, 2008, 2008R2, 2014), you just have to give it the correct rights.

It needs:
Act as part of the operating system
Adjust memory quotas for a process
Bypass traverse checking
Log on as a batch job
Log on as a service
Replace a process level token

It does not need to be a member of the windows Administrator group unless you enable the 'Automatically start SQL Server / SQL Agent if it fails'.

The Agent account will also need to be a Sysadmin account in SQL Server.




Thanks but I am not using a domain account. Using a local user.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search