Post reply

Custom DLL deployment

  • January 27, 2013 at 2:12 am

    #269739

    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,

  • January 27, 2013 at 9:23 am

    #1581378

    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

  • January 29, 2013 at 7:55 pm

    #1582448

    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.

  • January 29, 2013 at 9:18 pm

    #1582453

    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

  • January 29, 2013 at 9:49 pm

    #1582458

    Thanks for the information. I wil try this way and keep posted.

  • February 27, 2013 at 1:50 am

    #1591441

    Hi,

    Thanks for your help. Key files was the issue, I used same in all environments, which resolved the issue. 🙂

  • February 27, 2013 at 9:02 am

    #1591596

    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

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply