August 17, 2011 at 4:42 am
Hi,
I am trying to run an SSIS package via a job. However, I get the below error:
Started: 11:18:08 Error: 2011-08-17 11:18:18.26 Code: 0xC004706B Source: Data Flow Task DTS.Pipeline Description: "component "OLE DB Source" (1)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".
I am using data flow task and within that in OLEDB source, there are some fields which have been removed from the table and are represented with asterisk (*).
In the destination (OLEDB destination), the corresponding fields still exist in the table and I have mapped the asterisk marked fields from the source to the existing fields in destination. Could I be getting an error due to this ?
Thanks,
Paul
August 18, 2011 at 1:44 pm
VS_NEEDSNEWMETADATA shows up when the underlying data behind one of the tasks changes. In your case, if the data that is being obtained from the database has changed, then your data source will fail with the VS_NEEDSNEWMETADATA error.
The solution is to just right-click on the data source, and then select edit. It will automatically prompt you with a question asking if it should fix the meta data. Choosing "yes" generally solves the problems.
Once you change the meta data from the data source, the remaining tasks also need to be updated. If a column which was present before does not exist anymore, and the tasks require that column, then they'll need to be updated. If not, then generally you just need to update the meta data and everything will be fine.
August 22, 2011 at 4:23 am
kramaswamy (8/18/2011)
VS_NEEDSNEWMETADATA shows up when the underlying data behind one of the tasks changes. In your case, if the data that is being obtained from the database has changed, then your data source will fail with the VS_NEEDSNEWMETADATA error.The solution is to just right-click on the data source, and then select edit. It will automatically prompt you with a question asking if it should fix the meta data. Choosing "yes" generally solves the problems.
Once you change the meta data from the data source, the remaining tasks also need to be updated. If a column which was present before does not exist anymore, and the tasks require that column, then they'll need to be updated. If not, then generally you just need to update the meta data and everything will be fine.
I tried what you mentioned but I am still getting the same error. Do you know another way to resove this ?
August 22, 2011 at 7:06 am
honestly, the fastest solution will probably be to just delete and re-create each element which is throwing an error. you might be able to find another solution, but i doubt you'd do so in less time than it would otherwise take
May 15, 2017 at 8:10 am
kramaswamy's solution worked for me.... just double click all your OLE DB sources within your data flow task and it should work. I wasn't prompted to fix the metadata, however it fixed my problem and I was able to execute my data flow task.
February 17, 2019 at 11:58 pm
I have encountered this problem aswell, im not sure why my solution works but i guess i post it here, maybe it helps someone.
The reason i got this error was because i was deploying a singular SSIS packet. This resulted in the error on execution in a job.
The solution was deploying the complete project. I cant explain why though, the only thing i know is that it solved my VS_NEEDSNEWMETADATA issue.
I want to be the very best
Like no one ever was
September 25, 2019 at 10:29 am
I encountered the same issue and in my case it was the source component failed while reading from Azure Blob storage. Took couple of hours to figure out and finally resolve this. Even though the column names were all same w.r.t previous file and successful load this time around the case of few columns' were changed and so is the error "VS_NEEDSNEWMETADATA". After I got the case of column names corrected the file loaded successfully. Hope this helps.
May 4, 2021 at 3:26 pm
Revisar, si es un paquete SSIS con una conexion ODBC.
Review ODBC Source
Properties (ODBC); ValidateExternalMetada >> FALSE
😉
May 4, 2021 at 3:49 pm
So this is a super-old thread to bump, but ironically, I'm working on SSIS packages again after several years, and this exact problem has been coming up again.
I realise now that my previous post wasn't quite accurate. It's not the data that has changed - rather, it's the schema.
Also, with respect to the solution, one thing that causes problems is when the data types of a column have changed - for example, if you had a column that was CHAR(10) and you had changed it into a VARCHAR(10). SSIS will detect that the metadata has changed on the database, however, within the package, it won't necessarily properly update the metadata to match.
The brute-force solution I'd mentioned earlier (delete the source and re-add it) will work; but the simpler solution is to just remove the offending column, close the data source, and then add it back in.
With respect to @rodrigo's comment - setting ValidateExternalMetadata will prevent the errors from appearing while you're working on the task, however, you're likely to just be delaying the inevitable, as when you execute it, it'll likely throw the exception at runtime instead.
April 11, 2022 at 2:29 pm
Rodrigo.atomo's suggestion worked for me. Tranks
May 25, 2022 at 5:18 am
This was removed by the editor as SPAM
August 23, 2022 at 8:41 am
This was removed by the editor as SPAM
September 6, 2022 at 7:02 am
This was removed by the editor as SPAM
September 23, 2022 at 3:11 am
This was removed by the editor as SPAM
Viewing 15 posts - 1 through 15 (of 20 total)
You must be logged in to reply to this topic. Login to reply