Package failed error message when executing job (SSIS FTP Task)

I have a SSIS package that should do the following:
* get files from an FTP server to a local folder
* for each file do something
* after retrieving all the files and treat them execute another SSIS package

This package is configured to run as a job and is executed hourly. However it may happen that sometimes we don't have files to retrieve from the FTP server but the process show behave correctly.

What happen is that if I run the package from Microsoft Visual Studio I have a green color on FTP Task box and the process goes until the end smothly, but when I run it from job I get the package failed error:

Message
Executed as user: XXXXXXX\yyyyyyy. Microsoft (R) SQL Server Execute Package Utility  Version 10.0.1600.22 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  11:00:00  Error: 2009-07-05 11:00:01.12     Code: 0xC0029183     Source: Get backend files FTP Task     Description: File represented by "/ftp/bbbbbbbftp/backend/*.xls" does not exist.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  11:00:00  Finished: 11:00:02  Elapsed:  2.5 seconds.  The package execution failed.  The step failed.

Because I don't want the package to fail I configured the FTP Task properties like this:
FailPackageOnFailure = False
FailParentOnFailure = False
MaximumErrorCount=0

How can I have this job running whithout reporting failure even when I don't have files in FTP server that need to be processed?

Tkx
SSIS-FTP-Task-error---execution-.JPG
SSIS-FTP-Task-error.JPG
gurupesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rob_farleyCommented:
I'd put the MaximumErrorCount to 2, personally...

Or... handle the error by putting another task in there, connecting with the red arrow instead of the green.

Rob
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jbyers79Commented:
You may want to take a look at setting the ForceExecutionResult property to "Success"

Even if the task fails, the task result will be forced to "Success"
0
rob_farleyCommented:
Angel Eyes,

All he needs is error-handling.

Rob
0
rob_farleyCommented:
Angel Eyes,

All he needs is error-handling.

Rob
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Protocols

From novice to tech pro — start learning today.