Runaway log files

Some of you have run into a problem with the log files being written to and
consuming the entire hard drive. We have identified the issue and have
provided a fix. The KB article itself has not yet been published but the
fix is available through PSS. Please feel free to contact PSS and refer
them to KB 885286.
For everyone who has been waiting for this, thank you for your patience.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.Hi,
When will this fix be available for download?
Erik
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:OSFl%23KPnEHA.3076@.TK2MSFTNGP15.phx.gbl...
> Some of you have run into a problem with the log files being written to
and
> consuming the entire hard drive. We have identified the issue and have
> provided a fix. The KB article itself has not yet been published but the
> fix is available through PSS. Please feel free to contact PSS and refer
> them to KB 885286.
> For everyone who has been waiting for this, thank you for your patience.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>|||This has become a critical issue for the company I work
for.
A fix is needed pronto. Is this a matter of days for the
fix or "Future Thinking"?
>--Original Message--
>Hi,
>When will this fix be available for download?
>Erik
>"Daniel Reib [MSFT]" <danreib@.online.microsoft.com>
wrote in message
>news:OSFl%23KPnEHA.3076@.TK2MSFTNGP15.phx.gbl...
>> Some of you have run into a problem with the log files
being written to
>and
>> consuming the entire hard drive. We have identified
the issue and have
>> provided a fix. The KB article itself has not yet
been published but the
>> fix is available through PSS. Please feel free to
contact PSS and refer
>> them to KB 885286.
>> For everyone who has been waiting for this, thank you
for your patience.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties,
and confers no
>rights.
>>
>
>.
>|||At this point the fix is only available through PSS.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Erik Tamminga" <REVERSE_THIS_agnimmate@.REVERSE_THIS_nerrats.ln> wrote in
message news:eqTrhhvnEHA.2096@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When will this fix be available for download?
> Erik
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:OSFl%23KPnEHA.3076@.TK2MSFTNGP15.phx.gbl...
> > Some of you have run into a problem with the log files being written to
> and
> > consuming the entire hard drive. We have identified the issue and have
> > provided a fix. The KB article itself has not yet been published but
the
> > fix is available through PSS. Please feel free to contact PSS and refer
> > them to KB 885286.
> >
> > For everyone who has been waiting for this, thank you for your patience.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> >
>|||The fix is available now. You will need to contact PSS and reference the KB
number below. The fix is currently not available as a public download.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave Laskey" <anonymous@.discussions.microsoft.com> wrote in message
news:0ec501c49f2b$26f188b0$3501280a@.phx.gbl...
> This has become a critical issue for the company I work
> for.
> A fix is needed pronto. Is this a matter of days for the
> fix or "Future Thinking"?
> >--Original Message--
> >Hi,
> >
> >When will this fix be available for download?
> >
> >Erik
> >
> >"Daniel Reib [MSFT]" <danreib@.online.microsoft.com>
> wrote in message
> >news:OSFl%23KPnEHA.3076@.TK2MSFTNGP15.phx.gbl...
> >> Some of you have run into a problem with the log files
> being written to
> >and
> >> consuming the entire hard drive. We have identified
> the issue and have
> >> provided a fix. The KB article itself has not yet
> been published but the
> >> fix is available through PSS. Please feel free to
> contact PSS and refer
> >> them to KB 885286.
> >>
> >> For everyone who has been waiting for this, thank you
> for your patience.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties,
> and confers no
> >rights.
> >>
> >>
> >>
> >
> >
> >.
> >

Run entire package

Hello,

i have a problem that i don't understand why it occurs: i have a package like this (resumed and ordered by its correspondingdata flow):

1. move data files to a path through by a file system task

2. import data of data files to a sqlserver database (each file through its own data flow). The origin of data is in files that have been moved to the path of step 1

3. execute a procedure of database (sql task) to manipulate data and finally export resume (data flow) to a new file in the path (moved by other file system task)

PROBLEM: if i execute the package task by task (one by one), it runs ok, but then when i build and run package as a whole (debug), it produces an error in the data flow such as it doesnt' find the path to take data of data flow (it doesn't find the source). Really it doesn't find source because the data files aren't in its correct path (like step 1 had failed). In summary, it looks like if the order of the task of package aren't correct when i execute the entire package, because the log doesn't thread any error about step 1 (file system task).

ERROR MESSAGE: an OLE DB error has occurred. Error code: 0x80040E37

Thanks for any help.

Gema

I'm not really sure if this is you issue, as the limited error you gave doesn't quite fit, and you don't say which task that relates to. A common issue which I would expect to occur here is that your data flow may fail validation since the files it expects cannot be found, as validation takes place before they have been moved by your file system task. To fix this type of issue, set the DelayValidation property to true for any tasks that depend on resources that are created or maintained by previous tasks. So set your data flow task to DelayValidation = True, so that it will only be validated just before it executes, and after the file system task has moved the files to the correct location.|||

Thanks a bunch!

That was my problem.