Re: Problems with SQL Srv. Agent and Proxy Account

From: Sue Hoegemeier (Sue_H@nomail.please)
Date: 05/17/02 

From: Sue Hoegemeier <Sue_H@nomail.please>
Date: Fri, 17 May 2002 09:47:52 -0600

You need to go to the General Tab of the SQL Server Agent
Properties window. This is where you set the service startup
account for Agent.

-Sue

On Fri, 17 May 2002 07:22:09 -0700, "Jakob Persson"
<jakobpersson@yahoo.dk> wrote:

>Hi Sue
>
>thank you for your answer.
>
>It should allready be a member of the administrators on
>the local computer - I have checked and re-checked.
>
>I have tried with both the sa account and with Use Windows
>Authentication on the SQL Server AGent Connection tab. But
>alas still the same result.
>
>Any other ideas? (I'm desperate....)
>
>kind regards
>
>jakob
>
>
>
>
>>-----Original Message-----
>>SQL Server Agent account can't use sa - it needs to use a
>>Windows Account.
>>If SVC_SQLAGENT is the domain account you want to use for
>>SQL Server Agent, try adding this account to the local
>>admins group on your SQL Server PC and make sure the
>Account
>>referenced for SQL Agent is SVC_SQLAGENT, not sa.
>>
>>-Sue
>>
>>On Fri, 17 May 2002 05:11:14 -0700, "Jakob Persson"
>><jakobpersson@yahoo.dk> wrote:
>>
>>>Hi
>>>
>>>On SQL Server 7.0 SP3 Std. Edt installations (and a
>single
>>>7.0 SP3 Desktop Edt.)
>>>
>>>I have made an domian user account SVC_SQLAGENT (with
>user
>>>rights recording to INF: Reset Proxy and the
>>>SQLAgentCmdExec Account (Q264155))
>>>
>>>I get this error when starting the SQL Server Agent:
>>>
>>>[000] Password verification of the 'SQLAgentCmdExec'
>proxy
>>>account failed (reason: A required privilege is not held
>>>by the client)
>>>
>>>The agent starts, I can execute the jobs I have
>configured
>>>(maintenance and backup) ,but I still need to setup
>>>replication on the server - and I am not happy with this
>>>message.
>>>
>>>I have tried to:
>>>- both reset the Proxy account and Proxy Password of
>>>the "SQLAgentCmdExec" on the Job system tab of the SQL
>>>Agent properties
>>>
>>>- Set my sa user as the account that the SQL Server
>Agent
>>>should use to connect to the SQL Server
>>>
>>>- Re-entered the pwd for the SQL Server Agent user acount
>>>
>>>- Stopped and Started the SQL Agent sercive
>>>
>>>What have I done wrong?
>>>
>>>What to do to avoid this error?
>>>
>>>Thank you
>>>
>>>Jakob Persson
>>>Mærsk Data AS
>>>Denmark
>>
>>.
>>

Relevant Pages

  • Re: VS2005: SQL Debugging "T-SQL execution ended without debugging. You may not have sufficient
    ... > account also must be a member of the sysadmin role in the target SQL ... and the Windows firewall is disabled on both client & server. ... to the remote SQL Server 2005. ... But I'm still getting the "T-SQL execution ended without debugging. ...
    (microsoft.public.vsnet.debugging)
  • RE: DTS Package fails when Scheduled
    ... Make sure SQL Server Agent account has the correct rights/permissions. ... scheduled job under this context, I still received the error, even though I ...
    (microsoft.public.sqlserver.dts)
  • Re: Utter madness!
    ... It is just Windows security stuff. ... You can get a trusted connection back to SQL server. ... ASP.NET account (either processModel or app pool identity depending on ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Passthrough authenication w/ SQL trusted connection
    ... separate connection will be used for each security context (each user ... account will have it's own pool). ... if you are using a Windows 2000 Domain, ... backend SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Search services not available
    ... Let me clarify that our SQL server uses Windows Authentication, ... account, even if it was just for now to get it working, that would be easier ... I have configured the Search service to use this ...
    (microsoft.public.sharepoint.windowsservices)