SSIS package fails on SSIS server with error file or assembly not found, Microsoft.Azue.Storage.Common 11.1.3

Rajani Nandula 0 Reputation points
2024-04-14T05:33:23.1633333+00:00

We have SSIS packages working on prem and using file destination task and target server is SQL 2014. We are migrating these to SSIS , SQL server 2016 on Azure VM. We are converting the packages to use flexible file destination to write to adls gen2 account. I have installed Azure ssis feature pack 2016 on development machine and Azure VM. The package failed on development machine with the error mentioned above and I got the assembly by creating a console app and adding the assembly to references and adding to cache using gacutil. Then the package completes successfully on my machine but it fails to execute on Azure VM after deployment with the same error. I tried to add the assembly to cache on Azure VM using powers shell script but still fails with the same error. I am using VS 2015 on my development machine and targetserverversion= sqlderver2016.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,757 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,456 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ZoeHui-MSFT 33,126 Reputation points
    2024-04-15T08:22:26.8666667+00:00

    Hi @Rajani Nandula,

    The TLS version used by Azure Feature Pack follows system .NET Framework settings. To use TLS 1.2, add a REG_DWORD value named SchUseStrongCrypto with data 1 under the following two registry keys.

    1. HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319
    2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319

    You may have a double check.

    In addition, you may try to reinstall the Azure feature pack.

    If these all do not work, please check SSIS execution logs for more detailed error messages.

    Regards,

    Zoe Hui


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

    1 person found this answer helpful.