Hi
I have a stored procedure which runs for one and a half hours when executed
from sql server agent job. The same stored procedure runs for 10 minutes as a
dts package that gets run from sql server agent job. This is in development.
Now in test I cannot get the dts package step to run as it keeps failing
with this error:
The process could not be created for step 2 of job
0x11267FC6D743A048A98C2EA99EC096A9 (reason: The system cannot find the file
specified). The step failed.

This what I try to execute:
Exec xp_cmdshell '"\\server\c$\Program Files\Microsoft SQL
Server\80\Tools\Binn\dtsrun.exe" /S "server" /N "package" /W "0" /E '

I have searched the KB articles. Checked the owner of the package, login for
sql server agent job and its permissions to network resources, fully
qualified dtsrun.exe in the job step, made sure that there were no extra
spaces in the arguments for dstrun command.

Still no luck. Any ideas?

You may then be experiencing this then

Service Pack and Version Compatibility Problems
(http://www.sqldts.com/default.aspx?223)



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

Alan
I have got the version compatibility issue. We use Sql 2000.
Uma

"Allan Mitchell" wrote:

Alan
Sorry. I tried to say ' I have not got version compatibility issue'.

"Uma" wrote:

Set up logging in your package. Does it actually get into the package
itself or does it fail calling the package?

Why are you calling DTSRUN through a UNC?

Have you tried to log in to the server as the account which will run the
package and execute the exact same statement on the cmdline?


Allan

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

Alan
I have set up logging at the package level. I tried to run dtsrun through a
UNC as I had this error 'system could not find the path specified' without
that. It failed trying to run the package.

I deleted the second job step and typed the whole dtsrun command again. Now
it seems to be working. Looks like I had a space somewhere in the command
string. Not sure.
This is what I have got:
SET @cmdstr = ' dtsrun /S "CENSUSTEST\CENSUSTEST" /N
"run_api_code_edit_process_load" /W "0" /E '
EXEC @errorsave = master..xp_cmdshell @cmdstr, output
and is working.
Thank you for your useful suggestions.
Uma



"Allan Mitchell" wrote:

Little things like that can be hard to track down. Glad you sorted it.

Allan

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