Re: How can I grant user run cmdexec

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 08/24/04

  • Next message: Greg Dunlap: "Re: Slammer variant?"
    Date: Mon, 23 Aug 2004 21:25:05 -0600
    
    

    This can happen when the startup account for SQL Server
    doesn't have the proper permissions. If you change the
    accounts through Enterprise Manager, the permissions and
    rights are taken care of for you. If not, you need to go
    through and verify the correct rights and permission. You
    could reset the service accounts through Enterprise Manager
    or go through the following article to check the permissions
    for the account:
    HOW TO: Change the SQL Server or SQL Server Agent Service
    Account Without Using SQL Enterprise Manager in SQL Server
    2000
    http://support.microsoft.com/?id=283811

    -Sue

    On Thu, 19 Aug 2004 10:49:52 +0800, "Nobody"
    <nobody@nospam.com> wrote:

    >I tried, but got below error:
    >Unable to set the SQL Agent proxy account because of the reason listed
    >below.
    >'Error executing extended stored procedure: Specified user can not login'
    >
    >I tried to add an account that already have SQL Admin. rights and I have
    >explicitly added the account on master\xp_cmdexec xsp.
    >
    >Please advice.
    >
    >
    >
    >
    >"Hari Prasad" <hari_prasad_k@hotmail.com> wrote in message
    >news:ORKb7Y1fEHA.596@TK2MSFTNGP11.phx.gbl...
    >> Hi,
    >>
    >> First you can give grant execute on xp_cmdshell (gtrant execute on
    >> xp_cmdshell to user) to the user in master database.
    >>
    >> If they are not a member of the sysadmin role then they execute it under
    >the
    >> prefix of the SQL Agent Proxy Account.
    >> sysadmin users would execute it as the account under which MSSQL Server
    >> service starts.
    >>
    >> How to set the proxy account:
    >>
    >> 1. Open enterprise manager and select management options
    >> 2. Right click abouve the sql Agent and select properties
    >> 3. Select the "job system" option
    >> 4. Set the "Non sysadmin job step proxy account
    >> 5. There you have give the valid OS level user with previlage.
    >>
    >>
    >>
    >http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:
    >> 80/support/kb/articles/Q264/1/55.ASP&NoWebContent=1
    >>
    >>
    >> Thanks
    >> Hari
    >> MCDBA
    >>
    >> "Cora" <anonymous@discussions.microsoft.com> wrote in message
    >> news:3a2801c47f53$0d7a2ba0$a301280a@phx.gbl...
    >> > I have a DTS task that needs to run cmdexec, how can I
    >> > grant the user have the rights to run this DTS but not
    >> > giving him Admin rights?
    >>
    >>
    >


  • Next message: Greg Dunlap: "Re: Slammer variant?"

    Relevant Pages

    • Re: SQL account rights
      ... Please advice what is the best, suitable rights rather than domain admin ... Warren Brunk - MCITP - SQL 2005, ... Add it as a login to the SQL Server ... files, or backups, make sure that the service account has Full ...
      (microsoft.public.sqlserver.security)
    • Re: User authentication
      ... There are 2 SQL Server 2005 ... 1 SQL Server 2000 installed on another server ... Windows account instead to run backup jobs. ...
      (microsoft.public.sqlserver.clients)
    • Re: Cannot connect to Query Analyzer
      ... For Query Analyzer, I tried replacing the file as you suggested but had the ... same results (Enterprise Manager starts up fine, ... I created an account on my laptop and changed SQL ... Try replacing the MMC app for SQL Server from the original ...
      (microsoft.public.sqlserver.connect)
    • Re: SQL 2000 Server gets hacked
      ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
      (microsoft.public.sqlserver.security)
    • Re: SQL 2000 Server gets hacked
      ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
      (microsoft.public.sqlserver.security)