May 7, 2009 at 1:36 pm
Help,
I am experiencing issues with SSIS, where the package will consistently run fine in BIDS, but fail
intermittently when kicked off via a SQL 2005 job. The job will run fine 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 intermittently experience
issues.
The code has not been updated in weeks. In the past 6 days, I got the following results from the scheduled job:
Saturday:
Error - following messages:
Event Message
PackageStart Beginning of package execution.
OnWarning The specified network name is no longer available.
OnError Cannot write to the data file.
OnError Cannot copy or convert flat file data for column "UnplannedRegPaid".
OnError 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.
OnError 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.
OnWarning The specified network name is no longer available.
OnError Cannot write to the data file.
OnWarning SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (5) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
PackageEnd End of package execution.
Sunday:
Job completed successfully.
Monday:
Job completed successfully.
On Tuesday:
Error - following messages:
Event Message
PackageStart Beginning of package execution.
OnWarning The specified network name is no longer available.
OnError Cannot write to the data file.
OnError Cannot copy or convert flat file data for column "AllInUnPaid".
OnError 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.
OnError 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.
OnWarning The specified network name is no longer available.
OnError Cannot write to the data file.
OnWarning SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (5) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
PackageEnd End of package execution.
On Wednesday:
Job failed because I had output file open:
Message:Cannot open the datafile
On Thursday:
Job completed successfully.
I do have OLEDB Source Error Output going to a table, but that error table is empty.
Am stumped with this. Would appreciate any helpful suggestions!
Regards,
Ann Ortiz
May 8, 2009 at 7:24 am
In the server Event Log, was there anything abnormal going on during these times? I had an issue last year with GNE's that would hose up network connections to my file servers and create havoc for scheduled jobs with file imports and extracts...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply