SQL Server Agent

Created a job in Sql Server Agent.  I can not execute the job with myself as owner even though I am sysadmin on the database.   If I change the owner to and owner that has other jobs in the database  job executes perfectly.  What permission setting am I missing?
LVL 1
countyprobSystem AnalystAsked:
Who is Participating?
 
didnthaveanameConnect With a Mentor Commented:
That's an odd error.  It would seem to indicate that the account the SQL Server Agent service is running under doesn't have permissions to query AD for permissions.  Which begs the question as to how those jobs are running at all, regardless of the owner/user that it executes under.  Unless those other users are SQL Server authenticated accounts or local accounts to that server.  Check and see what account the SQL Server Agent service is running under.
0
 
didnthaveanameCommented:
What does the job do when you execute it as yourself?  Does it error out?  And if so, could you provide the error?
0
 
Guru JiConnect With a Mentor Commented:
It isn't a server role so sysadmin won't do anything

It is one of the "SQL Server Agent Fixed Database Roles" in msdb

See "How to: Configure a User to Create and Manage SQL Server Agent Jobs (SQL Server Management Studio)" on MSDN
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

 
countyprobSystem AnalystAuthor Commented:
When I execute the job as myself I get the following error.  

Message
The job failed.  Unable to determine if the owner (K*******\user) of job SRA Sheriff report daily has server access (reason: Could not obtain information about Windows NT group/user 'KERNPROBATION\joemunch', error code 0x5. [SQLSTATE 42000] (Error 15404)).
0
 
countyprobSystem AnalystAuthor Commented:
Had to use a high privilege account
0
 
countyprobSystem AnalystAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for countyprob's comment #a39223334

for the following reason:

after tinkering around, the past DBA had a higher privileged account and we started using that.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.