2

I have created an SSIS package in SQL Server. In Data Flow I have added a Script Task in which there is a break point. When I started debugging the package, it hit the break point and everything went fine.
Then I made some changes in code in Script Task and now break point won't hit. I have tried everything but no luck. I have even did the following as per Microsoft but same issue.

http://blogs.msdn.com/b/farukcelik/archive/2010/03/17/why-the-breakpoints-that-i-set-in-my-script-task-not-script-component-in-the-data-flow-never-hits.aspx

In the package it self it shows that Red circle on Script Task which means there is a break point but it never hits. When I debug the package and it reaches the Script Task, then looks like it is trying to open the editor and hit the break point but then it automatically closes and continues with the code. What am I doing wrong?

Frank Martin
  • 3,147
  • 16
  • 52
  • 73
  • Yes I restarted the SSIS service. – Frank Martin Jun 03 '14 at 09:27
  • Yes I have restarted SSDT twice but no luck. Now I have restarted the machine so let's see what happens. – Frank Martin Jun 03 '14 at 09:34
  • Same problem after restarting machine. – Frank Martin Jun 03 '14 at 09:47
  • Ok I reverted the changes which were described by article above and now it works. – Frank Martin Jun 03 '14 at 09:48
  • I made some changes and now breakpoint won't hit. This tool is a BIG JOKE! – Frank Martin Jun 03 '14 at 10:17
  • 2
    A Script Task exists on the Control Flow. A Script Component exists inside a Data Flow. The names are similar but the ability to use a break point with a Script Component has only been available since the 2012 release of SSIS. Which scripting object are you using? Which version of of SSIS are you using (2005/2008/2008r2/2012/2014)? Post your code. – billinkc Jun 03 '14 at 12:01
  • @FrankMartin Your primary intetion is to test out SSDT and you are using 2012? You shouldn't face these issues in 2008 and I believe it's mostly after that...likely 2010, 2012... – bonCodigo Jun 03 '14 at 12:04
  • Sorry yes it's a script task inside control flow and not data flow. I am using SQL Server 2012 on Windows Server 2012 (all 64 bit) – Frank Martin Jun 04 '14 at 11:47
  • Did you switch the project to 32bit? – Joost Jun 04 '14 at 12:25
  • some functions disable the debugger... comment out your code until you find the line responsible. Look here for two examples http://stackoverflow.com/questions/40677400/vs-2015-ssis-script-tasks-cannot-be-debugged – Chris Tian Dec 06 '16 at 21:25

0 Answers0