Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

error :Column data type DT_STR is not supported by the PipelineBuffer class. Expand / Collapse
Author
Message
Posted Thursday, September 20, 2012 2:08 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 5, 2014 9:35 PM
Points: 119, Visits: 240
I'm moving some data from sql server table to shaepoint list.
I'm on sql server 2008 r2
The input columns from sql serer table shows DT_STR and the Avalabe dest(sharepoint) list was showing DT_WSTR
and when i ran the job it complained of DT_WSTR so i changed the columns it to DT_STR
and now getting error.

Error: 0xC0047062 at Data Flow Task, SharePoint List Destination 1 [10095]: Microsoft.SqlServer.Dts.Pipeline.UnsupportedBufferDataTypeException: Column data type DT_STR is not supported by the PipelineBuffer class.

The messy thing it doesn't actually tell you the colum you have problem with.Even if i look at the SSIS logging
Any ideas?

Post #1361780
Posted Thursday, September 20, 2012 2:13 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 2:20 AM
Points: 5,231, Visits: 5,106
Have you tried to use a data conversion task instead of just changing the column types?



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1361782
Posted Thursday, September 20, 2012 4:40 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 5, 2014 9:35 PM
Points: 119, Visits: 240
Thanks
But are you saying I should just use data conversion for every column?
If I knew the column causing the error .yes
Cheers
Post #1361863
Posted Thursday, September 20, 2012 4:48 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 2:20 AM
Points: 5,231, Visits: 5,106
If the source is Non-Unicode and the destination is Unicode it is best to stick a data conversion task in to convert the data from Non-Uni to Uni (or vice-versa) for every column which violates the Non-Uni to Unicode mapping.



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1361870
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse