I am having a problem running bat or cmd files in my dts
packages. Whenever I first create a new package which
runs a bat file, the package runs fine. However, if I log
out of Enterprise Manager or schedule to run the package
later, the bat file is never able to run. From what I can
tell, it is asking for a parameter to be set. I can run
the bat file from a command prompt or Windows explorer all
day long without a parameter. ?????
Thanks,
Greg

What makes you think it is asking for a parameter to be set?
What does the bat file contain?

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Greg Barnes" <Greg.Barnes (AT) psc (DOT) state.ms.us> wrote

I have several different bat files that run in packages.
I have the same problem with all of them. One of them
ftps a file to our server, one of them deletes a file from
a previous run and renames a file.
I think it may be asking for a parameter because if you
run the package from Enterprise Manager, you can see the
cmd prompt screen flash by & it looks like the screen you
get when you type help cmd from the prompt.

It may weel be flashing up an error.

Try putting pause after significant steps and see whether that tells you the
problem

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Greg Barnes" <Greg.Barnes (AT) psc (DOT) state.ms.us> wrote

I put in a pause and was able to figure out what was going
on. In my bat files, I wasn't putting the etire path when
referencing other files. Apparently if you don't specify
the full path in your bat files, DTS looks for them in
C:\Program Files\Microsoft SQL Server\80\Tools\BINN. I
changed the bat files to include the entire path and
everything is working fine now. Thanks for your help.
Greg