I set up a very simple Execute Process Task which runs a batch file on our
server's local drive. The process works fine until I close and restart
Enterprise Manager. Then when I attempt to execute the package (which
contains only 1 task - the "batch file" task), execution fails. It will
only work again if I manually edit the properties of the Execute Process
Task to point to the batch file again (which already has the correct path
listed. I have to click browse, locate the same file that is already shown
in the path window, and hit enter). I can successfully execute the package
repeatedly until I close and restart Enterprise Manager.

I modified my batch file to print output to a file, and when package
execution fails no output file is generated, so I know DTS is not finding
the batch file.

If it helps to know, the batch file is used to process ftp commands, but I
don't think that has to do with the problem.

Thanks for any help!
Cory

--
Message posted via http://www.sqlmonster.com

I should have mentioned the error message I get when package execution
fails:

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

Thanks,
Cory

--
Message posted via http://www.sqlmonster.com

I recently ran into this myself. I put a "pause" in my batch file to figure
out what was going on. What I found out was that when I would edit my DTS
package in some way and then run it it would look run the batch file in the
directory where the batch file was located. As a result, it would find the
scripts I was trying to run from within my batch file. When I would close
Enterprise Manager it would run the batch file in a different directory. I
think it was like c:\program files\microsoft sql server\binn. To get around
this I put at the top of my batch file commands to change directories to my
proper working directory before executing my osql statements. It is
something like:

c:
cd\temp
osql .....

"Cory Rammer via SQLMonster.com" wrote:

I used your suggestion and it works great now. Thanks a lot!

Cory

--
Message posted via http://www.sqlmonster.com