SQLIS Wiki
User: Guest
Login
Wiki Home Wiki Home
Topic Index Topic Index
Edit Edit
Print View Print View
What's New What's New
Search
RSS 2.0 RSS 2.0
Recent Topics
0xC0047067 0xC0047067
0xC004704E 0xC004704E
0xC0047029 0xC0047029
0xC0047047 0xC0047047
SftpTask SftpTask
FtpsConnection FtpsConnection
0xC0047036 0xC0047036
0xC004706A 0xC004706A
NativeTransactions NativeTransactions
0xC0047040 0xC0047040

Current Version:
2/9/2009 8:55 AM Yipi
0xC0047067
.

The "%1!s!" failed to cache the component metadata object and returned error code 0x%2!8.8X!. A component failed its put_ComponentMetaData call.

Constant DTS_E_INDIVIDUALPUTCOMPONENTMETADATAFAILED
HRESULT 0xC0047067
Error -1073450905
Code 28775
Facility Pipeline (DTS_FACILITY_PIPELINE)
Severity Error (DTS_SEVERITY_ERROR)

Community Notes

This error is often seen when a component has not been installed on the current machine. An example of this error is shown below,

where a package that uses the Checksum Transformation, built on a second machine, has been copies to a new machine without the component.

This is error is for Data Flow components only, and can be rectified by installed the required component on the local machine.

 Validation error. Data Flow Task: DTS.Pipeline: 
  The component metadata for "component "Checksum Transformation" (270)" could not be upgraded to the newer version of the component. 
  The PerformUpgrade method failed.


 Error loading MyPackage.dtsx: 
  The "component "Checksum Transformation" (270)" failed to cache the component metadata object and returned error code 0x80131600.


 Error loading MyPackage.dtsx: 
  Component "component "Checksum Transformation" (270)" could not be created and returned error code 0xC0047067. 
  Make sure that the component is registered correctly.

==> well, I got the same error, but the component is being built and tested on the same machine... There must be something else as well!

I removed the component from my ssis package and from the toolbox(!), saved the package and closed the ssis package solution.

Then, I rebuilt my SSIS Data flow component, reinstalled and reregistered it (gacutil etc).

In the next step, I reopened my SSIS Package solution, and edited my data flow task. There, I reinserted my (newly registered) task component

into the toolbar and used it from the toolbar to insert it into my data flow task.

Then, I rebuild my package and it worked.

Note This process took me several attempts, but after some trials and errors it worked.

We had SSIS packages created on a development machine that displayed this error (and several others) for every component of our packages when we tried to start them on a test server then a deployment server. All machines had SQL Server 2005 SP3 CU1 installed.

Two things fixed the issue for us:

  • Install and run the SSIS service (I do mean the SQL Server Integration Services service)
  • Re-register the dst.dll file via:
 regsvr32 "%ProgramFiles%\Microsoft SQL Server\90\dts\binn\dts.dll" (NON-CLUSTER)

or

 %windir%\syswow64\regsvr32 "%ProgramFiles%\Microsoft SQL Server\90\dts\binn\dts.dll" (CLUSTER)

This fixed the issue on both servers. The order was not important (we mistakenly did it in different order on both servers and it worked anyway).

Below is a sample of the errors/warnings list seen at run-time (all codes were repeated for every single component of the package):

 Started:  1:53:27 PM
 Warning: 2009-02-09 13:53:44.14
    Code: 0xC0048000
    Source: DFT_Insert_Mapping_Data DFT_Insert_Mapping_Data (DTS.Pipeline)
    Description: The registry key "SOFTWARE\Classes\CLSID\{53A228EE-EBFA-48D6-A1AC-5269E5824A2C}\DTSInfo" cannot be opened.
 End Warning
 Warning: 2009-02-09 13:53:44.14
    Code: 0x8004801E
    Source: DFT_Insert_Mapping_Data DFT_Insert_Mapping_Data (DTS.Pipeline)
    Description: Cannot find the "CurrentVersion" value for component {53A228EE-EBFA-48D6-A1AC-5269E5824A2C}. The CurrentVersion value for the component  cannot be located. This error occurs if the component has not set its registry information to contain a CurrentVersion value in the DTSInfo section. This message occurs during component development, or when the component is used in a package, if the component is not registered properly.
 End Warning
 Error: 2009-02-09 13:53:44.17
    Code: 0xC0047067
    Source: DFT_Insert_Mapping_Data DFT_Insert_Mapping_Data (DTS.Pipeline)
    Description: The "component "XML_SRC_" (1)" failed to cache the component metadata object and returned error code 0x80131600.
 End Error
 Error: 2009-02-09 13:53:44.17
    Code: 0xC004706C
    Source: DFT_Insert_Mapping_Data DFT_Insert_Mapping_Data (DTS.Pipeline)
    Description: Component "component "XML_SRC_" (1)" could not be created and returned error code 0xC0047067. Make sure that the component is registered correctly.
 End Error
 Error: 2009-02-09 13:53:44.17
    Code: 0xC0048021
    Source: DFT_Insert_Mapping_Data DFT_Insert_Mapping_Data (XML_SRC_ [1])
    Description: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Extracts data from an XML data file.;Microsoft Corporation;Microsoft SqlServer v9;  2004 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;1".
 End Error
 Error: 2009-02-09 13:53:44.17
    Code: 0xC004801F
    Source: DFT_Insert_Mapping_Data DFT_Insert_Mapping_Data (DTS.Pipeline)
    Description: The component metadata for "component "XML_SRC_" (1)" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
 End Error

Hope it helps,

Yipi.

Add your experiences and workarounds here. If you have solved this issue, why not help the next person?

PipelineErrorCodes

Copyright © 2001-2005 SQLDTS.com. All Rights Reserved. TermsOfUse, Powered by FlexWiki 1.8.0.1677