September 4, 2009 at 5:18 am
hello,
I created an import package in Sql server 2005 that gets the data from db400 database.when i ran it the first time it succeeded but when i run it from the Integration Services i get this error:
Error: 2009-09-04 13:01:29.40
Code: 0xC0202009
Source: Data Flow Task Source - Query [1]
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
End Error
Error: 2009-09-04 13:01:29.76
Code: 0xC004706B
Source: Data Flow Task DTS.Pipeline
Description: "component "Source - Query" (1)" failed validation and returned validation status "VS_ISBROKEN".
End Error
Error: 2009-09-04 13:01:29.76
Code: 0xC004700C
Source: Data Flow Task DTS.Pipeline
Description: One or more component failed validation.
End Error
Error: 2009-09-04 13:01:29.76
Code: 0xC0024107
Source: Data Flow Task
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
i can not even run this from the SQL Server Business Intelligence Development Studio, so if i create a data task in there it also ends with the same error.
can you help me on solving this issue.
thank you.
October 1, 2009 at 12:12 pm
Hi,
I got same kind of problem any help?
October 1, 2009 at 12:37 pm
From http://msdn.microsoft.com/en-us/library/ms135954.aspx:
The VS_ISBROKEN value indicates that the component has an error that can be rectified by editing the component in the designer. The error is typically caused by a custom property or a required connection that is not specified or is set incorrectly.
December 29, 2010 at 2:53 am
brahma-324514 (10/1/2009)
Hi,I got same kind of problem any help?
me too got same issue. but i have resolved this issue by adding another one data flow on the ssis package,then copy and paste the source,destination of old data flow into the new data flow.finaly delete the old dataflow on the ssis and run the ssis pakcage. this way helped to resolve issue.
April 25, 2014 at 10:50 am
I got same kind of problem while I was running my packages through "Start without Debugging".
Then I run my packages with debugging and I resolve that error.
Thanks:-)
Viresh
--------------------------------------------------------------------------
“ The future belongs to those who are virile, to whom it is a pleasure to live, to create, to whet their intelligence on that of the others. ”
— Sir Henri Deterding
December 14, 2015 at 11:03 am
I found that this was due to trying to insert an identity into a field set as the primary key. This is locked by default, all you need to do is go back and click the Edit mappings button, and select the check-box for identity insert. You will need to do this for each table.
Good luck, hope this helps.
May 3, 2016 at 12:11 pm
I encountered this error this morning on an SSIS ETL package that had not changed, the source Excel file had not changed, and the target SQL Server table had not changed. It was failing in both production and development. The only thing that HAD changed was that we upgraded the SQL Server environments to SP3. I suspect that this had somehow disturbed the metadata.
I opened the package in development, opened and saved every step, and then ran it. It worked fine. I then deployed the refreshed package. If failed until I opened (didn’t change) and closed the ODBC environment variable. Then it worked in production.
Good luck!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply