Why the breakpoints that I set in my “Script Task” (not “Script Component” in the Data Flow *) never hits ?


Why the breakpoints that I set in my "Script Task" (not "Script Component" in the Data Flow *) never hits ?

On a Windows 2008 x64 machine, you're running SQL Server 2008 x64. Let's say you added a single "Script Task"; you wrote a very simple MessageBox.Show("Hello World"); line and put a breakpoint to this MessageBox.Show() line. Of course you should save your script to be able to run your SSIS package. Now you saved your script and returned to the main "Control Flow" and you see your "Script Task" there. You also see a circle on your script task which is telling you that it has a breakpoint in it. So far so good...

But when you saved your package it shows up the message box with "Hello World" although it should hit to your breakpoint and should show the line it hit. But it didn't.

To be able to have the debugger hit your breakpoint, you should change your SSIS Project's "Run64BitRuntime" propery's value from its default True to False as follows :

But that's not enough. Because your "Script Task" is still compiled as 64bit. You should edit your Script Task with "Edit Script" and save it again. This will help your script task code to be compiled as 32bit.

Now, you can run your package and you will see that the breakpoint hits (of course if it "really" needs to hit the line(s) you set 🙂 )

* : This applies to "Script Task" not to a "Script Component" you put in a Data Flow Task. To see the ways for debugging your code in "Script Component", please refer to our article titled as "Coding and Debugging the Script Component" in http://msdn.microsoft.com/en-us/library/ms136033.aspx .


Comments (20)

  1. thanks says:

    I knew it and done it before like 6 months ago, but forgot, now thanks for reminding me of how to do it again 🙂

  2. Sivan.G says:

    This Worked Thank u Very much…

  3. Atiq says:

    Good solved my problem

  4. Bill says:

    Thank you Faruk.  I had exactly that problem, and your solution works fine.

  5. Faruk Celik says:


    It's my pleasure hearing that this post helped you 🙂

  6. John.Groover@bcbsde.com says:

    Didn't work. My designer won't open.

  7. Praveen says:

    Its worked for me thanks

  8. vasudha says:

    wow…was struggling with this puzzel and here's the answer..worked like magic 🙂

  9. Krupa says:

    Thanks , worked for me too

  10. TC says:

    Thanks man! This helped me a lot after struggling with this issue.

  11. Faruk Celik says:

    It's great to hear that it helped you TC, Krupa, vasudha, Praveen 🙂

  12. Naveen Bhogi says:

    great !! helped me to overcome this problem.

  13. Greg says:

    But why should we have to dig this deep to find some obscure setting just to hit a breakpoint…sheesh!

  14. James says:

    Still not hitting a breakpoint. No idea why. This is awful

  15. majid ghorban janat says:

    it is work for me

    that is realy great

    you saved my day

  16. duchan says:

    thank you! you saved my day

  17. Dean says:

    How obscure! This should be on the MSDN page for the script task. Great tip, thanks – probably saved me many hours of frustration.

  18. AmitBurnwal says:

    It is not resolving my problem. The script task get open but never hit the breakpoint it just keep on running.

  19. Raghava Reddy says:

    Hi Faruk,
    i had same issue and fixed it in very less time by following this blog.
    thanks for saving our time.

Skip to main content