Joe Carbonella


Hi, I have the following setup:

- Win 2K Server, SP4

- SQL Srv 2K, SP4

- A 'DEV' domain, with an 'Administrator' account with all possible rights on the system

I need to configure a CmdExec proxy account in order to allow non-sys-admin users to execute the master.dbo.xp_CmdShell procedure.

When attempting to do this via QA as follows:

EXEC master.dbo.xp_sqlagent_proxy_account N'SET',
N'DEV', -- agent_domain_name
N'Administrator', -- agent_username
N'password' -- agent_password

...I get the following error:

"The system cannot find the path specified."

When attempting to do this via QA as follows (note: only change is adding domain to agent_username arg):

EXEC master.dbo.xp_sqlagent_proxy_account N'SET',
N'DEV', -- agent_domain_name
N'DEV\Administrator', -- agent_username
N'password' -- agent_password

...I get the following error:

"Error executing extended stored procedure: Specified user can not login"

I have tried this through Enterprise Manager and get identical results, of course.

I have also tried all of the following:

- different OS user accounts, including local system accounts with local admin rights;

- assigning the OS account to a SQL login with System Admin role/rights;

- specifically assigning the above SQL login with EXEC rights on the master.dbo.xp_CmdShell procedure;

- verifying local security policy settings, as per the following link: http://support.microsoft.com/ id=283811;

- pulling out my hair and banging my head against the wall.

Can anyone H E L P ! ! !

Thanks,

Joe




Re: SQL2K CmdExec Proxy Account Setup

Kent Waldrop Au07


Joe:

It has been a good while since I did one of these. I checked my notes and tried to confirm by checking a couple of web references. To me, this basically looks right and I cannot immediately spot the trouble. Hopefully someone that has dealt with this recently can comment. Sorry. :-(

( Give a look to the links listed by Caddre; I went to the same links. )






Re: SQL2K CmdExec Proxy Account Setup

Caddre

In 2000 the links below is where you get all you need to create the proxy.

http://msdn2.microsoft.com/en-us/library/aa260689(SQL.80).aspx


http://msdn2.microsoft.com/en-us/library/Aa260700(SQL.80).aspx







Re: SQL2K CmdExec Proxy Account Setup

Joe Carbonella

OK, I finally got this to work by re-installing... from scratch -- Win 2K OS (SP2!), SQL 2K (no SP's) and all.

My original thought here was that it might have been caused by one or another Windows auto-update patch. But in retrospect, I'm now thinking it might actually have been down to the server's network name having been changed after the initial SQL Server install. Dunno, I am honestly guessing here... but at least there's a "solution"!

Kent and Caddre, thanks for your reponses just the same...

J.





Re: SQL2K CmdExec Proxy Account Setup

Kent Waldrop Au07

Were you using the local server name for your domain name





Re: SQL2K CmdExec Proxy Account Setup

Joe Carbonella

I tried it every which way, including:

LocalServerName \ LocalAccountName

. \ LocalAccountName

Domain \ DomainAccount

etc.

And in every case, the account used had all the local access privileges required.