Failed to Initialize CLR Errors (CLR) v2.0.50727 with HRESULT 0x8007000e

This was running fine for two months and yestday we had to do a reboot. We then tried to execute some of our CLR functions and are now getting the below error? What can I do to check that all is ok?

Msg 6511, Level 16, State 82, Line 2

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

Have you tried to perform a repair install both on the framework and sql server ?
|||No, we need to figure out why its not working first.|||

The problem is due to not enough *virtual* memory available. This happens more often on high end 32 bit machines. Note that the issue is with virtual memory, so adding more physical memory will not help. In fact, it just makes the situation worse. Try to initialize SQLCLR immediately after you reboot SQL Server (e.g., by doing "drop assembly noexist"). If that doesn't fix the issue, you may need to start the server with -g to reserve enough memory for SQLCLR.

Could you post your machine configurations (physical RAM, num of processors, processor architecture and OS)? That will give us more information to identify the exact problem.

Xiaowei Jiang

|||

I am having a similar problem, but is actually with not manage code it is instead with procedure. I tried to post this message before, but it was deleted by the moderator for having a duplicate post.

during search I could not find any duplicate post that was related to store procedure. I don't know where Mr. moderator found the duplicated post that could have helped me.

Anywhy Here is the store procedure that is causing the CLR error. This store procedure which does a bulk insert to a session table from a XML file. This store procedure used to work fine until couple of month ago and now all of the sudden it stopped working. Whenever this procedure is executed I get following error:

Msg 6511, Level 16, State 82, Procedure up_XNetSessionBulkInsert, Line 42

Failed to initialize the Common Language Runtime (CLR) v2.0.50727 with HRESULT 0x8007000e. You may fix the problem and try again later. I also tested same procedure on the development sql server and it works fine. the settings on the production and development are same.I was wondering if any of you have a solution for it. Here is the procedure which causes error.

dbo.up_SessionBulkInsert '<sessions><s id="6" val="45465465" len="9" /></sessions>'

ALTER

PROCEDURE [dbo].[up_SessionBulkInsert]

(

@.sessionXml

text

)

AS

SET

NOCOUNT ON

declare

@.handle int

exec

sp_xml_preparedocument @.handle output, @.sessionXml

INSERT

INTO SessionTb

(

sessionID

,session

,length

)

SELECT

sessionID

,dbo.udf_DecodeBase64StringToBinary(session) as RawBytes -- Base64-decode to byte[] before we insert.

,length

FROM

OpenXml(@.handle, '/sessions/s', 1)

WITH

(

sessionID

varchar(88) '@.id'

,session varchar(max) '@.val' -- This value should be a base64-encoded string

,length int '@.len'

)

select

@.@.rowcount

exec

sp_xml_removedocument @.handle

SET

NOCOUNT OFF|||

Hi,

I get the same error. I'm trying to deploy a CLR assembly and running this script in sql server 2005 on a server running on Windows server 2003

CREATE ASSEMBLY CLRUtilities

FROM 'C:\CLRUtilities\bin\CLRUtilities.dll'

WITH PERMISSION_SET = SAFE;

GO

and running this this throws me this error:

Msg 6511, Level 16, State 82, Line 1

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

Not sure what to do next. Perhaps, something I need to do in the server configuration or sql server configuration? I already enabled the CLR using

USE master;

EXEC sp_configure 'clr enabled', 1;

RECONFIGURE;

GO

|||

Could you try to register the same assembly when the server just started? Let me know what happens.

thanks

Xiaowei