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

Anonymous
2024-12-24T19:58:15+00:00

Full error from the Integration Catalog in question:
SQL Load Queue List into Object:Error: Executing the query "EXEC [insert 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

SQL:
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.

Windows Server High availability Clustering and high availability

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous
    2024-12-25T01:11:27+00:00

    Hello,

    Thank you for posting in Microsoft Support Community. Based on the description, I understand your question is related to SQL Server. Since SQL Server is not currently supported in the Microsoft Support Community, it is recommended to repost your question in Microsoft Q&A.

    https://learn.microsoft.com/en-us/answers/questions/

    Click the "Ask a Question" button in the upper right corner to post your question and select the "SQL Server" tag.

    Thank you for your understanding and support. If you have any question or concern, please feel free to let us know.

    0 comments No comments
  2. Anonymous
    2024-12-26T16:45:48+00:00
    0 comments No comments