Hello.

I have a DTS package that has several Process tasks that run batch files.
These batch files contain a few osql commands where sql scripts are run.
When I initially boot my machine, with my local sql server, and I try to run
my DTS package the Process tasks fail. If I then open my dts package up in
design mode and add another process task that does the same sort of thing
(run a batch file with an osql command in it), the entire package will then
run fine. If I then save the package with this new task and reboot, it fails
again when my computer comes back up and I try to execute it.

So I guess the question is, "Why don't my Process tasks run successfully
after I reboot unless I create a new task in my dts package before I run it?"

Any help you can provide would be great as I'm about to throw my laptop out
the window.

Thanks in advance,

Darren

what are the error messages you are recieving?

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

"CreateProcessTask 'DTSTask_DTSCreateProcessTask_1': Process returned code
1, which does not match the specified SuccessReturnCode of 0.

"Simon Worth" wrote:

Resolved!

after putting a pause in my batch file so I could see what it was doing I
noticed that when you first open EM and run the batch file it would run it
from ....\mssql\binn. Since my sql scripts didn't reside in this directory it
would bomb. If I added a new process task and pointed it to a batch file in
c:\patload it would then execute the batch file from c:\patload and find the
scripts. So basically I had to include the entire path in my osql statement
like:

osql -Usa -Popenline -Sminsrvfnp02 -ic:\patload\delpat.sql
-oc:\patload\delpat.out -n

Don't you just love computers?

Thanks everyone.



"ddobier" wrote: