Re: SQL2k Sqlagentproxy fails to logon

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

From: "Chris Wood" <chris.wood@gov.ab.ca>
Date: Fri, 28 Jun 2002 09:06:25 -0600

Sue,

I am trying to add an account that SQL Agent will use to run jobs owned by
non-admins and get
Unable to set the SQL Agent proxy account because of the reason listed
below, 'Error executing extended stored procedure: Specified user can not
login'.
Is this because the account entered does not have the correct password
entered or the permissions of the account running SQL Server?

Thanks

Chris Wood
Alberta Department of Energy
CANADA

"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:74omhu0tuga22v8d73617f9i0s70ehf0vk@4ax.com...
> I think your permissions are probably not configured
> correctly for the SQL Server service account.
> I've seen someone else recently hit the Access denied with
> xp_sqlagent_proxy_account. The problem was due to the SQL
> Server account not running under a Windows
> administrator account to read or set the SQL Server Agent
> proxy account. It's not sa being denied permissions to
> execute the procedure but rather your SQL Server service
> account that does not have permissions to read the windows
> accounts.
> You get the 997 error when information can't be retrieved
> about the proxy account as well as when the proxy account
> isn't configured correctly. But I think you probably need to
> start with the permissions for the SQL Server service
> account first.
>
> -Sue
>
> On Thu, 27 Jun 2002 11:50:27 -0700, "Doug Little"
> <dlittle5@ford.com> wrote:
>
> >Hi,
> >We're running sql2k sp2 on w2k sp2 where we have a number
> >of jobs that have been running fine for over a year.
> >
> >Something recently changed where all jobs that use
> >OS Commands (CMDEXEC) now fail with the message "A problem
> >occurred while attempting to logon as the Windows
> >user 'SQLAgentCmdExec': The parameter is incorrect. The
> >step failed."
> >
> >Executing cmd_exec 'exec xp_cmdshell 'dir c:*.* /ad'
> >directly from a non-sa account gets us 'Msg 50001, Level
> >1, State 50001. Xpsql.cpp Error 997 from GetProxyAccount
> >on line 472"
> >
> >A review of the sqlagent.log file has an interesting
> >message '[298] SQLServer Error: 8198 Could not obtain
> >information about win nt grp/usr 'fordna1\cksinfra'.
> >sqlstate 42000 (ConnIsLoginSysAdmin)'
> >
> >We have the sqlagent set use use a proxy domain account
> >(which is fine, not locked, expired,etc)
> >
> >The sa can't execute the xp_sqlagent_proxy_account 'get'
> >to validate the proxy account info. He gets 'access is
> >denied'. I asked him to grant himself privledges and try
> >again. Hopefully that will show a glaring mistake.
> >
> >But, until then has anybody seen this before and can you
> >offer diag tips/resolutions.
> >
> >Thanks
> >Doug little
> >313-594-2706 dlittle5@ford.com
>

Relevant Pages

  • Re: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... Warren Brunk - MCITP - SQL 2005, ... Add it as a login to the SQL Server ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • Re: User authentication
    ... There are 2 SQL Server 2005 ... 1 SQL Server 2000 installed on another server ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: Microsoft Search service cannot be administered under the present user error SP3
    ... - Have not modified Administrator account, but i ran the SQL script anyway. ... SQL account is not a local administrator. ... > has this server ever been upgrade from SQL Server 7.0 or is this SQL ...
    (microsoft.public.sqlserver.fulltext)