SSIS Data Flow Task error - The version of the Flat File destination is not compatible with this version of the dataflow.

WMB853 6

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

Yitzhak Khabinsky 25,721 Reputation points

2020-10-15T15:02:00.78+00:00
Hi Bill,

Please edit your post and share the following:

Visual Studio version.

SSDT or Integration Services Projects Extension (for VS2019) version.

Targeted SSIS run-time version on the server.
Yitzhak Khabinsky 25,721 Reputation points

2020-10-15T15:59:13.757+00:00

Please share one more piece of information:
SSIS run-time version on the server via SELECT @@VERSION; in SSMS.
WMB853 6 Reputation points

2020-10-15T17:07:15.557+00:00

SELECT @@VERSION returns

Microsoft SQL Server 2016 (SP2-CU8) (KB4505830) - 13.0.5426.0 (X64) Jul 21 2019 21:16:47 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)
Yitzhak Khabinsky 25,721 Reputation points

2020-10-15T17:10:37.067+00:00

I would recommend to update the server up to the latest SP2 CU15:
Microsoft SQL Server 2016 Builds
WMB853 6 Reputation points

2020-10-15T17:22:49.083+00:00

Obviously that's not something I can do right now but do you know if there is definitely a fix for this error in one of those updates?

Thanks
Yitzhak Khabinsky 25,721 Reputation points

2020-10-15T18:09:13.277+00:00
The package in question is working on you dev. machine.

The same package is not working on the server. That's why it is worth it to update the server.
WMB853 6 Reputation points

2020-10-15T19:33:40.563+00:00

I think it's more due to the fact that it runs from Visual Studio manually than once it's imported into Integration Services on the server. Other people seem to have the same issue.
Chu, Connor 1 Reputation point

2021-12-07T19:01:56.09+00:00

Hi all,

I am still receiving the same error when trying to execute a package that exports data to a csv table. Works fine when running manually, but will fail when run via a Server Agent Job. Picture shows the error code I am getting. I tried running it via admin proxy with Operating System rights. I set the task, Server Agent process, and job all to run via the same Windows authentication. Not sure what is wrong. Please help!
Murray Brown 1 Reputation point

2022-03-22T21:47:19.673+00:00

I got this error when deploying a SSIS project to a server. Not sure if it's the same issue but in case it helps others, here it is ...

I can deploy a SSIS project to a server's Integration Services Catalogs from Visual Studio on a workstation then create a SQL job on that server to run the SSIS package. The package uses Excel reports and text files. All works well.

SQL Server version: 2016
Visual Studio version: 2015

However deploying the same SSIS project from a previously exported .ispac file either via Windows GUI steps or via a TSQL script I get this error when the SSIS package runs: "The version of (report name) is not compatible with this version of the data flow"

My fix was to avoid renaming the .ispac file. If I rename that file then deploy using it I get the above error. If I don't rename it from the original file name all works well. I guess there is a reference to the file name in that compiled file or a system stored procedure somewhere. I haven't looked for it yet.

Hope this helps others.

8 answers

Barrett, Preston G 1 Reputation point

2022-01-21T18:22:55.217+00:00

So I am getting this same error: My TargetServerVersion is SQL Server 2019 and Run64BitRunTime is set to False. However, I am using Visual Studion 2017. What else am I missing on this?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Jovy 1 Reputation point

2022-03-15T14:17:23.047+00:00

I have SQL Server 2016 and using Visual Studio Community 2019.

My TargetServerVersion is set to SQL Server 2016 and I and Run64BitRunTime is set to True but I am still getting the same error when running from SQL job. SSIS package works just fine when running inside Visual Studio.

Any thoughts please?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Mike Murphy 0 Reputation points

2024-05-02T18:11:24.7366667+00:00

Not sure what is going on here, however, i did do an upgrade to visual studio 2019.

Pulled back the package, that was targetServerVersion of SQL Server 2016. redeployed the package, for some reason, it was pushed back to targetServerVersion of SQL Server 2022.

Question for Microsoft, why does this TargetServerVersion change happen?

This has not been the first time!!!
Please sign in to rate this answer.
Mike Murphy 0 Reputation points

2024-05-02T18:12:14.9+00:00

DO I HAVE TO CHECK THIS EVERYTIME?
Sign in to comment

Share via

SSIS Data Flow Task error - The version of the Flat File destination is not compatible with this version of the dataflow.

8 answers