I am simply trying to run DTSrun.exe from the Job Agent in SQL Server and
everytime it Says that the job failed.

The job failed. The Job was invoked by User CHQPVUW0806\LenceRM. The last
step to run was step 1 (cmd).

The step failed.

This happens every if I just try to run dir or and other command.

My backup jobs are working, and other jobs that do not need CmdExec.

Help,

See if this helps:
http://www.support.microsoft.com/?id=269074

--
Andrew J. Kelly SQL MVP


"Ryan M. Lence" <Ryan M. Lence (AT) discussions (DOT) microsoft.com> wrote

Thanks for the link. It did help me learn more about sql server but did not
really help me fix my issue.

Even if I try to run simply dir from the SQL Job Agent I will get the listed
error.

Ryan

"Andrew J. Kelly" wrote:

If you look in the Job history you will see a checkbox labeled "show job
steps" (or similar). This should give you more details. But it is most
likely a permissions issue. Can you get dir to work using xp_cmdshell?

exec master..xp_cmdshell 'DIR *.*'

I assume you are running SQL 2000? If so there are two accounts that may
need permissions to do what you are asking. They are outlined in the KB
article. One is the account SQL Agent is running under and the other is the
Proxy depending on how you are running the job or what role the user is in.

--
Andrew J. Kelly SQL MVP


"ryanlence" <ryanlence (AT) discussions (DOT) microsoft.com> wrote

exec master..xp_cmdshell 'DIR *.*'

Ran just fine

"Andrew J. Kelly" wrote:

I created a proxy account, from what I understand SQL Server should only need
to use the account if the job owner is not a member of sa.

Having created a proxy account who is a memeber of the local admin group I
now get a new error message saying.

Step 1 of job 'DTSRun' (0x0F9B5D8784E34341960EC066AE7E7858) has caused an
exception in the CmdExec subsystem and has been terminated.

Any Ideas

"Andrew J. Kelly" wrote:

Did you ever get xp_cmdshell to work?

--
Andrew J. Kelly SQL MVP


"ryanlence" <ryanlence (AT) discussions (DOT) microsoft.com> wrote

Yes,

It ran just fine

"Andrew J. Kelly" wrote:

Well now it sounds like you have a problem with the package itself or how
you are calling it. Maybe someone else can help here but that isn't a whole
lot to go on.

--
Andrew J. Kelly SQL MVP


"ryanlence" <ryanlence (AT) discussions (DOT) microsoft.com> wrote

It is not the package as anything that is run from CmdExec Sql Agnet job will
fail. You can try DTSRun, dir, ping, hostname, and command that you run from
the job queue will fail.

"Andrew J. Kelly" wrote: