Re: Job owned by a non-sysadmin fails to run
- From: "Ivan Gerken" <testivan@xxxxxxxxxxxxx>
- Date: Mon, 25 Dec 2006 11:05:15 +0200
Looks like I have a problem with CmdExec jobs in general.
I changed the step command to "dir c:\temp" and it ran fine when owned by an
admin but failed when owned by a user. In case of being owned by a user even
the output file was not created. The folder c:\temp has "full control"
permission granted to everyone.
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:42FF0C9C-4AFC-42AF-9464-0931A1DDE13B@xxxxxxxxxxxxxxxx
I'm starting to run out of ideas. Do you have any CmdExec job steps that
successfully run as non-sysadmin users or is it just dmlrun.exe that has
the problem?
--
Hope this helps.
Dan Guzman
SQL Server MVP
.
- Follow-Ups:
- Re: Job owned by a non-sysadmin fails to run
- From: Dan Guzman
- Re: Job owned by a non-sysadmin fails to run
- References:
- Job owned by a non-sysadmin fails to run
- From: Ivan Gerken
- Re: Job owned by a non-sysadmin fails to run
- From: PSPDBA
- Re: Job owned by a non-sysadmin fails to run
- From: Ivan Gerken
- Re: Job owned by a non-sysadmin fails to run
- From: Dan Guzman
- Re: Job owned by a non-sysadmin fails to run
- From: Ivan Gerken
- Re: Job owned by a non-sysadmin fails to run
- From: Dan Guzman
- Re: Job owned by a non-sysadmin fails to run
- From: Ivan Gerken
- Re: Job owned by a non-sysadmin fails to run
- From: Dan Guzman
- Job owned by a non-sysadmin fails to run
- Prev by Date: Re: Restoring Databases with Encrypted Data to Another Server
- Next by Date: Re: Job owned by a non-sysadmin fails to run
- Previous by thread: Re: Job owned by a non-sysadmin fails to run
- Next by thread: Re: Job owned by a non-sysadmin fails to run
- Index(es):
Relevant Pages
|