I was facing the same issue, My SSDT is 17 version and Server is 16. So i changed the Target version to 16 as below
it resolved my issue.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am trying to edit an SSIS package and getting the error "The version of the Flat File destination is not compatible with this version of the dataflow." when trying to run it from a SQL Agent Job or when performing a validation on the SSIS package from Integration Services Catalogs. If I run it from Visual Studio, it runs fine.
After the above error, during validation of the SSIS package, I also see an error saying the clsid is not compatible. {44152846-e5a6-4edb-8b8e-7072209a7662}
I have seen other posts with people having the same issue - they say to make sure the package is configured for TargetServerVersion 2016 which is the version we are using. I did that and it didn't make a difference. Still getting the error with the Flat File task.
Visual Studio version. 2015 14.0.25431.01 Update 3
SSDT or Integration Services Projects Extension (for VS2019) version. SSDT 2015 14.0.61712.050
Targeted SSIS run-time version on the server. TargetServerVersion is SQL Server 2016
Any help is GREATLY appreciated.
Thanks,
Bill
I was facing the same issue, My SSDT is 17 version and Server is 16. So i changed the Target version to 16 as below
it resolved my issue.
The solution was to remove the "version="1" as explained here:
"Fix is to remove the version="1"> from the dtsx XML. You can easily do this in notepad for example. This worked for me."
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0cff32ea-3e9e-43b3-be7f-73c6b26a8029/ssis-package-just-failsnot-compatible-with-this-version-of-the-dataflow?forum=sqlintegrationservices
Hi @WMB853 ,
Please set the Delay Validation as True in SSIS package.
Please choose 64-bit runtime when executing packages in agent job or SSISDB Catalog.
Best Regards,
Mona
So this is the craziest work around I have seen yet. I can get my SSIS package to validate and run on the server as long as I import the dtsx file back into Integration Services FROM THE SERVER. If I import it using SSMS on my workstation, it will not run, with the issue I originally posted.
I also went to another workstation and connected with SSMS, imported the dtsx file to the server, and it works fine there as well. It only fails if I import it to SSIS using my workstation.
SO it's something just in the import process that is causing the issue. The package itself that is created on my workstation is fine. Can someone tell me why this is happening?
That is great!!! my problem is also resolved.