|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 8:46 AM
Points: 2,750,
Visits: 1,410
|
|
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?
LinkedIn Profile
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 8:26 AM
Points: 6,737,
Visits: 11,791
|
|
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
Believe you can and you're halfway there. --Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 8:46 AM
Points: 2,750,
Visits: 1,410
|
|
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.
LinkedIn Profile
|
|
|
|