RE: xp_cmdshell failed to execute because current security context is
- From: db <db@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 9 Jun 2009 07:40:01 -0700
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:
- Prev by Date: Compare Schema Between Two Databases
- Next by Date: RE: SQL 2005 Index fragmentation
- Previous by thread: Re: xp_cmdshell failed to execute because current security context is
- Next by thread: Re: xp_cmdshell failed to execute because current security context is
- Index(es):
Relevant Pages
|
