Ideas on resolving error -- "VS_NEEDSNEWMETADATA".

  • Mark F-428640

    Hall of Fame

    Points: 3596

    Hi I am running a large dtsx package and in a data flow task I am getting the following error in the validation of the OLE DB DESTINATION object. Here is the specific error:

    [DTS.Pipeline] Error: "component "My_Data reader destination" (337)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".

    Not sure where I should look from here I have looked at my source data and the data types and sizes are compatible with the destination.

    I welcome any suggestions.

  • pduplessis-723389

    SSChampion

    Points: 10539

    This normally occurs if there has been a change to your schema, not to stress, just double click on your input and output and it should resolve itself

  • Mark F-428640

    Hall of Fame

    Points: 3596

    Thanks,

  • Sanjay Rohra

    Ten Centuries

    Points: 1109

    I was facing the similar issue. In my case, I was creating the SQL query on run time using script task, storing it in a variable. The default value that I had provided to my variable , one of the column names had the first character in Upper case. But in the script task, while designing the query, the same column had the first character in Lower case. On changing the latter to Upper case solved my problem. Quite strange, but it worked for me.

    HTH

    Sanjay.

  • rsingh.sql

    SSC Eights!

    Points: 814

    I am getting the same error message, I have an OLE DB source that gets a set of columns from a variable that executes a given stored proc.

    The data flow task can be individually executed successfully, but if I run the job or the package, it is giving me the error "Description: "component "OLE DB Source" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA" ".

    Any advise is appreciated.

    Things I have tried:

    1: remove OLE DB source and destinations and re create it.

    2. remove the entire data flow task itself and recreate it.

  • SQListic

    SSCertifiable

    Points: 6904

    Help on this please, I am having similar issue.

  • Phil Parkin

    SSC Guru

    Points: 243261

    SQListic (10/21/2013)


    Help on this please, I am having similar issue.

    What have you tried?

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

  • herladygeekedness

    SSCertifiable

    Points: 5798

    try setting DelayValidation to True.

  • l.bissett

    Valued Member

    Points: 53

    I have a project that has been running fine for a long time. Recently however I had to change the password to my AS400 ODBC connection string. I had a problem doing this so I ended up deleting the connection configuration XML file and creating it again. I think this cause a problem in my package. Now I am getting a metadata error. Is there something else I have to do once I change the connection?

  • Satu

    SSC-Addicted

    Points: 433

    I have always managed to get rid of metadata errors simply by running the project in BIDS step by step. When all previous steps have been executed, open the input and output steps, accept any (sensible) notifications on changes needed, and press OK. BIDS will most of the time detect what has changed in data source.

    Using a stored procedure as a data source, though, might be a different story altogether.

  • Jay Hammer

    SSC Enthusiast

    Points: 188

    I am receiving a similar error in an SSIS package that I am writing. The package connects to my MS SQL Server 2005 SP 4 database and executes a Stored Procedure (with the SET FMTONLY OFF command included) as the data source of my Data Flow Task, and is able to properly read the column definitions and even preview the output data. When I try to test the step, however, I receive the VS_NEEDSNEWMETADATA error along with an error message that states "The external metadata column collection is out of synchronization with the data source columns." and that each one of my SP output columns needs to be removed from the external metadata column collection.

    I have verified my OLE DB connection, edited my OLE DB Source, Data Conversion, and Flat File Destination objects, and previewed the source data. BIDS is not suggesting any changes to any of my objects, so I am at a loss as to the next steps to resolve this issue.

    Please help me.

  • Phil Parkin

    SSC Guru

    Points: 243261

    ahammer 40362 (4/20/2015)


    I am receiving a similar error in an SSIS package that I am writing. The package connects to my MS SQL Server 2005 SP 4 database and executes a Stored Procedure (with the SET FMTONLY OFF command included) as the data source of my Data Flow Task, and is able to properly read the column definitions and even preview the output data. When I try to test the step, however, I receive the VS_NEEDSNEWMETADATA error along with an error message that states "The external metadata column collection is out of synchronization with the data source columns." and that each one of my SP output columns needs to be removed from the external metadata column collection.

    I have verified my OLE DB connection, edited my OLE DB Source, Data Conversion, and Flat File Destination objects, and previewed the source data. BIDS is not suggesting any changes to any of my objects, so I am at a loss as to the next steps to resolve this issue.

    Please help me.

    Are you using SET FMTONLY because your proc returns data from a temp table?

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

  • Jay Hammer

    SSC Enthusiast

    Points: 188

    Yes, I am using a TEMP table in my SP to gather the data, and then I return the contents of the TEMP table.

  • Phil Parkin

    SSC Guru

    Points: 243261

    Rather than the FMTONLY way, you could try this method instead. Maybe it will help:

    http://stackoverflow.com/questions/1579476/using-temp-tables-in-ssis

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

  • Jay Hammer

    SSC Enthusiast

    Points: 188

    Phil,

    I tried the "IF 1=0" method and there was no change in the results of executing the Data Flow task (i.e. I am still getting the same error).

    Thanks for the suggestion, but I am still in the same boat. 🙁

Viewing 15 posts - 1 through 15 (of 20 total)

You must be logged in to reply to this topic. Login to reply