“An error occurred in the Microsoft .NET Framework while trying to load assembly id 65675” may occur when moving Acctivate to a new server

You may run into this error message whenever moving Acctivate to a new server.

An error occurred in the Microsoft .NET Framework while trying to load assembly id 65537. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. 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 ‘acctivatesqlfunctions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=3ec1e49bd2ebbb18’ 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)

This message is likely related to permissions to the SQL user account on the new instance.

1. Ensure that SQL Server Management Studio is installed on the server.
2. Login into the new instance (Servername\Acctivate) using a windows user account or a SQL User.
3. Run the following script below FOR EACH DATABASE….

USE <DATABASE>;

EXEC sp_configure 'clr enabled' ,1

GO

USE <DATABASE>

GO

EXEC sp_changedbowner 'sa'

USE <DATABASE>

GO

ALTER DATABASE <DATABASE> SET TRUSTWORTHY ON;

For each result, the output should state “Command(s) completed successfully.”. Once the script is ran for all database, attempt to log into Acctivate again.

Posted in Uncategorized - Last modified on March 27, 2017daniel.stenbro
Still need help?
Search all content on this site, contact support at 817-870-1311, or create a support request.