March 2, 2012 at 3:58 pm
I've been trying to install a SAFE assembly which is supplied as a block of hexadecimal bytes.
I know categorically that it is safe and it installs absolutely fine under local instances of SQL Server, both 2005 & 2008.
On our shared servers I get the dreaded 6218 error. The only thing I can think of is that these servers us a domain account for the MSSQLSERVER service and that this account does not have suitable permissions to access the .NET framework. The service account is NOT a local administrator.
Does anyone know of any specific permissions that are necessary to register assemblies?
I've heard the term "blessed" assemblies but I'm not sure if this is the same thing as the GAC. Do I need specific permissions to reference these assemblies?
March 5, 2012 at 10:23 am
Which version of the FW are you targeting? Check your SQLCLR assembly's references to make sure those exist on the server.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 5, 2012 at 11:21 am
I'm trying to install SQLSharp on a SQL2005 server patched up to build 5000.
I can do it provided I mark all the assemblies as UNSAFE.
Installing on a SQL2008 server presents no problems with the assemblies in the default install of SAFE.
The SQL Server service account is in the local admins group. Probably shouldn't be, but that's another story! Anyway my initial thought was that it was some form of permissions issue but I'm clutching at straws.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply