4

In my SSIS package, I have a script task in addition to other tasks. When I put a debug point within the script task and run the package( on the whole), ideally, it is supposed to hit the breakpoint. but it now only opens a new VS window, shuts it after few seconds and a green tick is displayed over the task.

I tried setting the the Run64BitRuntime flag to false and also editted and saved the script task again. The issue persists. Any pointers on this ?

I have VS 2010 BI and the machine is 64 bit Windows Server R2

3
  • Yup. The pitfall of SSIS. I've never been able to debug a script task. I wonder if there's a workaround for this Commented Oct 1, 2013 at 9:38
  • possible duplicate of how debug a script component in SSIS Commented Oct 1, 2013 at 9:39
  • 3
    Solution Explorer -> Project -> Properties -> Debugging -> Run64BitRuntime -> False Commented Oct 1, 2013 at 11:52

3 Answers 3

8

Yes, break points do work in script task. But if that was a script component, then it wouldn't have worked. Any way, if you have a script task, the reason it might not be working is that it may be using the 64 bit runtime. Try running it in the 32 bit runtime.

Also, make sure that the place at which you have hit the breakpoint is actually reachable. If there are some case statements or if conditions, possibilities are that the line of code is actually missed.

Sign up to request clarification or add additional context in comments.

3 Comments

Starting with the 2012 release of SSIS, you do have the ability to debug script components.
My first step with the VTSA editor is add a breakpoint at the first line just to get into debug mode and then F5 my way to the actual breakpoint I want.
Even when i place the breakpoint at the first line, it does not hit the breakpoint. not sure why it does not work now . Already tried the Run64BitRuntime option
3

Surely debug is allowed for script task. Couple of point to remember 1. Run the package in 32 bit 2.wherever u set up debug pointer... code should be rechable 3.debug only allowed for 1 script task. Ssis engine can only show you debugging only for 1 script task. If you have 2 script task then ssis will open debugging only for first script task.. suggesting you put de bugging only to one script task

Comments

0

I ran into this as well and found the script task had been set to optimize code even for debug mode.

See more detail here

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.