Re: Job owned by a non-sysadmin fails to run
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Dec 2006 11:35:09 -0600
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
"Ivan Gerken" <testivan@xxxxxxxxxxxxx> wrote in message news:eXF$F3dJHHA.4376@xxxxxxxxxxxxxxxxxxxxxxx
Hi Dan,
Thank you for your ideas.
I tried to get command output in a different way. I specified "Output file" in the CmdExec step properties, tab Advanced. This helped me earlier to identify problems occurred when running the executable.
Now I get an empty file created after the job have executed successfully and no file created at all after it have failed. This makes me think that the job step was not executed at all. The folder where the output file is written has "full control" permission granted to everyone.
I tried your suggestion about redirecting stdout/stderr. It works fine from the command line. However, CmdExec declined to run it with the following message in the output file:
Error: Invalid command-line option: '>c:'
The command looks like the following:
dmlrun.exe /create:type=CSS;dml_item=26;css_site="<site name>" /server:<server name> /execute /wait >c:\temp\dmtest.txt 2>&1
I tried also to put c:\temp\dmtest.txt into double quotes but got the same error message.
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E82DADE6-9C93-4770-95A0-8026EF28782B@xxxxxxxxxxxxxxxxYou 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
.
- 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
- Re: Job owned by a non-sysadmin fails to run
- From: Ivan Gerken
- Job owned by a non-sysadmin fails to run
- Prev by Date: Re: Locked out of server?
- Next by Date: Re: auditing access to object
- 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
|