Re: Job owned by a non-sysadmin fails to run

For debugging, try temporarily changing the job owner to 'sa' as PSPDBA suggested. If the job still fails, then the problem is related to running as a job rather than a security issue.

Exactly what does the CmdExec step do? Are mapped drives accessed?

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Ivan Gerken" <testivan@xxxxxxxxxxxxx> wrote in message news:uE$3GeRJHHA.420@xxxxxxxxxxxxxxxxxxxxxxx
This quick solution is not an option.

Jobs are created from an external application (Business Desk of Commerce Server 2002). A created job is owned by the user logged in to the application (using win integrated authentication).

I definitely don't want to give users administrative privileges.

"PSPDBA" <DissendiumDBA@xxxxxxxxx> wrote in message news:1166704870.838450.230270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Try changing the owner of the job to SA or another sysadmin.





.

Relevant Pages

  • Re: SQL Agent Jobs Failing
    ... Is changing the job owner to "sa" an option? ... Tibor Karaszi, SQL Server MVP ... > SQL Agent runs under a domain account with sysadmin rights ...
    (microsoft.public.sqlserver.server)
  • Re: Weird SQL Server 2000 behavior in Transaction Log Shipping
    ... Can you please check the job owner is sa and then start the job - sometimes ... this lack of response is due to the job owner not being validated in AD. ... Paul Ibison SQL Server MVP, ...
    (microsoft.public.sqlserver.replication)