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

Error 229: Execute permition denied on object............. Expand / Collapse
Author
Message
Posted Tuesday, March 4, 2008 5:34 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 9:33 AM
Points: 186, Visits: 815
Hello again,

People are reporting the following error:
Error 229: Execute permission denied on object 'xp_sqlagent_enum_jobs', database 'master', owner 'dbo'.
Can you tell me what should i check?

This was working until yesterday but now i don't know if anyone of System Administration Team change any privilege of one user.
Teams work separately and this sheet always happens.

Thanks and regards,
JMSM ;)
Post #463688
Posted Tuesday, March 4, 2008 1:57 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, June 16, 2014 6:53 AM
Points: 1,145, Visits: 1,932
What is it that the users are attempting to do?

By default (someone correct me If I'm wrong, as there is no documentation on this xproc), only sysadmins, msdb dbo's (?), and members of the defined msdb SQLAgentRoles (SQLAgentOperatorRole/SQLAgentUserRole/SQLAgentReaderRole) have the ability to use that procedure.

xp_sqlagent_enum_jobs is basically a nice, quick little way to view running jobs.


---
SQLSlayer
Making SQL do what we want it to do.

Post #464081
Posted Wednesday, March 5, 2008 3:32 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 9:33 AM
Points: 186, Visits: 815
Thanks everybody, the solution was as follows:

Regards,
JMSM ;)

use master
go
grant select on master.dbo.sysperfinfo to {username}
go
grant execute on master.dbo.xp_sqlagent_notify to {username}
go
grant execute on master.dbo.xp_sqlagent_enum_jobs to {username}
go
grant execute on master.dbo.xp_sqlagent_param to {username}
go
grant execute on master.dbo.xp_sqlagent_is_starting to {username}
go
grant execute on master.dbo.xp_instance_regenumvalues to {username}
go
use msdb
go
grant execute on msdb.dbo.sp_help_alert to {username}
go
grant execute on msdb.dbo.sp_help_notification to {username}
go
grant select on msdb.dbo.sysalerts to {username}
go
grant select on msdb.dbo.sysoperators to {username}
go
grant select on msdb.dbo.sysnotifications to {username}
go

Post #464310
Posted Friday, March 7, 2008 8:25 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, August 5, 2013 9:59 AM
Points: 307, Visits: 385
I'm having the same permission problems. I use to put my agent operators in the sqlAgentOperatorRole in the msdb database. Thisa would allow them to go under the jobs and view and execute all jobs.

Does anyone know if a SP2 roll up changed this? I did restore msdb from a backup but I do not think it would have changed the XP_ permissions.
Post #465906
Posted Thursday, April 10, 2008 5:03 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 10:07 AM
Points: 1,931, Visits: 3,159
"I did restore msdb from a backup" - this could be your problem.
Check something has permissions to run xp_sql_agent_is_starting, and that the msdb & master databases have the same owner.
Post #482913
Posted Wednesday, October 20, 2010 10:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, March 26, 2012 2:24 PM
Points: 3, Visits: 148
I searched the error for a while and saw a lot of things about certificates differing between msdb and master. But I checked the certificates and they were identical.

I compared my server to others, and noticed that the ##MS_AgentSigningCertificate## user was missing from the master database. Running the following query worked for me:

USE MASTER
CREATE USER [##MS_AgentSigningCertificate##] FOR LOGIN [##MS_AgentSigningCertificate##]
GO

GRANT EXECUTE TO [##MS_AgentSigningCertificate##]
go
Post #1007863
Posted Wednesday, March 14, 2012 9:16 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 8, 2014 7:01 AM
Points: 5, Visits: 189
I also encountered this issue and found the steps at http://support.microsoft.com/kb/2000274 solved my issues. Wanted to add that in case it helps anyone else out.
Post #1266830
Posted Wednesday, October 31, 2012 7:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 1:20 AM
Points: 1, Visits: 10
hi dear,

this is the error list what is get after applying this query.
Post #1379322
Posted Wednesday, December 18, 2013 12:01 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, August 18, 2014 8:51 AM
Points: 29, Visits: 596
I restored msdb from other server for hardware migration. The SQLAgent Service account was not in Systemadmin server role and caused the SQL Server Agent service couldn't start due to lack of permission to access master database. I added the SQLServerAgentService account to SysAdmin server role.

SQLServer Agent Service was able to start right away. Just thought about to share.
Post #1524288
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse