SSIS Package 2019 runtime error on Server

Bala Jagannathan 1 Reputation point
2021-10-29T00:41:46.18+00:00

We have the SSIS package upgraded from SQL Server 2012 to 2019, they are all working on DEV environment but getting below on QA, I would appreciate for any help on this issue.

The following error(s) occurred:System.IO.FileLoadException: Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Microsoft.SqlServer.ManagedDTS, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Microsoft.SqlServer.ManagedDTS, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

at Scs.InterfaceRunner.ExecuteProcess.ExecuteSSIS(String strPkgName, String strFile)
at Scs.InterfaceRunner.ExecuteProcess.ExportFile(String strFilePath)
at Scs.InterfaceRunner.InterfaceRunner.RunProcess(String strFilemask)

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,438 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.
485 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ZoeHui-MSFT 32,081 Reputation points
    2021-10-29T07:48:31.157+00:00

    Hi @Bala Jagannathan ,

    Please check if the Microsoft.SqlServer.ManagedDTS assembly is in the folder.

    Location: C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS

    Have a compare of the DEV environment and QA in the folder.

    Copy the matched dll to the folder for a try.

    Regards,

    Zoe


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    Hot issues October

    1 person found this answer helpful.