April 22, 2009 at 4:05 pm
Help,
I am experiencing issues with SSIS, where the package will run fine in BIDS, but fail
intermittenly when kicked off via a SQL job. I have seen a job run one day and fail the next
with no code changes. Specifically, the SSIS package does the following:
1. Executes a SQL task which populates the data to be output in a SQL reporting table.
2. A Data Flow task copies the data from this SQL reporting table to a flat file destination
(csv file). The package includes several variables, for generating the output file name and folder and
changing parameters for determining which population to select. I included package configurations to allow me
to readily update the parameters used and the output file path.
The package runs fine from BIDS. However, when I try to schedule this to run as a SQL job I experience
some issues. I ran this several times today. The only thing I changed was a parameter
in the dtsConfig file for the business. I started with a small population (about 900 people) without any issues.
I then updated the dtsConfig file BusinessId parameter to select a slightly larger population (about 9000 people).
Job ran fine. I next updated this to point to an even larger population ( about 44,000 people)
and the job errored out.
Note, when this runs from BIDS for this population (or a population twice this size), it works fine.
Below are the error messages I am got today when this errored out:
-- For First error run:
The specified network name is no longer available.
Cannot write to the data file.
Cannot copy or convert flat file data for column "UnplannedRegPaid".
SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Flat File Destination" (1016) failed with error code 0xC02020A0. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC02020A0. There may be error messages posted before this with more information on why the thread has exited.
-- For Second error run (note, I had not changed anything from previous run other than scheduling the job
rather than kicking it off manually):
The specified network name is no longer available.
Cannot write to the data file.
Cannot copy or convert flat file data for column "DeptId10".
SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Flat File Destination" (1016) failed with error code 0xC02020A0. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC02020A0. There may be error messages posted before this with more information on why the thread has exited.
Regards,
Ann Ortiz
July 1, 2009 at 5:02 pm
Hello everyone,
I'm experiencing exactly the same problem with the difference of the package, scheduled as a SQL job, failing on a very rare occasion with the aforementioned error. It is a critical package and failure, however occasional, is not an option for us. Considering that over the course of several years, this error was generated only twice, the assumption of permissions is not an issue.
Does anyone have an idea of what could cause it? Though I found some references on line to the same problem, no one seemed to have an answer.
Thank you very much in advance.
Best Regards,
Lana
September 28, 2012 at 8:25 am
hello,
Has solved the problem? me is the same. please help!
RZ.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply