December 5, 2018 at 5:42 am
Hello,
How to resolve this error? I only have the .dtsx file which I opened in Visual Studio SSDT 2017. It did say upgraded successfully.
On running it I am getting the following error for CSV destination.
The version of Flat File Destination is not compatible with this version of the DataFlow
Error: 2018-12-05 12:05:47.67
Code: 0xC0048021
Source: Data Flow Task Flat File Destination [2]
Description: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "Flat File Destination;Microsoft Corporation; Microsoft SqlServer v10;
Many thanks for the help,
Vinay
December 17, 2018 at 12:18 pm
Need a lot more information. Could be any of a number of things. Exactly what version of Visual Studio was the package originally created in? Exactly what version of Visual Studio was used to "convert" the package dtsx file? Have all the latest updates been applied to that latter version of Visual Studio? It might also be a matter of just replacing the Flat File destination and re-configuring it to match the original from a configuration perspective. Unless, you used some kind of VS add-in and perhaps a custom flat-file destination component? Please be a lot more detailed.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
January 10, 2019 at 10:00 am
Steve,
Apologies for the delay in replying. Wasn't actively testing this for sometime.
Basically all the old SSIS packages were created in VS 2008. They all work fine on SQL 2008 R2.
But they fail to execute on SQL 2016 using VS 2017.
Keep getting the same error of component missing in File Destination. It's a simple Query few columns and flat-file (CSV) destination.
All updates are applied on the Windows 2016 server.
As you suggested I also deleted the Destination and the mapping and re-inserted from the components with same column mappings. Re-executed it using DTEXEC /file and the same error.
The only way this works is to re-create a new SSDT package on VS-2017. That works well.
But it means I need to re-create all the old-SSIS packages again. Quite time-consuming.
Thanks,
Vinay
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply