Hi
I'm using an FTP task in a loop to download files from a WAN based FTP server. I've got a script to generate the name of the file I require and place into a variable. Problem is sometimes some of the remote files haven't been published so the FTP component errors and the package fails.
I tried setting StopOnFailure to False - all I get is the following errors
[FTP Task] Error: File represented by "User::RemotePath" does not exist.[FTP Task] Error: Attempt to read message string for 0x80020918 failed with error 0xc02090f3. Make sure all message related files are registered.
What I want to do is ignore the error and perform the next loop iteration
Is this a bug, or am I missing something
Dave
To ignore the ftp task error within a loop, put an OnError event handler on the FTP task. In the handler, set the System::Propagate variable to false. This setting will keep the error(s) in the ftp task from bubbling up the container hierarchy, and thus keep the loop from failing on a missing file.For example:
Imports Microsoft.SqlServer.Dts.Runtime
Public Class ScriptMain
Private vars As Variables
Public Sub Main()
Dts.TaskResult = Dts.Results.Success
Dts.VariableDispenser.LockForWrite("System::Propagate")
Dts.VariableDispenser.GetVariables(vars)
vars("System::Propagate").Value = False
vars.Unlock()
End Sub
End Class
P.S. Another way to ignore the ftp error is by configuring the MaximumErrorCount property on the loop executable to some relatively high number.
|||Excellent thanks, I initially set the MaximumErrorCount as a quick hack but thanks for the first suggestion - I've been meaning to figure out how OnError works.
|||
This sounds like the perfect solution for what I'm trying to do... but one question:
How do you "put an OnEvent handler on the ftp task"?
Not sure what this means.
Thanks much!!
|||Ok, I figured out the event handler tab functionality.
So, for my FTP task, I created an OnError event handler. I put a script task in the event handler.
Imports Microsoft.SqlServer.Dts.Runtime
Public Class ScriptMain
Private vars As Variables
Public Sub Main()
Dts.TaskResult = Dts.Results.Success
Dts.VariableDispenser.LockForWrite("System:
Dts.VariableDispenser.GetVariables(vars)
vars("System:
vars.Unlock()
End Sub
End Class
However, the FTP task is still failing as before, and failing the ForLoop container with it.
What am I doing wrong?
Thanks
|||Hello,
I am still trying to figure out why FTP the error is still "bubbling up" to the ForLoop container?
This is what I have:
ForLoop [ FTP task --> script task ]
In the FTP task Event Handler tab, I created an "On Error" event handler. It is a script task with the above poster's code that is supposed to turn off the System propogate variable. However, it isn't working. What am I doing wrong?
I need to turn off error handers in the FTP task, so that when I get a file not found error, it doesn't cause the ForLoop container to fail also. It needs to keep looping, even if the file isn't there yet.
Thanks much!
|||The system variable System:
So if an error occurs in the validation phase of the ftp task, the first time a System:
The two properties which also account for validation errors (which always bubble up at least one level) are ForceExecutionResult and MaximumErrorCount. By setting ForceExecutionResult=Sucess on the for each loop container or by setting MaximumErrorCount on the for each loop container to a large number, the loop will continue.
You can determine in which phase the the error(s) occur by observing if the error events fall exclusively between the OnPrevalidate / OnPostValidate events of the ftp task.
ropagate")