Getting error
"The version of flat file destination is not compatible with this version of the dataflow"
when trying to execute a SSIS package from the catalog, the package executes well from visual studio. I have tried in catalog to run it both in 32 bit mode and in 64 bit.
the package just executes a stored procedure and exports the result as csv. I don't know what could be happening with it that is giving this "version not compatible" searching for it I found something similar and the recommendation was to delete a section with "version" in it, I did that and I get the same result.
These are the error I'm getting:
╔══════════════╦══════════════╦═════════════════════╦═════════════════════════════════════════════════════════════════════════════════╦═══════════════╦═════════════════════════════════╦═══════════════════════════╗
║ Message Type ║ Action ║ Message ║ Message ║ Message ║ Subcomponent ║ Execution Path ║
║ ║ ║ Time ║ ║ Source Name ║ Name ║ ║
╠══════════════╬══════════════╬═════════════════════╬═════════════════════════════════════════════════════════════════════════════════╬═══════════════╬═════════════════════════════════╬═══════════════════════════╣
║ OnError ║ View Context ║ 4-7-2020 5:05:23 PM ║ Export to Excel:Error: There were errors during ║ Export ║ ║ \Package1\Export to Excel ║
║ ║ ║ ║ task validation. ║ to Excel ║ ║ ║
║ ║ ║ ║ ║ ║ ║ ║
╠══════════════╬══════════════╬═════════════════════╬═════════════════════════════════════════════════════════════════════════════════╬═══════════════╬═════════════════════════════════╬═══════════════════════════╣
║ OnError ║ View Context ║ 4-7-2020 5:05:23 PM ║ Export to Excel:Error: One or more component ║ Export ║ SSIS.Pipeline ║ \Package1\Export to Excel ║
║ ║ ║ ║ failed validation. ║ to Excel ║ ║ ║
║ ║ ║ ║ ║ ║ ║ ║
╠══════════════╬══════════════╬═════════════════════╬═════════════════════════════════════════════════════════════════════════════════╬═══════════════╬═════════════════════════════════╬═══════════════════════════╣
║ OnError ║ View Context ║ 4-7-2020 5:05:23 PM ║ Export to Excel:Error: Flat File Destination ║ Export ║ SSIS.Pipeline ║ \Package1\Export to Excel ║
║ ║ ║ ║ failed validation and returned error code 0xC0048021. ║ to Excel ║ ║ ║
║ ║ ║ ║ ║ ║ ║ ║
╠══════════════╬══════════════╬═════════════════════╬═════════════════════════════════════════════════════════════════════════════════╬═══════════════╬═════════════════════════════════╬═══════════════════════════╣
║ OnError ║ View Context ║ 4-7-2020 5:05:23 PM ║ Export to Excel:Error: The component is ║ Export ║ Flat File Destination [2] ║ \Package1\Export to Excel ║
║ ║ ║ ║ missing, not registered, not upgradeable, or missing required interfaces. The ║ to Excel ║ ║ ║
║ ║ ║ ║ contact information for this component is "Flat File ║ ║ ║ ║
║ ║ ║ ║ Destination;Microsoft Corporation; Microsoft SQL Server; (C) Microsoft ║ ║ ║ ║
║ ║ ║ ║ Corporation; All Rights Reserved; ║ ║ ║ ║
║ ║ ║ ║ http://www.microsoft.com/sql/support;1". ║ ║ ║ ║
║ ║ ║ ║ ║ ║ ║ ║
╠══════════════╬══════════════╬═════════════════════╬═════════════════════════════════════════════════════════════════════════════════╬═══════════════╬═════════════════════════════════╬═══════════════════════════╣
║ OnError ║ View Context ║ 4-7-2020 5:05:23 PM ║ Export to Excel:Error: The version of Flat File ║ Export ║ SSIS.Pipeline ║ \Package1\Export to Excel ║
║ ║ ║ ║ Destination, clsid {0667D728-1E5F-4BB6-863D-B29D3F405706} is not compatible ║ to Excel ║ ║ ║
║ ║ ║ ║ with this version of the DataFlow. ║ ║ ║ ║
║ ║ ║ ║ ║ ║ ║ ║
╠══════════════╬══════════════╬═════════════════════╬═════════════════════════════════════════════════════════════════════════════════╬═══════════════╬═════════════════════════════════╬═══════════════════════════╣
║ OnError ║ View Context ║ 4-7-2020 5:05:23 PM ║ Export to Excel:Error: The version of Flat File ║ Export ║ Export to Excel (SSIS.Pipeline) ║ \Package1\Export to Excel ║
║ ║ ║ ║ Destination is not compatible with this version of the DataFlow. ║ to Excel ║ ║ ║
║ ║ ║ ║ ║ ║ ║ ║
╚══════════════╩══════════════╩═════════════════════╩═════════════════════════════════════════════════════════════════════════════════╩═══════════════╩═════════════════════════════════╩═══════════════════════════╝
please let me know what other information I can add. I have other packages running in the server so SSIS catalog works. and this particular package works from visual studio, but not on the catalog. the component that is failing is a dataflow that has an OLEDB Connection to a flat file destination:
with a basic flat file connection manager:
Update: I found tha tif I do the deploy from visual studio the package works when I execute in SSMS. the problem is that I need to import the package, since it's going to be installed in a third party server not connected with visual studio. I'm trying to replicate this on my computer (server is in my computer) and it works with deploy from VS but not when importing. this is the error that I get when executing the imported file (the table above also shows it):
I fixed this by going to Project Property and change the TargetServerVersion from SQL Server 2019 to 2017
I was encountering a very similar issue whilst upgrading a Visual Studio 2017 package with a TargetServerVersion
of SQL Server 2012 to Visual Studio 2019 and SQL Server 2017.
Other than when we ran the package in the design location from within Visual Studio, we kept getting the error:
The version of flat file destination is not compatible with this version of the dataflow
I resolved the issue by:
TargetServerVersion
to SQL Server 2017ispac
file.If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With