6

I'm using the following command to try and enable the CLR on a SQL Server 2008 instance

EXEC sp_configure 'clr enabled', 1 GO RECONFIGURE GO

But I still get the following error

Execution of .NET Framework code is disabled. Set "clr enabled" configuration option and restart the server

Do I need to do anything else?

Improve this question
15
  • "restart the server". Is your server a 32bit server? Commented Feb 2, 2016 at 13:38
  • Yes I tried that but still no dice Commented Feb 2, 2016 at 13:39
  • Then you are doing something incorrect. That's all there is to it. Commented Feb 2, 2016 at 13:40
  • 1
    It's trying to do this when it fails:- CREATE ASSEMBLY [FileObject] Commented Feb 2, 2016 at 13:47
  • 1
    Light weight pooling is not enabled Commented Feb 2, 2016 at 14:16

3 Answers 3

Reset to default
5

To review what has been checked and attempted so far:

  1. EXEC sp_configure 'clr enabled', 1; has been executed.

  2. RECONFIGURE; has been executed.

  3. The server has been restarted. This should only be necessary on WOW64 servers.

  4. Running EXEC sp_configure 'clr enabled'; shows a 1 for run_value.

  5. Running EXEC sp_configure 'lightweight pooling'; shows a 0 for run_value.

  6. state property in sys.dm_clr_properties has a value of "Locked CLR version with mscoree", meaning:

    The Locked CLR version with mscoree state may be seen where the hosted CLR is not being used and, thus, it has not yet been initialized. The hosted CLR is initialized the first time a DDL statement (such as CREATE ASSEMBLY (Transact-SQL)) or a managed database object is executed.

Additional things to try / check:

  1. Make sure that .NET Framework 2.0 and 3.5 SP1 are installed
  2. Make sure that .NET Framework patches have been applied through Windows Update
  3. Possibly make sure, in Control Panel\Programs\Programs and Features that "Microsoft SQL Server System CLR Types" is installed
  4. Check your authentication type. If set to "both", try change to "Windows Only", restarting the SQL Server service, and see if that helps. Not a good long-term solution, but might point in a direction.
  5. What account is the MSSQLSERVER service logging on as? There are some reports that "Network Service" or "NT AUTHORITY\Network Service" might have issues and that Local System account might be preferred.
  6. ??
Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

I'm giving up on this. It's not essential for this server and it's taking up too much of my time. Thanks for your help anyway
Installing .Net 2.0 and 3.5 resolved this for me - thanks!
@KevinPope Glad this info help! Thanks for posting what worked for you to help narrow down for others :-)
1

Try

EXEC sp_configure 'clr enabled', 1 go RECONFIGURE go EXEC sp_configure 'clr enabled' go

Also

To enable CLR integration, you must have ALTER SETTINGS server level permission, which is implicitly held by members of the sysadmin and serveradmin fixed server roles.

Improve this answer

Comments

0

Are you sure you have advanced options enabled?

sp_configure 'show advanced options', 1; GO RECONFIGURE; GO sp_configure 'clr enabled', 1; GO RECONFIGURE; GO
Improve this answer

5 Comments

Yes, I have advanced options enabled
What is your assembly .NET CLR version? Is it the same as in results of: select * from sys.dm_clr_properties
CLR enabled is not an advanced option.
I just got some old code of mine and it was there. I checked now and on MSDN it's also described like that: msdn.microsoft.com/pl-pl/library/ms131048(v=sql.100).aspx. Finall I also double checked now and I can execute it without advanced options enabling, which prooves you're right it's not needed.
Another question is, what account is it running on? If it's a network service, maybe you could try changing it to 'Local System' for a moment and see if it's the same

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.