Failed to initialize the Common Language Runtime from SQL Server 2008 R2

0

Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80131022. You may fix the problem and try again later.

I get the above error.

Microsoft's Solution

It tells me I have some sort of memory problem pressure but does not provide a solution. I have determined that SQL Server 2008 R2 uses CLR 2 still, so I have tried reinstalling .net Framework 3.5 (which includes .Net Framework 2) but that is not working on my machine which is Windows 10. I have 15.9 GB available of RAM. My SQL Server is Microsoft SQL Server 2008 R2 (SP3) - 10.50.6220.0 (X64).

I am at a loss as to how to solve this problem. I do not think it is a memory issue with. The code that causes the error is pointing to a linked server but it passes the connection test. I should add that I posted a similar question in.StackExchange Database Administrators-How to resolve Geospatial Data over linked server causing error??

.net
sql-server
sql-server-2008-r2
asked on Stack Overflow Jul 26, 2016 by Darren • edited Apr 13, 2017 by Community

1 Answer

0

SQL Server: How to check if CLR is enabled? <<-- check out this stack overflow answer

Here is how to change it.

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

I So Rarely activate the CLR surface on SQL Instances due to many application design issues that it brings up. It literally triggers me. (And I don't like triggers).

https://msdn.microsoft.com/en-us/library/ms131048(v=sql.105).aspx

I think you can do this via the SQL Server install setup.

answered on Stack Overflow Jul 26, 2016 by Sql Surfer • edited May 23, 2017 by Community

User contributions licensed under CC BY-SA 3.0