ssis runtime error "TXN_DATA_FEED/DP_TXN_MEASUREMENTS/TXN_MEASUREMENT/TXN_ERROR" has changed. Please re-initialize the metadata for this component and review column mappings.

Answered ssis runtime error "TXN_DATA_FEED/DP_TXN_MEASUREMENTS/TXN_MEASUREMENT/TXN_ERROR" has changed. Please re-initialize the metadata for this component and review column mappings.

  • Friday, August 03, 2012 9:30 PM
     
     

    I have an SSIS package that loads data from an xml file to sql server database. A new xml file is downloaded each time the package runs. I am using XMLSource to get my xml data. When I run the package from a SQL Server Agent Job, I get the following error

       Code: 0xC0209318     Source: Data Flow Task 1 XML Source 1 [1]     Description: The XML schema data type information for "code" on  element "TXN_DATA_FEED/DP_TXN_MEASUREMENTS/TXN_MEASUREMENT/TXN_ERROR" has changed.  Please re-initialize the metadata for this component and review column mappings.  End Error  Error: 2012-08-03 13:32:25.70     Code: 0xC004706B     Source: Data Flow Task 1 SSIS.Pipeline     Description: "component "XML Source 1" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".  End Error  Error: 2012-08-03 13:32:25.70     Code: 0xC004700C     Source: Data Flow Task 1 SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2012-08-03 13:32:25.70     Code: 0xC0024107     Source: Data Flow Task 1      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  1:32:14 PM  Finished: 1:32:25 PM  Elapsed:  11.5 seconds.  The package execution failed.  The step failed.

    How do I reinitialize the metadata automatically within my package?

All Replies

  • Saturday, August 04, 2012 10:05 AM
     
     

    Like the message tells your XML data type in the new file has changed. Since your XSD is generated based on a different file the schema in this file may be a mismatch. Compare the values of node "code" from a working file and the errored file and see whats the difference.

    As a hint: there could be fields which had numeric values during design of the package but now those fields have alphanumeric characters.

    Hope this helps-

  • Thursday, August 09, 2012 1:38 PM
     
     
    Sorry it doesn't quite help because the xsd will change with each new file. How do I deal with there being a new xml file each time I run my package?
  • Friday, August 10, 2012 10:20 PM
     
     Answered

    I figured out that I need to read the xml with a script component instead.

    • Marked As Answer by ErinSue Friday, August 10, 2012 10:20 PM
    •