Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Possible causes of "Failed to initialize the Common Language Runtime (CLR)" when using SQL CLR
Article ID: 2003681 - View products that this article applies to.
When using SQL CLR stored procedures, user defined functions, user defined data types, or user defined aggregates, you many notice one or more of the following error messages being logged in the SQL server error log when running on a 32 bit instance of either SQL Server 2005 or 2008
Error message 1
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x8007000e.
Error message 2
Msg 6511, Level 16, State 20, Line 1
Error message 3
Msg 6512, Level 16, State 27, Line 2
Error message 4
Msg 6513, Level 16, State 27, Line 1
Error message 5
6513: Failed to initialize the Common Language Runtime (CLR) v2.0.50727 due to memory pressure.
Error message 6
Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x80131522.
Additionally, you may see the above error messages with SQL Server 2008 features which use SQL CLR internally, like DMF (Declarative Management Framework) and spatial data types.
The error message and HRESULT of the CLR exception can be used to identify the probable cause and likely resolution of the exception
For error messages 1,2,4 and 5 from the above list, the most probable cause of these errors is SQL CLR encountering memory pressure. For further information on how to resolve these errors refer to the following article:
For error messages 3 and 6, one probable resolution is to reinstall.NET Framework 2.0. To obtain the .NET Framework 2.0, visit the following Microsoft Web site:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2003681 - Last Review: March 10, 2010 - Revision: 3.0