Re: xp_sqlagent_proxy_account

From: Chris Wood (chris.wood@gov.ab.ca)
Date: 02/12/03 

From: "Chris Wood" <chris.wood@gov.ab.ca>
Date: Wed, 12 Feb 2003 10:19:26 -0700

Hitesh,

With SP3 you have to have a proxy account to run any xp_cmdshell commands
from inside a job that is not owned by a sysadmin. The account should be
different from the account running SQL Agent, but could be the same, and
may have to be a domain account if it needs to access folders on other
servers on the network. If it only needs to perform functions on the local
server then that is where is needs to be defined.

Chris Wood
Alberta Department of Energy
CANADA

"Hitesh Govind" <hgovind@hmausacom> wrote in message
news:043001c2d2ab$6ea91310$3301280a@phx.gbl...
> Hi,
>
> I'm having the same problem. Things used to work before I
> installed SP3 on SQL2000/Win2k.
>
> Does this proxy account need to be a "Domain Account" or
> can it be a local account running on a computer that is
> not part of a domain.
>
> Does the SQL Agent service account need to be the same as
> the proxy account or do they need to be different ?
>
> thanks
> Hitesh
>
>
> >-----Original Message-----
> >Chris -
> >That solved the problem.
> >Thanks very much for your help!
> >- Jeff
> >
> >>-----Original Message-----
> >>Jeff,
> >>Make sure that the account running SQL Server and/or
> >SQLAgent has these
> >>local policies set:-
> >>
> >>Act as part of the operating system
> >>
> >>Bypass traverse checking
> >>
> >>Increase quotas
> >>
> >>Log on as a batch job
> >>
> >>Log on as a service
> >>
> >>Replace a process level token
> >>
> >>Chris Wood
> >>
> >>Alberta Department of Energy
> >>
> >>CANADA
> >>
> >>"Jeff Miles" <milesjg@yahoo.com> wrote in message
> >>news:021c01c2d1fe$3cc447f0$a101280a@phx.gbl...
> >>> Running SQL 2000 SP2 on one system, SQL 2000 base on
> >>> another system. Both on Win2K servers.
> >>>
> >>> After upgrading the network security from NT4 to
> >2000/AD,
> >>> I can no longer update the proxy account.
> >>>
> >>> If I try to update with the GUI, I get:
> >>> "Unable to set the SQL Agent proxy account because of
> >the
> >>> reason listed below. 'Error executing stored procedure:
> >>> Specified user can not login'"
> >>>
> >>> If I run: exec master.dbo.xp_sqlagent_proxy_account
> >>> N'SET', N'domain', N'user', N'password' I get:
> >>> "Error executing stored procedure: Specified user can
> >not
> >>> login"
> >>>
> >>> I've tried every combination of id/password I have: for
> >>> the SQL Services, for the user I'm logged on to SQL as,
> >>> for the proxy account, for the Windows user, etc.
> >>>
> >>> Any ideas?
>

Relevant Pages

  • Re: SQL2005 - Snapshot agent wont start
    ... account, so I tried to change the Snapshot Agent to use this acct as well. ... get the proxy account info if it is running as LocalSystem. ... SQL Server Agent but I am guessing that you want to have integrated ...
    (microsoft.public.sqlserver.replication)
  • Re: proxy account in SQL 2000 cluster environment
    ... this is domain account with local admin right. ... Now when I try to reset proxy account through TSQL I get the message: ... Log on as a batch Job ... I have run into issue with proxy account in cluster - after failover ...
    (microsoft.public.sqlserver.clustering)
  • Re: Proxy Account
    ... you might try logging in interactively as the proxy account ... Try running the BCP command ... I am not a network admin and don't have anyone here ...
    (microsoft.public.sqlserver.programming)
  • Re: Proxy Account
    ... >> The SQL account should have write access on the remote location you are ... The command creates a text file that is ... The proxy account has access to the ... I am not a network admin and don't have anyone here ...
    (microsoft.public.sqlserver.programming)
  • Re: Unable to set SQL proxy for xp_cmdshell
    ... When I select the SID of the proxy account, ... i can login to SQL box using the proxy account via terminal ...
    (microsoft.public.sqlserver.security)