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 12»»

SSIS 2008 Script Component error Expand / Collapse
Author
Message
Posted Tuesday, May 12, 2009 11:21 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, May 25, 2009 11:10 AM
Points: 25, Visits: 105
Hi,

I'm using Script component in SSIS 2008. This is the error I received when I'm done writing the script.
Microsoft.SqlServer.Dts.Pipeline.CannotCreateUserComponentException: Cannot create user component class. Make sure there is one class marked with SSISScriptComponentEntryPointAttribute in your script. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserComponent().

Any idea what this error means and how can I resolve this error?

Thanks
Post #715670
Posted Sunday, September 13, 2009 4:38 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, June 13, 2013 5:24 PM
Points: 310, Visits: 294
did you find a resolution? i am having same issue and cannot find
ANYTHING to help!
Post #787085
Posted Monday, September 14, 2009 4:34 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 6:50 AM
Points: 2,719, Visits: 1,065
unikhath (5/12/2009)
Hi,

I'm using Script component in SSIS 2008. This is the error I received when I'm done writing the script.
Microsoft.SqlServer.Dts.Pipeline.CannotCreateUserComponentException: Cannot create user component class. Make sure there is one class marked with SSISScriptComponentEntryPointAttribute in your script. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserComponent().

Any idea what this error means and how can I resolve this error?

Thanks


Ok...

can I ask a few questions first.

is this a new SSIS Package created specifically in 2008, or did it come from sql 2005, or is it a converted DTS to SSIS package.

Did you do any editing of the package outside of BIDS, ie, did you use notepad for any changes.

You could save the script you haev written, remove the script component, re-save the package, add the script component back in, and try it again.

Not sure if this will help you but...

In SQL Server 2008, the version-specific interface names have changed from ending with a "90" to a "100." For scripts and custom code that use these interfaces, code must be changed to use these new "100" interfaces as opposed to the "90" interfaces, and upgrades of script tasks and components do not automatically search and replace instances of "90" interface usage in custom-written code; this must be done manually.

IDTSConnectionManager90 -> IDTSConnectionManager100
IDTSComponentMetadata90 -> IDTSComponentMetadata100



--------------------------------------------------------------------------------------
Recommended Articles on How to help us help you and
solve commonly asked questions

Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden
Managing Transaction Logs by Gail Shaw
How to post Performance problems by Gail Shaw
Help, my database is corrupt. Now what? by Gail Shaw
Post #787306
Posted Monday, September 14, 2009 6:04 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, June 13, 2013 5:24 PM
Points: 310, Visits: 294
I have a new 2008 pkg, added script component , wrote some
vb code and voila there was the error message when i tried to
run the pkg. I tried adding a new script component and added
my code back in but same thing happened.
very frustrated! in 2005 never had this issue.
is there a line of vb code i need to insert into the script
to make this work properly?
Post #787363
Posted Monday, September 14, 2009 8:03 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 6:50 AM
Points: 2,719, Visits: 1,065
tiffanyjanetblack (9/14/2009)
I have a new 2008 pkg, added script component , wrote some
vb code and voila there was the error message when i tried to
run the pkg. I tried adding a new script component and added
my code back in but same thing happened.
very frustrated! in 2005 never had this issue.
is there a line of vb code i need to insert into the script
to make this work properly?


tell you what, can you post the code that you are trying to run in the script. If it is database centric, can you remove that and get it to do something basic. like display 'hello world' within a dialogue box.

silly question but you are writing VB.net code and not standard visual basic? and you have the scriptlanguage set to Microsoft Visual Basic .NET


--------------------------------------------------------------------------------------
Recommended Articles on How to help us help you and
solve commonly asked questions

Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden
Managing Transaction Logs by Gail Shaw
How to post Performance problems by Gail Shaw
Help, my database is corrupt. Now what? by Gail Shaw
Post #787484
Posted Monday, September 14, 2009 8:28 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, June 13, 2013 5:24 PM
Points: 310, Visits: 294
got it fixed....

the wacky error was really not telling me the actual issue, which was that
I had a column in my input twice. dont ask, because I dont know :)

so i fixed that up and then the error disappeared.

but yes, am writing .net code.

One thing that I think might help any future folk who get this
wacky error (and assumming its a new SSIS 2008 pkg) is that they
need to open the script and Build (from Build Menu) the script -
which will tell the REAL error. I never did this before with 2005...

and the stuff I found on google DID say to open the script and "make sure it builds" but only in reference to when they are upgrading 2005 to 2008
packages - which I was not doing and so I did not try that.
Post #787502
Posted Tuesday, January 11, 2011 10:22 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, May 07, 2012 2:48 PM
Points: 11, Visits: 105
Thanks, SSC, that was very helpful. I did as you said and clicked on Build from within the script itself, and the "real" problem was that I had a "For" without a matching "Next". Otherwise, I might have been struggling with this all day!!!
Post #1046009
Posted Monday, August 08, 2011 8:54 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, December 04, 2012 8:16 AM
Points: 121, Visits: 245
I saw the same error if you had syntax error in the script component. I'll treat this like a generic error applicable to many unrelated issues unless some one clarifies to the contrary.

Rajib Bahar
http://www.rajib-bahar.com
http://www.twitter.com/rajib2k5
http://www.youtube.com/icsql
Post #1156111
Posted Wednesday, August 31, 2011 6:10 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 31, 2011 6:09 PM
Points: 1, Visits: 1

This error also occurs if your script's code is trying to read an output column (which is supposed to be write-only). Something like this will issue the error:

myVar = Row.anOutputColumn

Post #1168453
Posted Thursday, October 27, 2011 12:14 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, June 10, 2013 3:00 PM
Points: 2, Visits: 3
Also, This is elementary but I missed it for 30 minutes...

For Variable Names VARIABLE_NAME is not same as Variable_Name.

This causes the issue problem
Post #1197151
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse