Re: SQL Server Agent Proxy Error

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Jason Delaune (JasonDelaune_at_discussions.microsoft.com)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 05:59:05 -0800

OJ,

Okay, I think we got it. I ran the following command from Query Analyzer:

EXEC xp_sqlagent_proxy_account N'GET'

And when I did, I got "Access is Denied" as a result. I did this as 2 users
that had SA privileges and got the same results each time, which led me to
believe we had issues elsewhere. So, I made the account that runs SQL Server
and SQL Server Agent a member of the local admins group on the server. Then I
restarted both services, and reran the above command. This time I got back
the expected results. The proxy accout was set properly, but I guess since
the account running SQL Server and SQL Server Agent wasn't a member of the
local admins group, then it couldn't get the proxy account information either
when trying to execute the job, which led to the cryptic error message.

Well, thanks again so much for your help! I really appreciate it!
Jason

"oj" wrote:

> Jason,
>
> Something is not set right. Please use this article to set agent proxy.
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_8sdm.asp
>
> Also, be aware that SP3 has added a new flag. You might have to set it to
> your environment.
>
> e.g.
> --restrict to admin only. 1=yes, 0=no
> EXECUTE msdb..sp_set_sqlagent_properties @sysadmin_only = 0
> go
>
>
>
> "Jason Delaune" <JasonDelaune@discussions.microsoft.com> wrote in message
> news:3FA249EE-D9DA-4884-A437-BEEFC586EE93@microsoft.com...
> > OJ,
> >
> > Nope, that didn't work either. Still get the same error message. Thanks
> > for
> > your persistent help!
> >
> > Jason
> >
> >
> > "oj" wrote:
> >
> >> Jason,
> >>
> >> See if this helps.
> >> http://support.microsoft.com/kb/298725
> >>
> >>
> >> "Jason Delaune" <JasonDelaune@discussions.microsoft.com> wrote in message
> >> news:A9A35584-4220-4A4A-B873-4823A480D73E@microsoft.com...
> >> > OJ,
> >> >
> >> > Thanks for the link. I checked the local security policy settings on my
> >> > server against what was listed in the KB article, and they were set
> >> > correctly. I didn't however reboot the server once I made the changes
> >> > ...
> >> > I
> >> > had just restarted the services. So, I rebooted the server, but no
> >> > luck.
> >> > The
> >> > error still occurs. :(
> >> >
> >> > Jason
> >> >
> >> >
> >> > "oj" wrote:
> >> >
> >> >> Please take a look at this kb for some info:
> >> >>
> >> >> http://support.microsoft.com/?id=264155
> >> >>
> >> >>
> >> >> "Jason Delaune" <JasonDelaune@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:E3D14DC8-20E0-4757-A5F1-5432A718AC50@microsoft.com...
> >> >> > Hello all,
> >> >> >
> >> >> > I have several non-sysadmin developers who are creating SQL Server
> >> >> > jobs
> >> >> > that
> >> >> > call ActiveX scripts. I have setup the SQL Server Proxy account and
> >> >> > password,
> >> >> > and I restarted the Agent service to make sure the change took
> >> >> > effect.
> >> >> > However, when they execute their job, they get the following error
> >> >> > message:
> >> >> >
> >> >> > Unable to set proxy user context (reason: The parameter is
> >> >> > incorrect). The step failed.
> >> >> >
> >> >> > Has anyone ever seen this message and know how to correct it?
> >> >> >
> >> >> > Thanks for your help!
> >> >> > Jason
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Relevant Pages