Microsoft distributes Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release.
Consider the following scenario:
You migrate a Microsoft SQL Server Integration Services (SSIS) package to SQL Server 2012.
The SSIS package was created by using the Japanese edition of Business Intelligence Development Studio (BIDS) from an earlier version of SQL Server. For example, the SSIS package was created by using the Japanese edition of BIDS 2005.
The SSIS package contains a Bulk Insert task.
You try to open the Bulk Insert task by using SQL Server 2012 SQL Server Data Tools (SSDT).
In this scenario, you cannot open the package. Additionally, you receive an error message that resembles the following.
"Cannot display the editor for this task.
The key specified does not exist in the directory. (mscorlib)"
When this issue occurs, you cannot run the upgraded SSIS package in SQL Server 2012.
Note This error message was translated from Japanese to English.
To resolve this issue, apply the following cumulative update on the computer on which SSDT is used and on the computer on which you run the SSIS package.
Cumulative update information
SQL Server 2012
The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
2703275 Cumulative update package 2 for SQL Server 2012Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2692828 The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.