Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Custom DLL deployment Expand / Collapse
Author
Message
Posted Sunday, January 27, 2013 2:12 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 4:38 AM
Points: 39, Visits: 22
Hi,

I have two SSIS packages which uses the Custom DLL in a script task. This Custom DLL has code which is not only used by ssis, but various other components in our project. Everytime when the DLL updated for any change in other components(not in the code used by the ssis tasks), the package been failed in the production with the following error.
"Cannot create user component class. Make sure there is one class marked with SSISScriptComponentEntryPointAttribute in your script. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserScriptInstance() End "

Note:whenever the DLL changes, I ensured to register the latest in GAC of the production environment.

If I open the script tasks and rebuild the code, it resolves the issue without changing any setting or one line of code.
Is this the SSIS necessity to rebuild the tasks if DLL changes or am I missing any setting? Please help me on this.

ENV used : SSIS 2008 and .NET 3.5 framework
Note: I tried setting dealy validation to true also, but no help.


Thanks,
Post #1412111
Posted Sunday, January 27, 2013 9:23 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:48 AM
Points: 7,094, Visits: 12,581
When you promote the new assembly into the GAC is it using the same version and public key?

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1412136
Posted Tuesday, January 29, 2013 7:55 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 4:38 AM
Points: 39, Visits: 22
I found the Key file used to build my custom assembly was different in production region.
But I later updated the package using the new build assembly from prod. My assumption is, so after that(package updated with new assembly from prod), whenever the custom assembly rebuild, the package should not fail, as we rebuild already with the assembly from prod.
Would that not be the case? please advise me. I am bit confused how things are with.
Post #1413419
Posted Tuesday, January 29, 2013 9:18 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:48 AM
Points: 7,094, Visits: 12,581
mramaswamy (1/29/2013)
I found the Key file used to build my custom assembly was different in production region.
But I later updated the package using the new build assembly from prod. My assumption is, so after that(package updated with new assembly from prod), whenever the custom assembly rebuild, the package should not fail, as we rebuild already with the assembly from prod.
Would that not be the case? please advise me. I am bit confused how things are with.

As I understand it as long as you keep the version number, name and sign it with the same key the SSIS package will not notice if you redeploy a custom assembly that it references to the GAC.


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1413426
Posted Tuesday, January 29, 2013 9:49 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 4:38 AM
Points: 39, Visits: 22
Thanks for the information. I wil try this way and keep posted.
Post #1413433
Posted Wednesday, February 27, 2013 1:50 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, April 23, 2014 4:38 AM
Points: 39, Visits: 22
Hi,

Thanks for your help. Key files was the issue, I used same in all environments, which resolved the issue.
Post #1424396
Posted Wednesday, February 27, 2013 9:02 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:48 AM
Points: 7,094, Visits: 12,581
Excellent! That is how the GAC is supposed to work. Happy to know you got it sorted. Thanks for posting back.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1424586
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse