KB2938476 - FIX: Errors when you use export/import data wizard to move data in SQL Server

Applies To
SQL Server 2008 R2 Service Pack 2 SQL Server 2008 R2 Datacenter SQL Server 2008 R2 Enterprise SQL Server 2008 R2 Standard SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Standard SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

Assume that you have applied cumulative update package 2 (CU2) or later to Microsoft SQL Server 2008 R2 Service Pack 2 (SP2). When you try to move data in SQL Server Management Studio (SSMS) by using export/import data wizard with "Write a query to specify the data to transfer" option, you receive the following error:

Note

Found 1 unknown column type conversion(s)
You are only allowed to save the package

further Details
[Source Information]
ource Location : <ServerName>
Source Provider : <DataBaseName>
Table: [Query]
Column: <ColumnName>
Column Type: <TypeID>
SSIS Type: (Type unknown ...)
Mapping file (to SSIS type): <FilePath>⁠\MSSQLToSSIS10.XML

[Destination Information]
Destination Location : <ServerName>
Destination Provider : SQLNCLI10
able: [dbo].[Query]
Column: <ColumnName>
Column Type: <TypeID>
SSIS Type: (Type unknown ...)
Mapping file (to SSIS type): <FilePath>⁠\MSSQLToSSIS10.XML

[Conversion Steps]
Conversion unknown ...
SSIS conversion file: <FilePath>⁠\DtwTypeConversion.xml

Note The issue also occurs in SQL Server 2012 and SQL Server 2014.

Resolution

The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 2 for SQL Server 2014 /en-us/help/2967546

Cumulative Update 10 for SQL Server 2012 SP1 /en-us/help/2954099

Cumulative Update 12 for SQL Server 2008 R2 SP2 /en-us/help/2938478

About cumulative updates for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

      

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.