SSIS 2014 Custom Component: "The component metadata could not be upgraded to the newer version of the component."

Question

I recently upgraded my set of custom data flow components to use the SQL 2014 SDK as we are upgrading to SQL Server 2014 RTM.  The only change I made to my custom components was to change the references to the following DLLs from version 11.0 to version
12.0:
Microsoft.SqlServer.DTSPipelineWrap
Microsoft.SQLServer.DTSRuntimeWrap
Microsoft.SQLServer.ManagedDTS
Microsoft.SqlServer.PipelineHost
After rebuilding my assembly, adding it to the GAC, and placing it in the appropriate directory structure (the 120\DTS\PipelineComponents directory for both the x86 and x64 versions), my components no longer display in the SSIS toolbox in SSDT.  In
addition, whether loading up my packages in SSDT or executing them via the SSIS catalog (in SQL 2014), I get the series of error messages below.  I do have a PerformUpgrade method implemented in my packages that has worked successfully through previous
component upgrades.  I also found this seemingly relevant thread (Custom
SSIS Connection Manager error message in SSIS 2014 (RTM): The connection manager '' is not properly installed on this computer.) and tried modifying the extensions.xml script, but I was unsuccessful with this approach (though I could have done so
incorrectly).
Validation error. DFT Process Changes: DFT Process Changes: The component metadata for "xxx, clsid {874F7595-FB5F-40FF-96AF-FBFF8250E3EF}" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Error loading xxx.dtsx: The "xxx" failed to cache the component metadata object and returned error code 0x80131600.
Error loading xxx.dtsx: Component xxx, clsid {874F7595-FB5F-40FF-96AF-FBFF8250E3EF} failed to initialize due to error 0xC0047067 "The "%1" failed to cache the component metadata object and returned error code 0x%2!8.8X!.".
Error loading xxx.dtsx: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
Error loading xxx.dtsx: The component metadata for "xxx" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Validation error. DFT Process Changes SSIS.Pipeline: The component metadata for "xxx, clsid {874F7595-FB5F-40FF-96AF-FBFF8250E3EF}" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Thanks in advance,
Ben

Answer 1

Hi Ben,
Please also update the reference to the SSIS assembly Microsoft.SqlServer.Dts.Design located in C:\Program Files (x86)\Microsoft SQL Server\120\SDK\Assemblies folder to the version 12.0.0.0. Besides, rename IDTSxxxx110 objects to IDTSxxxx120.
It may also be the factor that the custom mapping file is not created correctly. You can make a copy of the built-in mapping.xml.sample file, rename its extension to XML, and then edit its <ExtensionMapping> attribute:
<ExtensionMapping tag="mycustom extension"
oldAssemblyStrongName="MyCustomAssembly.MyCustomTask, MyCustomAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"
newAssemblyStrongName="MyCustomAssembly.MyCustomTask, MyCustomAssembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
Then, we need to upgrade the packages, and SSIS will read all the XML mapping files placed in this directory during upgrade.
References (although the blogs are written for SSIS 2008 by Matt, we can still refer to them for SSIS 2014):
http://blogs.msdn.com/b/mattm/archive/2008/02/01/custom-extensions-in-sql-server-2008.aspx 
http://blogs.msdn.com/b/mattm/archive/2007/06/05/katmai-custom-components-and-upgrade.aspx 
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support