Assembly could not be installed because existing policy would keep it from being used

Question

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?

Hello, have you solved the question? If yes, could you share the solution? — Boogier, Jun 23 '14 at 08:00
@Boogier Unfortunately we were forced to resort to an NTLM WebClient request; using `System.Security.Principal.WindowsIdentity`, `WindowsImpersonationContext`, and the `CredentialCache`. If you are interested I can post sample code here. — Joshua Drake, Jun 23 '14 at 16:41

score 3 · Answer 1 · edited May 23 '17 at 12:18

3

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

edited May 23 '17 at 12:18

Community

1
1

answered Sep 18 '13 at 11:04

steoleary

8,362
2
28
45

I'll have to try out the accepted answer later this week. The registry key is not set on the system in question. – Joshua Drake Sep 19 '13 at 12:51
Unfortunately the sqlservr.exe.config suggestion also failed to allow the dlls to be registered. – Joshua Drake Sep 27 '13 at 13:40

Assembly could not be installed because existing policy would keep it from being used

1 Answers1