Link to home
Start Free TrialLog in
Avatar of danny1620
danny1620Flag for United States of America

asked on

SSIS Script Component Error

Hi

I am new to this field .. I am using a Script component of Data Flow Task and when I try to debug the Script It throws me an error
integration services script component error: cannot debug or run this project because the required version of microsoft application is not installed

Should I need to install the whole MS office application with latest SP ?

What is the cause for this problem Help Me?

Thanks in Advance
Avatar of Rob Farley
Rob Farley
Flag of Australia image

Debugging Script Components isn't pretty. I generally have a bunch of extra outputs to be able to get a picture of what's going on. You can't use Breakpoints in the Script Component, like you can in the Script Task (Control Flow).

You can raise events, and you can use FireProgress commands to push information out to the Progress tab. You can even use MessageBox to pause execution. (But be careful - if you have millions of rows going through, you might be better off pushing information out to a separate output)

No 'stepping through' or anything though. Sorry.

Rob
Avatar of danny1620

ASKER

I am unable to debug it .... it is giving me an error saying
integration services script component error: cannot debug or run this project because the required version of microsoft application is not installed

Script that i am actually using is just an if then else condition
you cannot debuf the script component inside dataflow, only the script task of controlflow.
try to debug using message boxes (MSGBOX) inside the script to see the values that is being passed in by the script.
helped?
Regards,
Pedro
Danny,

Correct - you can't debug like you can in the Script Task (Control Flow). A Script Component (Data Flow) gets called for every row in every buffer, so it's unfeasible to debug using "stepping through", etc.

Instead, push useful information out to a different output buffer, and look at what's going on that way.

If you're just doing an "if then else" condition, I'd consider a Derived Column transform or a Conditional Split. A Script Component is probably overkill for you.

Use Data Viewers to look at the data going down a particular path - right-click on the data flow arrow and you'll see how to add them.

Rob
Actually I am using a derived column instead of the script for now but was curious to know whats going wrong... I have never used VS, so do not know much about it but in case if its more than else which it is in other packages that i need to migrate, In such case what do i need to do.. Could you please elaborate your solution/explanation.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Rob Farley
Rob Farley
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
you mean just attach it to any DF destination or a staging table and see the result
Yeah - have an output which you send off to a table, flat file, or even just another transform that doesn't have an output (just so that you have a data flow path that you can put a viewer on)

Rob
link the script to a UNION ALL component and add the a data viewer in the link row.
Helped?
Regards