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.
Symptoms
Consider the following scenario:
-
You have a version of SQL Server Integration Services (SSIS) that is earlier than SSIS 2012 installed on your computer.
-
You have an SSIS package that uses the Microsoft Connector for Oracle by Attunity or the Microsoft Connector for Teradata by Attunity.
-
You upgrade to SSIS 2012.
-
You try to open the package.
In this scenario, you receive an error message that resembles the following:
Error 0xc004706c: Dataflow - SSISPackageName: Component "Oracle Source Oracle Source Name, clsid {4CAC6073-BCA7-430E-BD29-68A9F0012C6D}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.Error 0xc0048021: Dataflow - SSISPackageName: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Oracle Source;Microsoft Connector for Oracle by Attunity; Attunity Ltd.; All Rights Reserved; http://www.attunity.com;2".Error 0xc004801f: Dataflow - SSISPackageName: The component metadata for "Oracle Source < Oracle Source Name>" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Cause
This issue occurs because an old GUID is used in the SSIS package.
Resolution
Cumulative update information
Cumulative update package 1 for SQL Server 2012 Service Pack 1
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
2765331 Cumulative update package 1 for SQL Server 2012 Service Pack 1Note 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:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Cumulative update package 3 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 3. 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:
2723749 Cumulative Update 3 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
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Workaround
To work around this issue, find and then replace the old GUID with the new one in the .dtsx package file together with the following mapping. These changes can be done before or after the SSIS packages are upgraded to SQL Server 2012.Oracle Source OLD: {4CAC6073-BCA7-430E-BD29-68A9F0012C6D} NEW: {CB67CD40-126C-4280-912D-2A625DFAFB66} Oracle Destination OLD: {3C2D9CC0-74EE-4f64-98E0-4DD374B92068} NEW: {96F6C478-E5BE-45A4-B39A-055F9787CCD4} Oracle Connection ManagerOLD: {58BD57A5-2572-4e04-8D64-A646AFD434F3} NEW: {577C27D9-1E41-4116-B8AC-1A11E1E4B66D} Teradata SourceOLD: {58664F3B-262F-4E4B-8AD1-E3FA1B504C1E} NEW: {FE2F6C7B-2535-434A-8E03-894F4C01D8B7} Teradata DestinationOLD: {3703B1C2-3155-4905-9D5B-9DDAB8EB8773} NEW: {664D5009-786B-4C11-A507-2BF056EF5F61} Teradata Connection ManagerOLD: {EA88DC41-494C-41FE-9BB2-0B728B46B7B2} NEW: {84B09D80-8309-4CA8-9CEC-E19ACB76F257}
More Information
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
