How to resolve File Transfer Task failing when no files exist.
If you are not sure there will be files on the remote server
when you execute the package and you do not want the package to fail in that situation, then set the NoFilesFail parameter to "False". If
you are converting your packages over from using the deprecated SFTP Task, then
be aware that this is a new parameter. With the SFTP Task, setting the StopOnFailure parameter to "False" would accomplish the same
thing. The following table makes it clear how these two parameters are used with
the File Transfer Task.
NoFilesFail | StopOnFailure | Result |
True | False | Task will fail if there is no file. Task will not fail for any other errors related to the operations
it’s performing. |
False | False | Task will not fail if there is no file. Task will not fail for any other errors related to the operations
it’s performing. |
True | True | Task will fail if there is no file. Task will fail for any other errors related to the operations it’s
performing. |
False | True | Task will not fail if there is no file. Task will fail for any other errors related to the operations it’s
performing. |
The NoFilesFail Property can be found by right clicking the File Transfer Task --> Choose Properties --> Under Misc grouping set 'NoFilesFail' = 'False'
The File "" doesn't contain file path(s). See ticket 11056