Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Proxy account

11 views
Skip to first unread message

ilovesql

unread,
Sep 10, 2003, 1:55:28 PM9/10/03
to
I want to setup proxy account so that developers can run xp_cmdshell as
follows

EXEC master.dbo.xp_sqlagent_proxy_account N'SET',
N'mydomain', -- agent_domain_name
N'ntaccount', -- agent_username
N'123password'

I get a message saying
"Error executing extended stored procedure: Specified user can not login"

If I use
EXEC master.dbo.xp_sqlagent_proxy_account 'GET'
I get nothing.

I tried to do this from Enterprise MAnager also but same error.


Sue Hoegemeier

unread,
Sep 10, 2003, 2:37:29 PM9/10/03
to
Most of the times that I've seen that error come up, it was
due to the permissions and rights settings for the service
account not being set correctly - usually from someone not
using Enterprise Manager to change the service accounts.
Try setting(resetting) the service accounts through
Enterprise Manager and see if that helps.

-Sue

ilovesql

unread,
Sep 10, 2003, 3:47:24 PM9/10/03
to
I am getting same error message from EM that user can not login.

The Ntaccount I am using to do the task is Admin as well as SA and the
account I am using for Proxy has the same priveleges.

"Sue Hoegemeier" <Su...@nomail.please> wrote in message
news:elrulv8gi0qk69f3q...@4ax.com...

Sue Hoegemeier

unread,
Sep 10, 2003, 4:04:34 PM9/10/03
to
Sorry...I didn't mean to try setting he proxy account in
Enterprise Manager. What I meant was to reset the service
account for SQL Server in Enterprise Manager. Resetting it
(even to the same account) will udpate the rights and
permissions for the account. The problem is likely related
to the rights and permissions of the service account that
SQL Server runs under.

-Sue

On Wed, 10 Sep 2003 15:47:24 -0400, "ilovesql"

ilovesql

unread,
Sep 11, 2003, 11:56:39 AM9/11/03
to
Thanks Sue. I would check this.

"Sue Hoegemeier" <Su...@nomail.please> wrote in message
news:6q0vlv8449o3kdlmc...@4ax.com...

Gert E.R. Drapers

unread,
Sep 12, 2003, 2:43:28 PM9/12/03
to
Most of the times this is caused due to insufficient priviliges of the SQL
Server service account used.
Go to SQL EM, Server Properties, Security tab, set the service account to
LocalSystem, restart SQL Server.
Repeat the same process to set it back to the account you want to use.

Try again to set the proxy account.

if that does not work, use the following alternative way to execute the XP

EXEC master.dbo.xp_sqlagent_proxy_account N'SET',
N'mydomain', -- agent_domain_name
N'ntaccount', -- agent_username
N'123password'

N'machine name', -- name of the machine or note your are
running on
N'Administrator', -- local machine administrator account
N'123AdminPassword'

Ge...@SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.

"ilovesql" <ilov...@hotmail.com> wrote in message
news:erL3MS8d...@TK2MSFTNGP09.phx.gbl...

Michael

unread,
Jan 27, 2017, 9:53:40 AM1/27/17
to
Please assist

I am getting the below type of error message for all jobs that uses proxy account. These jobs runs fine before with proxy account.

Executed as user : Domain\Account.

The process could not be created for step Step Number of job Unique Job ID (reason: A required privilege is not held by the client). The step failed.

I have tried the below resolution with no luck

https://support.microsoft.com/en-gb/help/911305/sql-server-agent-jobs-may-fail-after-you-change-the-sql-server-agent-service-startup-account-by-using-the-windows-service-control-manager
0 new messages