March 31, 2011 at 7:56 am
I get this error message when i run this...
USE [WT]
CREATE ASSEMBLY [ERPConnect40.dll]
authorization dbo
FROM '\\sr-agd-wt\Dev\ERPConnect40.dll'
WITH PERMISSION_SET = UNSAFE
CREATE ASSEMBLY for assembly 'ERPConnect40' failed because assembly 'ERPConnect40' failed verification. Check if the referenced assemblies are up-to-date and trusted (for external_access or unsafe) to execute in the database. CLR Verifier error messages if any will follow this message
any ideas how i can successfully execute it?
March 31, 2011 at 8:57 am
did you sign the assembly? Does the assembly really need to be unsafe? You will probably have to set the database as trustworthy if so.
The probability of survival is inversely proportional to the angle of arrival.
March 31, 2011 at 8:59 am
no i didnt sign it, is that in the signing tab? and if so what strong name key file will i give it?
I've set the db to trustworthy and set to safe
March 31, 2011 at 9:02 am
in fact to sign that it is for the clr, this if for a third party dll i need to reference
March 31, 2011 at 9:11 am
read this: http://support.microsoft.com/kb/302340
The probability of survival is inversely proportional to the angle of arrival.
March 31, 2011 at 9:12 am
im also trying with a ERPConnect35 version running same sql statements for VS2008 and i get this...
Assembly 'ERPConnect35' references assembly 'system.windows.forms, version=2.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089.', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: 2(The system cannot find the file specified.)). Please load the referenced assembly into the current database and retry your request.
do i need to create assembly for system.windows.forms.dll?
March 31, 2011 at 9:29 am
It appears the other assembly reference the other assembly version 2.0 We don't don;t know if it is specifically needing that version (probably referring to .NET 2.0) or it can't find any version assembly of that namespace.
Make sure you have .NET 3.5 installed on that server and that any and all applicable service paks are installed. If you are still having the issue you will have to locate that version of the assembly and put it on the server.
The probability of survival is inversely proportional to the angle of arrival.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy