RE: xp_sqlagent_proxy_account

From: Kevin McDonnell [MSFT] (kevmc_at_online.microsoft.com)
Date: 12/30/03 

Date: Tue, 30 Dec 2003 20:17:36 GMT

Start|Run|cmd.exe and type the following two lines:
CD C:SET
If SET returns a LOGONSERVER value that is the local box's name (as opposed
to the
name of a domain controller) then you are logged onto this box using cached
credentials and instead this box needs to logon to the domain (and
rebooting the
box may cause the logon server to now more appropriately be the Domain
Controller).
If no reboot is needed (because the LOGONSERVER is set to a Domain
Controller) then
keep the command prompt window open (as it's needed in step 4).

1)
Verify that the startup account for SQL Server and SQL Agent services are
NT
domain accounts and are member of the local administrators group.

2)
Verify that the startup account for SQL Server and SQL Agent services have
the
following rights
Act as part of the Operating System
Increase Quotas
Log on as a Service
Replace a process level token
Log on as a batch Job
(per http://msdn.microsoft.com/library/en-us/instsql/in_overview_6k1f.asp)

3)
Verify that the account that you want to use for "SQL Agent proxy account"
has the
"Log on as a batch job" right. If not, then assign it the right using the
instructions in step 2.

Thanks,

Kevin McDonnell
Microsoft Corporation

This posting is provided AS IS with no warranties, and confers no rights.

Relevant Pages

  • Re: Very Very Urgent, Please Help
    ... production servers services will always run under domian admin account. ... It sounds like you are running the SQL Agent service under the local ... system account which does not have access to the DTS packages. ...
    (microsoft.public.sqlserver.datawarehouse)
  • RE: dts package error
    ... "Donna Lambert" wrote: ... > under the context of the SQL Agent account. ... > account and try to manually kick off the package. ...
    (microsoft.public.sqlserver.dts)
  • RE: dts package error
    ... under the context of the SQL Agent account. ... account and try to manually kick off the package. ... > When it runs through the scheduler it cannot find the mdb file on the server. ...
    (microsoft.public.sqlserver.dts)
  • Re: Very Very Urgent, Please Help
    ... Try logging onto the server under the domain account that the SQL Agent ... >> system account which does not have access to the DTS packages. ...
    (microsoft.public.sqlserver.datawarehouse)