MSSQL 2022 - SSISDB ETL returning "...failed with the following error: "An error occurred in the Microsoft .NET Framework while trying to load assembly id 65536. "

Fred Bartley 0 Reputation points
2024-12-26T16:44:24.62+00:00

Full error from the Integration Catalog in question:

SQL Load Queue List into Object:Error: Executing the query "EXEC [My PROC name]" failed with the following 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 'clr, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)

System.IO.FileLoadException:

at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)

at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)

at System.Reflection.Assembly.Load(String assemblyString)

". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

I have done the following: - Changed DB owner to 'SA'

  • Set CLR Enabled
  • Set CLR Security On
  • Set SSISDB Trustworthy on and off
 ALTER DATABASE SSISDB SET TRUSTWORTHY ON;
 EXEC sp_changedbowner 'sa'  
 GO  
 EXEC sp_configure advanced,1 'clr enabled'  
 GO  
 EXEC sp_configure 'clr strict security';  
 GO  
 EXEC sp_configure 'clr strict security' , '1';  
 RECONFIGURE;  
 GO 
--Also enabled the assymetric key for the user ---##MS_SQLEnableSystemAssemblyLoadingUser##   
--SQL:   
     USE MASTER  
     CREATE ASYMMETRIC KEY MS_SQLEnableSystemAssemblyLoadingKey FROM EXECUTABLE FILE = 'C:\Program Files\Microsoft SQL Server\160\DTS\Binn\ISServerExec.exe'  
     CREATE LOGIN MS_SQLEnableSystemAssemblyLoadingUser FROM ASYMMETRIC KEY MS_SQLEnableSystemAssemblyLoadingKey  
     GRANT UNSAFE ASSEMBLY TO ##MS_SQLEnableSystemAssemblyLoadingUser##

  
--In addition, I made sure the Securable UNSAFE was granted with user 'sa' and other users. Seems I can't get past this error.
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,222 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,619 questions
{count} votes

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.