RE: master..xp_cmdshell Error 997 from GetProxyAccount

From: Frank (Frank_at_discussions.microsoft.com)
Date: 07/30/04

  • Next message: jimtone7: "Re: Re: sql hacked"
    Date: Thu, 29 Jul 2004 17:49:04 -0700
    
    

    - Start SQL Enterprise manager
    - Open your server
    - open the Management folder
    - right mouse on SQL Server Agent and select properties
    - select Job System tab
    - UNCHECK the box in the section 'Non SysAdmin job step proxy account'
      which says 'Only users with SysAdmin priveleges can ...'
    - when the dialog comes up enter the username, password, [domain] of
      some defined Windows user with sysAdmin priveleges (create one if needed first).
    - click Apply and OK

    "Phil" wrote:

    > Hello all,
    >
    > I have an aspx page that inserts a record in a table via a stored
    > procedure. That table has a trigger which gets fired on an insert. The
    > trigger has the following code
    > EXEC master..xp_cmdshell 'C:\MyApp\try.exe'
    > This all works when the stored procedure is fired inserting the record
    > in turn firing off the trigger; but when the ASPX page runs the stored
    > procedure I get the following error.
    >
    > A severe error occurred on the current command. The results, if any,
    > should be discarded. xpsql.cpp: Error 997 from GetProxyAccount on line
    > 472
    >
    > The Guest login has permissions to the extended stored procedure
    > xp_cmdshell on the master db, but this has not helped.
    >
    > Any help would be greatly appriciated.
    > Phil
    >


  • Next message: jimtone7: "Re: Re: sql hacked"

    Relevant Pages

    • RE: master..xp_cmdshell Error 997 from GetProxyAccount
      ... Start SQL Enterprise manager ... right mouse on SQL Server Agent and select properties ... select Job System tab ... > This all works when the stored procedure is fired inserting the record ...
      (microsoft.public.sqlserver.programming)
    • Re: sql expression
      ... Create a stored procedure ... similar to that shown below in SQL Enterprise Manager. ... param2 and param3) or whatever and how many ...
      (microsoft.public.vb.crystal)
    • Package fails when run from Sql Server Agent
      ... I have a stored procedure that createz a DTS package on the fly using ... Step error code: 8004206A ... What would cause some rows to fail when using Sql Server Agent? ...
      (microsoft.public.sqlserver.dts)
    • Re: Timed Events
      ... and schedule it to run via SQL Server Agent. ... The easiest way to setup a job to run is to open Enterprise Manager ... > How can I write a stored procedure that runs at a particular time every ...
      (microsoft.public.sqlserver.programming)
    • Re: Is it possible to set a scheduled job for executing a store procedure?
      ... you can scedule a job to execute a stored procedure and send a ... SQL Enterprise Manager. ...
      (microsoft.public.sqlserver.programming)