Re: xp_cmdshell failed to execute because current security context
- From: db <db@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 10 Jun 2009 05:46:01 -0700
How to check if user has the permission to execute xp_cmdshell and if user
does not have permission, how to grant permission.
--
ontario, canada
"Tom Moreau" wrote:
When you run xp_cmdshell yourself, are you a system admin? Has the user.
been granted permission to execute xp_cmdshell?
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"db" <db@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0221B5E0-9A04-4FDC-94FD-076BCA9FB626@xxxxxxxxxxxxxxxx
No. Yes it works as master.dbo.xp_cmdshell. But still in the application I
have that error message. I do not have access to application code but in the
logs I still have the same error message. What could be the issue?
--
ontario, canada
"Tom Moreau" wrote:
Did you run it as master.dbo.xp_cmdshell?
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"db" <db@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EAB61CBA-6830-4589-8FAC-2F8C852E93CF@xxxxxxxxxxxxxxxx
Thanks Tom. I have checked that article.
When I run " xp_cmdshell 'dir *.exe'" useing master database I get the
directory listing. When I run it against the production database I get:
==============================
Server: Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'xp_cmdshell'.
=============================
--
ontario, canada
"db" wrote:
Microsoft SQL server standard edition
Microsoft windows NT 5.2 (3790)
Platform: NT INTEL X86
Version: 8.00.2039
SQL server 2000 SP4
Application error log has following message:
xp_cmdshell failed to execute because current security context is not
sysadmin and proxy acount is not setup correctly. For more information,
refer
to Book Online, search for topic related to xp_sqlagent_proxy_account.
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown
Source)
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown
Source)
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown
Source)
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown
Source)
com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown
Source)
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown
Source)
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown
Source)
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(Unknown
Source)
--
dbdba
ontario, canada
- Follow-Ups:
- References:
- xp_cmdshell failed to execute because current security context is
- From: db
- RE: xp_cmdshell failed to execute because current security context is
- From: db
- Re: xp_cmdshell failed to execute because current security context is
- From: Tom Moreau
- Re: xp_cmdshell failed to execute because current security context
- From: db
- Re: xp_cmdshell failed to execute because current security context
- From: Tom Moreau
- xp_cmdshell failed to execute because current security context is
- Prev by Date: FlatFile Encryption using FILESTREAM
- Next by Date: RE: Cannot drop the table '#tmp_sp_db_vardecimal_storage_format'
- Previous by thread: Re: xp_cmdshell failed to execute because current security context
- Next by thread: Re: xp_cmdshell failed to execute because current security context
- Index(es):
Relevant Pages
|
