SSIS Package is not loading in VS2019 - The Argument type "System.__ComObject' cannot be converted into parameter type "Microsoft.SqlServer.Dts.Pipleline.Wrapper.IDTSPipeline100'

Anupriya Athalye 1 Reputation point
2023-03-27T11:19:51.5566667+00:00

Hi All,

We are trying to migrate SSIS 2014 packages to SSIS 2019. We are using Package Deployment Model only. Under one solution we have multiple Projects and under one projects we have 4-5 packages.

I selected one project, and in properties I changed to Target server version from 2014 to 2019. It converted all 5 packages under that project successfully.

4 out of 5 packages are opening without any issue. But I am not able to open 1 package, firstly it takes lot of time to open the package and then it fails to open it with the following error message -

WhatsApp Image 2023-03-27 at 16.45.53

This package has script tasks, which is using some dlls also. Can anybody suggest what is the issue.

Our aim is to just lift and shift the packages from 2014 to 2019 without breaking the functionality. We are not aiming to use any of the new features.

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,704 questions
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
568 questions
Developer technologies | Visual Studio | Debugging
Developer technologies | Visual Studio | Other
SQL Server | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ZoeHui-MSFT 41,491 Reputation points
    2023-03-28T02:13:18.4366667+00:00

    Hi @Anupriya Athalye,

    This is a well-known issue. Script tasks require recompilation after migrating to 2019 as they hold onto old .net references.

    In addition, as said here, Script Task and Script Component scripts that explicitly reference ADODB.dll may not upgrade or run on machines without SQL Server Management Studio or SQL Server Data Tools (SSDT) installed. In order to upgrade these Script Task or Script Component scripts, it is recommended that you remove the dependency on ADODB.dll. Ado.Net is the recommended alternative for managed code such as VB and C# scripts.

    You may have a double check.

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.