Reputation: 2746
Assembly could not be installed because existing policy would keep it from being used
While attempting to load an earlier version of a .NET assembly, indicated as possible in a comment on an answer to MSSQL 2012 creating CLR triggers for WCF fails. I receive the titular error message.
Despite searching for additional information on the error itself, ensuring that 3.5 was installed in Windows Features, investigating useLegacyV2RuntimeActivationPolicy and more, I have been unable to determine how to enable previous versions of .NET assemblies to execute in SQL Server 2012 on Server 2012.
Does anyone know what is required to allow this execution?
Upvotes: 1
Views: 12152
Answers (1)
Reputation: 9278
Have a look at the following SO post and see if that is applicable to your issue:
SQLCLR using the wrong version of the .NET Framework
Upvotes: 4
Related Questions
- Could not load file or assembly 'Microsoft.SqlServer.Types, Version=12.0.0.0, Culture=neutral, PublicKeyToken=myKey' or one of its dependencies.
- SQL Server 2012 create assembly failed - invalid attribute
- How to resolve failed assembly verification when installing assembly into SQL Server
- Permissions needed to exceute an assembly in SQL Server 2014
- MSSQL load assembly error
- Could not load file or assembly 'EntityFramework.SqlServer' or one of its dependencies. The parameter is incorrect
- Assembly uses a dll which has a higher version than referenced assembly after installing SQL Server 2014
- SQL Server 2012 CLR Error creating assembly
- Error when adding assembly to SQL Server 2012
- Error running Sql Assembly