Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » Data Warehousing » Integration Services » The column "Column 2" cannot be processed...
Add to briefcase
12 posts, Page 1 of 2
12»»

The column "Column 2" cannot be processed because more than one code page (65001 and 1252) are specified for it. Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
winston Smith
Posted Friday, August 21, 2009 9:17 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, May 17, 2013 2:59 AM
Points: 827, Visits: 1,517
I get this error if i try to import a tab delimited flat file to a table in sql server.

The column "Column 2" cannot be processed because more than one code page (65001 and 1252) are specified for it.


I have set the "alwaysUseDefaultCodePage" property of the destination connection to True.
There is no such property for the flatfile source connection.

I have gotten around it by setting the codepage property of the OLEDB connection to 65001 but i dont know what this did or why it worked.

What does this error mean?
Is it a bug or is it serving a usefull purpose?
Why did my "workaround" work?



Thanks!
Post #775159
madhukeshwark
Posted Saturday, August 22, 2009 12:10 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, December 30, 2012 11:54 PM
Points: 19, Visits: 79
Hi Winston Smith !
As per my understanding, u have set the flat file connection manager configuration setting correctly. You need to specify the delimiter in the connection manager.
Pls let me know which tasks u r using to achieve this task?
Post #775510
winston Smith
Posted Saturday, August 22, 2009 4:58 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, May 17, 2013 2:59 AM
Points: 827, Visits: 1,517
madhukeshwark (8/22/2009)
Hi Winston Smith !
As per my understanding, u have set the flat file connection manager configuration setting correctly. You need to specify the delimiter in the connection manager.
Pls let me know which tasks u r using to achieve this task?


Hi.

I think you misread my post. I didnt change anything for the flatfile connection as the flag was not present. what i changed was:

1. I have set the "alwaysUseDefaultCodePage" property of the destination OLEDB connection to True.
2. I have set the codepage property of the OLEDB connection to 65001

This allowed the package to work but I would really like to understand what a code page is, why this error presents its self so often, if its a bug and if not, what usefullness does it provide.

Regarding what im using, i simply have a flat file connection feeding to a OLEDB destination connection
Post #775544
BaldingLoopMan
Posted Wednesday, May 12, 2010 1:32 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, December 05, 2012 7:23 AM
Points: 304, Visits: 457
i had the same issue except i was conn to sql server.

i had to delete everything and rebuild it with my flat file code page to = 1252 and it worked.
Post #920823
v-hymag
Posted Monday, May 17, 2010 4:18 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, July 07, 2010 4:38 AM
Points: 56, Visits: 39
Hi;

CODE PAGE BACKGROUND:-

I was working with one SSIS package and created a second package that would use some of the configured controls from the first package. By copying controls from the first package to the second package, I ended up with several controls using the page number from its source. So, when I attempted to debug the second package I received the following message:

The "column1" cannot be processed because more than one code page (1252 and 65001) are specified for it.

In short the first SSIS package had a page number of 1252 and the second SSIS package had a page number of 65001. So all of the controls copied from the first package retained their 1252 page number references.



SOLUTION 1:-
1. I edited the metadata code-behind by replacing all 1252 page number references with 65001.
2:- setting "AlwaysUseDefaultCodePage" property of oledb source as true.

Summary:-
While building SSIS packages graphically within VS 2005 design mode, a metadata code behind page is modified to reflect the graphical controls used within the designer. It is here within the metadata code-behind where controls reference their parent page with a page number. Each SSIS package has a code-behind with a default page number. Different SSIS packages should have different page numbers.
Post #922787
vgv8
Posted Sunday, June 06, 2010 5:22 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 25, 2010 4:25 AM
Points: 15, Visits: 87
having same in the same SSIS package

I also would like to understand where is the phantom codepage for and why
Post #933214
vgv8
Posted Monday, June 28, 2010 11:44 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 25, 2010 4:25 AM
Points: 15, Visits: 87
IMO, this is obvious and very annoying bug
which I reported
https://connect.microsoft.com/SQLServer/feedback/details/566945/bids-inserts-fanthom-code-page-s-into-ssis-2008-r2-components-irrelevant-to-format-locales-codepages-of-data-and-software-used-blocking-the-ssis-tasks

No, response whatsoever in 2 weeks
I guess from my previous experiences with ingenuous "conveniences" in MS products,
it will be closed "by design"
http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/f6717d6d-3ffb-426f-8a82-96e1e3d131d8
Post #944393
koushaljha
Posted Wednesday, August 22, 2012 3:42 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 23, 2012 6:05 AM
Points: 2, Visits: 6
I faced this issue , and just delete the existing source file (.csv) connection and re-create it. it get fresh code page 1252.
Post #1348280
koushaljha
Posted Wednesday, August 22, 2012 3:44 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 23, 2012 6:05 AM
Points: 2, Visits: 6
[b]I faced this issue , and just delete the existing source file (.csv) connection and re-create it. it get fresh code page 1252.
Post #1348281
Michael G
Posted Tuesday, January 22, 2013 5:59 AM
SSC-Enthusiastic

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

Group: General Forum Members
Last Login: Thursday, May 09, 2013 6:24 AM
Points: 184, Visits: 120
I've just encountered this bug too.
What caused it was I edited a package by deleting the Excel source and replaced it with a .rpt flat file source... then all hell broke loose

The only way I managed to fix it (after an hour or so of browsing between the source and target's trees and messing with the codepages) was to delete my Derived Column and OLE DB Destination.

I'm about to press run, wish me luck.

Michael Gilchrist
Database Specialist
http://www.michael-gilchrist.com
There are 10 types of people in the world, those who understand binary and those that don't.
Post #1409981
« Prev Topic | Next Topic »

Add to briefcase
12 posts, Page 1 of 2
12»»

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.