sql server dts: Hi,

I'm new to this so please be gentle if I make a faux pas.

I have a DTS script designed to run other DTS scripts in parallel, but
its failing on the first script. I'm trying to run it from Enterprise
Manager. The errors are logged as follows:

Step 'Execute APOeWFM Load Incremental Meta Data' failed

Step Error Source: Microsoft Data Transformation Services (DTS)
Package
Step Error Description:The filename, directory name, or volume label
syntax is incorrect.
The filename, directory name, or volume label syntax is incorrect.

Step Error code: 8007007B
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:1100

Step Execution Started: 27/11/2003 13:56:23
Step Execution Completed: 27/11/2003 13:56:23
Total Step Execution Time: 0 seconds
Progress count in Step: 0

I have also had 'The filename or extension is too long' and ' Cannot
find the file specified in the current location'.

I'm running on SQL2000 SP3 with Windows 2000 server. All the scripts
it points to run fine on their own. I just can't run them from this
script.

Any help will be very much appreciated

Thanks

In article <803ed22e.0311270619.5080b17@posting.google.com>, Richard
Moss <richard_moss@aimtechnology.com> writes
[quoted text, click to view]
<snip>

Can you describe or provide the code for the step "Execute APOeWFM Load
Incremental Meta Data".

Which package is this step in, parent or child?


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

[quoted text, click to view]

Thanks for responding, I really appreciate it.

The Incremental Meta Data package is the child. It forms part of a set
of scripts designed to take data from a database holding realtime data
and upload it into a set of OLAP cubes. The problem occurs when trying
to run an overnight upload. At this point we use the Full Process
Parallel script to call these other scripts.

This script is not used when the system has just been installed, i.e.
we use another script called Initial Package Setup, and this works
fine. As do the other packages.

I suspect that the paths are becoming concatonated in the Parallel
Script with multiple usage, but I'm not sure.

Is this any help? Can't really provide the code unfortunately. I will
try to provide more though when I can.

In article <803ed22e.0311280114.58495648@posting.google.com>, Richard
Moss <richard_moss@aimtechnology.com> writes
[quoted text, click to view]

There isn't a lot I can recommend from this. You didn't say what type of
step it was that failed. If it is an ActiveX Script then you really want
to get the line number as well.

Run the package interactively on the server, logged on under the same
account as the service account. I often find this useful as you get
slightly better error messages from the progress dialog, and you can
also check the state of any variables immediately post execution, which
are lost if executed in an unattended manner.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org