SSIS Script task and Script Component ReadWriteVariables list not consistent between both types of component - by PJFINTRAX

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 126791 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 5/25/2006 7:16:07 AM
Access Restriction Public


 had a Script Task which was taking a few package level variables to use in the script.

So I put the list of variables in the ReadWriteVariables property.

Specified them like this:

"User::FileBeingProcessed, User::FileSource"

And all was well....

Then later on decided to use the same set of variables in a Script Component contained in a Data Flow.

And kept kept getting a "..variable not found.." error dialog when I clicked on Design Script.

Finally the solution came to me: Spaces in the list of variables !

In a script task you can have a space after a comma in the list... but in a script component you CAN'T !!

So what works in a Script Task is :

Task :   "User::FileBeingProcessed, User::FileSource"

But that will not work in a Script Component...

See the difference?:

Task     :"User::FileBeingProcessed, User::FileSource"

Sign in to post a comment.
Posted by Microsoft on 6/25/2007 at 4:18 PM
Thanks for reporting the issue to me, this is fixed in our Katmai release CTP1.

Wenyang HU