SSIS package Just fails...not compatible with this version of the DataFlow?

Question

Executed as user: x ...0.00 for 64-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  11:27:08 AM  Error: 2013-01-09 11:27:09.74     Code: 0xC0048020     Source: import file import file (DTS.Pipeline)     Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow.  End Error  Error: 2013-01-09 11:27:09.75     Code: 0xC0048020     Source: import file DTS.Pipeline     Description: The version of component "Flat File Source" (1) is not compatible with this version of the DataFlow.  End Error  Error: 2013-01-09 11:27:09.75     Code: 0xC004706C     Source: import file DTS.Pipeline     Description: Component "component "Data Conversion" (773)" could not be created and returned error code 0x80070005. Make sure that the component is registered correctly.  End Error  Error: 2013-01-09 11:27:09.75     Code: 0xC0048021     Source: import file Flat File Source [1]...  The package execution fa...  The step failed.

I am unsure what i am running into here.... Any ideas?

Answer 1

Are you running on 64bit or 32bit based server? Please check option.

Answer 2

Justin,

Navigate to your data flow and see which component is failing. I guess the issue with the flat file souce component.

Thanks,

---

hsbal

Answer 3

I believe my server is running on 64 bit...

Answer 4

I am not sure it is on that side... I build and run it fine from BIDS. When i am running through ssis i get the error...

Answer 5

I am not sure it is on that side... I build and run it fine from BIDS. When i am running through ssis i get the error...

What is diff between ssis and bids? Both mean same. When you run it locally, you can see which task/component is failing. I guess your configuration for flat file source is incorrect.

Thanks,

---

hsbal

Answer 6

By bids, i mean the visual studio package section. When I debug and build from there it will pull the records into my sql table. Nothing fails or even gives me any warnings. When I go to sql server management studio and sql server Agent and jobs, i cannot get it to run from the job.

Answer 7

Try to choose the option "Use 32 bit runtime" under "Executions options"

when you configure this package in SQL Agent.

Hope this helps.

Answer 8

Try to choose the option "Use 32 bit runtime" under "Executions options"

when you configure this package in SQL Agent.

Hope this helps.

I went ahead and gave that a shot. I received this instead:

"Microsoft (R) SQL Server Execute Package Utility  Version 9.00.5000.00 for 64-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Option "/X86" is not valid.  The command line parameters are invalid.  The step failed."

Answer 9

Did you try to run with DTExec utility?

Answer 10

Did you try to run with DTExec utility?

At this time i have not. i am still a very new to SSIS and my peers just left me hangin...

Answer 11

If I go to the command prompt and run DTExec utility, it will run and update my tables successfully it seems.

Answer 12

Are you trying to import data from text file to Database?

Answer 13

Yeah. Essentially i want to set it up so that a user can drop off a text file and I upload it automatically.

Answer 14

Since you are new, I suggest you to validate your package again few examples - This is all for importing text file data to Database.

http://www.codeproject.com/Articles/155829/SQL-Server-Integration-Services-SSIS-Part-1-Basics

http://decipherinfosys.wordpress.com/2008/07/28/ssis-importing-data-from-a-text-file-using-a-package/

http://www.databasejournal.com/features/mssql/article.php/3832386/Flat-File-Imports-with-SQL-Server-Integration-Services-2008.htm

Answer 15

I had exactly the same error after upgrading my SSIS project from SQL 2008R2 to SQL 2016. 

I compared a new created SSIS package with the old upgraded one:

Old example:

           <component
              refId="Package\DFT - Adecco Analytics Bedrijf\FFD - Bedrijf CSV"
              componentClassID="Microsoft.FlatFileDestination"
              contactInfo="Flat File Destination;Microsoft Corporation; Microsoft SqlServer v10; (C) Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;0"
              description="Flat File Destination"
              localeId="1043"
              name="FFD - Bedrijf CSV"
              version="1">

New:
             <component
                  refId="Package\SC - Export Studytube files\DFT - Export StudyTube_Krachten\Flat File Destination"
                  componentClassID="Microsoft.FlatFileDestination"
                  contactInfo="Flat File Destination;Microsoft Corporation; Microsoft SQL Server; (C) Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;1"
                  description="Flat File Destination"
                  localeId="1043"
                  name="Flat File Destination">

Fix is to remove the version="1">   from the XML. You can easily to this in notepad for example. This worked for me.

Answer 16

Thank you - this worked for me.  How did you ever find this solution?

Answer 17

Thank you.  Life saver.

Is there anyway to stop the Visual Studio editor from putting in the version number?

Answer 18

Just change the target server version to match actual server version.

Project Properties => Configuration Properties => General => Deployment Target Version => TargetServerVersion

Answer 19

Just change the target server version to match actual server version.

Project Properties => Configuration Properties => General => Deployment Target Version => TargetServerVersion