SSIS - error message
Hi, I have a Package running on a server - SQL Server 2005 - 9.0.3042 DFT - Source SQL server 2000 8.0.2040 to Destination SQL Server 2005 9.0.3042 My workstation has sql 2005 client tools installed. The package fails with the below message when the agent job runs nightly. The same package when exported and run from my workstation completes successfully. OnError, computer,operator,source,sourceid,executionid,starttime,endtime,-1071607780,0x,There was an error with output column "col1" (125) on output "OLE DB Source Output" (11). The column status returned was: "Text was truncated or one or more characters had no match in the target code page.". OnError, computer,operator,source,sourceid,executionid,starttime,endtime,-1071607766,0x,The "output column "COL1" (125)" failed because truncation occurred, and the truncation row disposition on "output column "COL1" (125)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component. OnError, computer,operator,source,sourceid,executionid,starttime,endtime,-1073450952,0x,SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Table1" (1) returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. OnError, computer,operator,source,sourceid,executionid,starttime,endtime,-1073450975,0x,SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited. OnError, computer,operator,source,sourceid,executionid,starttime,endtime,-1073450951,0x,SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled. OnError, computer,operator,source,sourceid,executionid,starttime,endtime,-1073450975,0x,SSIS Error Code DTS_E_THREADFAILED. Thread "WorkThread0" has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited. Please let me know what is causing this. Thanks, NR
April 7th, 2011 1:56pm

To me this sounds like a truncation issue. Can you fix it by doing this: Right-click on source and select "show advanced editor", go to the last tab - "input and output properties" then expand the "oledb souce output" -> "output columns" and click on the column [COL1 ?] that generated the error; In the properties of the column on the right side change property "TruncationRowDisposition" value to "RD_IgnoreFailure"?Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 2:34pm

I checked the source and destination on DFT - show advanced editor - input & output properties It shows the same length on both tasks for the col1 . It runs fine if executed from my workstation but from server agent job calling the ssis - it errors out with the above message.
April 7th, 2011 5:44pm

This might help : http://dwhanalytics.wordpress.com/2010/05/07/ssis-csv-import-status-code-4-error-column-is-truncated/ Thanks http://dwhanalytics.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2011 7:19am

Hi, The job failed with the same truncation issues. This time I opened the package on the server itself (instead of my workstation) and I did see the warning icon. Checked the field length in the Data Flow tab and both the input and output columns had the length 44 for the column "col1" I just clicked on the Refresh button and ran the package - it completed successfully. Re-deployed the package back to the server. Thanks for all the help. - NR
April 8th, 2011 11:52am

Which means while you were running this package on your development machine you were connecting to a different database than the deployed package, this explains the validation error and thus the fix was in refreshing the metadata to adjust to the new column size.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
April 8th, 2011 2:28pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics