Error
An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. The server may be running out of resources, or the assembly may not be trusted. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly ‘microsoft.sqlserver.integrationservices.server, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
System.IO.FileLoadException:…
Cause
When the backup of SSISDB from one SQL Server is restored on another SQL Server and creating an SSISB object on the target SQL Server Integration Services Catalog, you may get this error.
Solution
While the nature of the solution will depend significantly on the SQL Server versions, you can try the solutions below to resolve the issue.
Solution 1. Run the script below on target SSISDB.
USE [SSISDB]
EXEC sp_configure 'clr enabled', 1
RECONFIGURE
ALTER DATABASE SSISDB SET TRUSTWORTHY ON;
EXEC sp_changedbowner 'sa'
Solution 2. Recreate SSISDB in target SQL Server (Recommended).
Delete SSISDB (Integration Services Catalog) from the target SQL Server and create a new SSISDB in the target SQL Server. Once the SSISDB is created, migrate your SSISDB objects from source SSISDB to target. You can use the SSIS Catalog Migration Wizard to bulk-migrate SSIS objects with just a few clicks.
See more
Kunal Rathi
With over a decade of experience in data engineering and analytics, I've assisted countless clients in gaining valuable insights from their data. As a dedicated supporter of Data, Cloud and DevOps, I'm excited to connect with individuals who share my passion for this field. If my work resonates with you, we can talk and collaborate.
I am always interested in new challenges so if you need consulting help, reach me at kunalrathi55@gmail.com.