Re: SQLAgent Jobs Not Available after SP4 Applied

• Previous message: Prakash: "Re: Permissions on stored procedures & tables"
• In reply to: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Fri, 20 May 2005 06:51:06 -0700

Hello Mike,

Yep, we applied SP4 to the client machines, but this didn't help.

No, we just calling custom SPs. Until I granted EXEC to the xp_sqlagent_*
procedures in the master database to the generic account, the developers
weren't even allowed to see the jobs. Once I granted the permissions, the
developers can see the jobs, but now they can't view or edit any of the job
steps until I grant EXEC access to xp_instance_regenumvalues in the master
database. There may be other extended procs that I will have to grant access
to, but we won't know yet until we do some more testing.

Apparently, Microsoft really locked down the security on the SQL Agent in SP4.

Thanks,
Jason

"Mike Epprecht (SQL MVP)" wrote:

> Hi
>
> Have you applied the SP4 to their developer machines also. The tools have
> had updates.
>
> Are you using any un-documented SP and XP's? Microsoft has added a lot of
> security on this when the user is not in the sysadmin role.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program: http://www.microsoft.com/mvp
>
> Blog: http://www.msmvps.com/epprecht/
>
> "Jason Delaune" <JasonDelaune@discussions.microsoft.com> wrote in message
> news:EFBEA7FC-E269-4A4F-BFCA-46B0A16AAE6D@microsoft.com...
> > Hello all,
> >
> > I have created a generic user for our developers to use as the owner of
> > the
> > SQL Server jobs they create. This way all developers can use a generic
> > account to manage the jobs they create so that all developers can easily
> > see
> > each other jobs. For the jobs that required administrator access, we setup
> > a
> > proxy account. This all worked great when our server was running SP3a.
> >
> > We recently applied SP4 to the server and now we are receiving all kinds
> > of
> > permission problems. Now when our developers what to see the jobs using
> > the
> > generic account (job owner) they get errors about permissions denied to
> > the
> > xp_sqlagent_* extended stored procedures as well as various other xp_*
> > extended stored procedures within the master database.
> >
> > What has changed with SP4 that would cause this problem? And what's the
> > easy
> > way to fix it other than making the generic account dbo within the master
> > database?
> >
> > Thanks,
> > Jason
>
>
>

• Previous message: Prakash: "Re: Permissions on stored procedures & tables"
• In reply to: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]