question

BalaJagannathan-7426 avatar image
0 Votes"
BalaJagannathan-7426 asked ZoeHui-MSFT commented

SSIS Package 2019 runtime error on Server

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-servicessql-server-migrationsql-server-migration-assistant
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

ZoeHui-MSFT avatar image
1 Vote"
ZoeHui-MSFT answered ZoeHui-MSFT commented

Hi @BalaJagannathan-7426,

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



· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you Zoe for the response.
Yes I see the DLL Microsoft.SqlServer.ManagedDTS was missing on QA Server, so I got this DLL from working server (DEV) and moved to QA and registered using gacutil.exe but that did not work, also tried after server reboot and the issue still persists, greatly appreciate you suggestion.

0 Votes 0 ·
ZoeHui-MSFT avatar image ZoeHui-MSFT BalaJagannathan-7426 ·

Hi @BalaJagannathan-7426,
Please ensure that that Integration Services is installed in the QA machine. Go to Services (Start -> Run -> Services.msc -> OK) and locate the SQL Server Integration Services service and verify that it is running.

In addition, have you tried to re-build the package and re-deploy it, check if this is helpful.

1 Vote 1 ·