The child package uses SQL Server logging. It is the log for the child
package that shows normal log entries for the first four, serially executed
steps, that shows a successful running by one of the data pump tasks, and
that shows that the rest of the data pumps have started but contain null end
times and execution statuses. There should be 28 steps, though. The package
log has no end time. The package is set to fail on log error. There is no
separate error file.

The results of sp_enum_dtssteplog is:

53531 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSExecuteSQLTask_9 4 0 2004-11-15 03:04:37.000 2004-11-15 03:04:38.000 0.32800000000000001 0
53532 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSExecuteSQLTask_5 4 0 2004-11-15 03:04:38.000 2004-11-15 03:04:38.000 0.73399999999999999 0
53533 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSExecuteSQLTask_1 4 0 2004-11-15 03:04:38.000 2004-11-15 03:04:44.000 5.109 0
53534 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSExecuteSQLTask_8 4 0 2004-11-15 03:04:44.000 2004-11-15 03:04:44.000 0.28199999999999997 0
53535 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSDataPumpTask_3 4 0 2004-11-15 03:04:44.000 2004-11-15 03:04:45.000 0.95299999999999996 0 538
53536 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSDataPumpTask_5 NULL NULL 2004-11-15 03:04:44.000 NULL NULL NULL NULL NUL
53537 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSDataPumpTask_1 NULL NULL 2004-11-15 03:04:44.000 NULL NULL NULL NULL NUL
53538 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSDataPumpTask_6 NULL NULL 2004-11-15 03:04:44.000 NULL NULL NULL NULL NUL
53539 6CBC4557-FF81-4728-A450-CEB14C92CFBA DTSStep_DTSDataPumpTask_10 NULL NULL 2004-11-15 03:04:45.000 NULL NULL NULL NULL NULL



"Allan Mitchell" wrote:

Do you have the child packages to "Fail On First Error"



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com


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

Actually, no.

"Allan Mitchell" wrote:

I'm not clear that that would make a difference in this case. It's not a
case of later errors masking an earlier error, it's a case of no error being
generated at all.

"SidneyDG" wrote:

What happens if you execute the child package by itself. There have been quite a few cases reported by people executing child
packages (are you doing this though the task) and errors no bubbling up. A few of them were solved by setting this property as
although something went west it was not enough to fail the package and hence the package retirned successfully.




--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com


"SidneyDG" <BEGINsadgeMIDDLE (AT) earthlink (DOT) netEND> wrote

I've run into that before, but unlike in those cases, this child package
doesn't record an error in its own package log. I'll have the DTS package
set to fail on first error.

The problem is intermittant, but increasing in frequency. Once 3 months
ago. Twice 2 months ago. Three times last month. So far, three times this
month. The recovery process is to re-run an edited version of the parent
package (which re-runs the child package), and a temporary job to execute the
temporary parent package; this recovery process is usually started 1-2 hours
after the initial failure (i.e. when the dayshift operator wakes up and
checks job statuses). It has yet to encounter the same error.

SidneyDG

"Allan Mitchell" wrote: