April 17, 2009 at 2:52 am
I am having difficulties creating an Assembly for a vb.net project I have written.
I am getting the error:
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.
I have been successful in creating this assembly before on this server but i made a small change the the assembly so I deleted the assembly and am now trying to recreate it.
I am not 100% sure that I even need to delete the Assembly within SQL for it to register any changes in the built project since the first Created the Assembly?
My code for the creation of the assembly is as below and i haven't changed it since it previously worked:
USE [NSG_Data]
GO
/****** Object: SqlAssembly [asmFindNearestRoad] Script Date: 16/16/2009 08:32:48 ******/
CREATE ASSEMBLY [asmFindNearestRoad]
AUTHORIZATION [dbo]
FROM '\\###\###\###\NSG Data\VB Projects\FindNearestRoad\obj\Release\FindNearestRoad.dll'
WITH PERMISSION_SET = EXTERNAL_ACCESS
EXEC sp_configure 'clr enabled', 1
GO
RECONFIGURE
GO
n.b. # represents varying numbers of characters in my UNC path!
I have searched the internet for the cause of this error and from my research i have found that the code 0x8007000e is a to do with a lack of virtual memory available to the CLR.
One proposed solution which i have found is to use the -g switch in the Startup Parameter of the SQL Service (MSSQLSERVER) which i have tried both -g512 and -g1024 and stopped and restarted the service.
Neither values have been either sufficient or a solution.
I have also read that it might be a problem with SP2 for SQL as per
http://forums.asp.net/t/1098345.aspx
I am running SQL2005 with SP2 on Windows Server 2003.
I was hoping that someone else might know of another reason for this problem. I appreciate any assistance.
April 17, 2009 at 3:05 am
matthewr (4/17/2009)
I am having difficulties creating an Assembly for a vb.net project I have written.I am getting the error:
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.
I have been successful in creating this assembly before on this server but i made a small change the the assembly so I deleted the assembly and am now trying to recreate it.
I am not 100% sure that I even need to delete the Assembly within SQL for it to register any changes in the built project since the first Created the Assembly?
My code for the creation of the assembly is as below and i haven't changed it since it previously worked:
USE [NSG_Data]
GO
/****** Object: SqlAssembly [asmFindNearestRoad] Script Date: 16/16/2009 08:32:48 ******/
CREATE ASSEMBLY [asmFindNearestRoad]
AUTHORIZATION [dbo]
FROM '\\###\###\###\NSG Data\VB Projects\FindNearestRoad\obj\Release\FindNearestRoad.dll'
WITH PERMISSION_SET = EXTERNAL_ACCESS
EXEC sp_configure 'clr enabled', 1
GO
RECONFIGURE
GO
n.b. # represents varying numbers of characters in my UNC path!
I have searched the internet for the cause of this error and from my research i have found that the code 0x8007000e is a to do with a lack of virtual memory available to the CLR.
One proposed solution which i have found is to use the -g switch in the Startup Parameter of the SQL Service (MSSQLSERVER) which i have tried both -g512 and -g1024 and stopped and restarted the service.
Neither values have been either sufficient or a solution.
I have also read that it might be a problem with SP2 for SQL as per
http://forums.asp.net/t/1098345.aspx
I am running SQL2005 with SP2 on Windows Server 2003.
I was hoping that someone else might know of another reason for this problem. I appreciate any assistance.
do the following way, this may help to your problem.
1. Close all connections and re-Start the SQL Server
2. Again Create the Assembly with new one.
3. Test: Access this assembly thro' T-SQL.
try it.
April 17, 2009 at 3:12 am
Thanks for your post, I have since posting read this:
It mentions that restarting the service, as we did, isn't sufficient to apply the change to the startup parameter.
I was told by our DBA that the server was restarted recently for another issue since we first made the change, but not since I increased the value to -g1024.
Obviously it is a production server and i can't just go and restart it, but I shall try and arrange for it to be restarted over the weekend and see what success we have.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply