Re: Job owned by a non-sysadmin fails to run
- From: "MB" <MB@xxxxxx>
- Date: Fri, 22 Dec 2006 20:50:38 +0530
Try "xp_cmdshell" and make sure that user have permission for stored
procedure for "xp_cmdshell"
MB
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E82DADE6-9C93-4770-95A0-8026EF28782B@xxxxxxxxxxxxxxxx
You mentioned earlier that you looked at the job for error messages. Do
you get any additional messages from the job step details? If not, try
redirecting stdout/stderr to a file using on the command line:
MyProgram.exe (other command-line arguments) >C:\MyProgram.log 2>&1
Obviously, there a subtle difference when the program runs interactively
under the proxy account vs. as a job step. This could be due to a
different environment (different path, environment variable, etc.) or the
way the program retrieves configuration information under the different
execution contexts. I see that there's a Commerce Server bug
(http://support.microsoft.com/kb/818143/) that required dbo rights but
that wouldn't explain why the program runs interactively without errors.
However, that's been fixed in a service pack.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Ivan Gerken" <testivan@xxxxxxxxxxxxx> wrote in message
news:Ox81y3aJHHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
Hi Dan,
Certainly I tried changing job owner to an account with administrative
privileges, and the job ran perfectly after that.
The job runs the command-line executable of DirectMailer (Commerce Server
2002). As I wrote earlier, this executable runs fine if I login
interactively as user (non-admin) as well as sqlproxy and execute it from
the command line.
Mapped drives are not accessed.
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C369A6FD-078E-4150-9874-EA1203FE7786@xxxxxxxxxxxxxxxx
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
.
- Follow-Ups:
- Re: Job owned by a non-sysadmin fails to run
- From: Ivan Gerken
- 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
- Job owned by a non-sysadmin fails to run
- Prev by Date: Re: Job owned by a non-sysadmin fails to run
- 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
|
|