|
Home > Archive > MS SQL Server > March 2006 > xp_cmdshell in MSSQL2005 return error 1314
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
xp_cmdshell in MSSQL2005 return error 1314
|
|
| stephanie 2006-03-09, 7:23 am |
| I have followed the step to run
- exec xp_cmdshell_proxy_ac
count 'xxxx','yyyy'
- enable surface area configuration
- grant exec to xp_cmdshell to the sqllogin
But still got the error,
Msg 15121, Level 16, State 10, Procedure xp_cmdshell, Line 1
An error occurred during the execution of xp_cmdshell. A call to
'CreateProcessAsUser
' failed with error code: '1314'.
Any step missing to run xp_cmdshell for a non-sysadmin user in MSSQL2005?
Thanks in advance
| |
| Dan Guzman 2006-03-09, 7:23 am |
| From the command prompt:
NET HELPMSG 1314
returns
"A required privilege is not held by the client."
This indicates that the SQL Server Service account doesn't have the rights
needed to switch the connection security context to the proxy account. The
required advanced user rights are assigned when you specify the service
account during installation or change the service account later using
Enterprise Manager. However, the rights are not assigned if you change the
account via another method.
The easiest way to fix the problem is to use EM to change the account to
local system and then back to the desired Windows account. Alternatively,
you can assign the rights manually. The right are described in the Books
Online and article http://support.microsoft.com/kb/248391/en-us.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"stephanie" < stephanie@discussion
s.microsoft.com> wrote in message
news:0911B8BF-8F9C-4EBF-94A4- 31A99312A502@microso
ft.com...
>I have followed the step to run
>
> - exec xp_cmdshell_proxy_ac
count 'xxxx','yyyy'
>
> - enable surface area configuration
>
> - grant exec to xp_cmdshell to the sqllogin
>
> But still got the error,
>
> Msg 15121, Level 16, State 10, Procedure xp_cmdshell, Line 1
> An error occurred during the execution of xp_cmdshell. A call to
> 'CreateProcessAsUser
' failed with error code: '1314'.
>
>
>
> Any step missing to run xp_cmdshell for a non-sysadmin user in MSSQL2005?
> Thanks in advance
>
| |
| stephanie 2006-03-10, 3:23 am |
| Also, I found that the problem can be solved by add the desired Windows
account in Computer Management -> local users and groups ->
SQLServer2005MSSQLUs
er$<servername>$<instancename>
"Dan Guzman" wrote:
> From the command prompt:
>
> NET HELPMSG 1314
>
> returns
>
> "A required privilege is not held by the client."
>
> This indicates that the SQL Server Service account doesn't have the rights
> needed to switch the connection security context to the proxy account. The
> required advanced user rights are assigned when you specify the service
> account during installation or change the service account later using
> Enterprise Manager. However, the rights are not assigned if you change the
> account via another method.
>
> The easiest way to fix the problem is to use EM to change the account to
> local system and then back to the desired Windows account. Alternatively,
> you can assign the rights manually. The right are described in the Books
> Online and article http://support.microsoft.com/kb/248391/en-us.
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "stephanie" < stephanie@discussion
s.microsoft.com> wrote in message
> news:0911B8BF-8F9C-4EBF-94A4- 31A99312A502@microso
ft.com...
>
>
>
| |
| Dan Guzman 2006-03-10, 7:23 am |
| Yes, that's the proper method for SQL 2005 since those Windows groups have
the needed rights. I was thinking of SQL 2000 in my response. Sorry about
the confusion.
--
Dan Guzman
SQL Server MVP
"stephanie" < stephanie@discussion
s.microsoft.com> wrote in message
news:EAE4CB39-6654-4860-B973- 06D88A2D4864@microso
ft.com...[color=darkred]
> Also, I found that the problem can be solved by add the desired Windows
> account in Computer Management -> local users and groups ->
> SQLServer2005MSSQLUs
er$<servername>$<instancename>
>
> "Dan Guzman" wrote:
>
|
|
|
|
|