Post reply

Problem Debugging Script Task

  • February 27, 2014 at 10:14 am

    #284164

    Hi. We have a strange problem when trying to debug a script task in SSIS 2012. Here's the scenario - my colleague and I both use remote desktop connections to connect to the same dev server and use SQL Server Data Tools (Visual Studio) on that server. So it's the same installation, same server, etc. I can debug script tasks with no problem but he cannot debug them.

    He can open the script, add a breakpoint, and run it. It gets to the script task and opens VSTA. But then nothing happens. No line of code is highlighted. Hitting F5 or F10 doesn't step through the code in any way. He can't move forward to get to the problematic part.

    I do not have this problem. Using the same exact package as he does, with the same breakpoint, after it opens in VSTA I can use F10 to step through it with no problems.

    We tried changing the 64-bit debug setting with no effect. It's Yes for me and it works fine. We tried No for him and it didn't help.

    So, same machine, same package, same code, same breakpoint, debugging works for me and not for him.

    Any suggestions?

    Thank you,

    Cindy

  • April 28, 2014 at 9:52 am

    #1709216

    Any suggestions?

  • April 28, 2014 at 11:01 am

    #1709235

    Has your colleague looked at the "Execution Results" pane for a clue about what is happening? Are there any errors?

    Another thing to try is have your colleague rebuild the SSIS project. Perhaps he running from an older source than you are.

  • April 28, 2014 at 11:03 am

    #1709237

    see this if it helps... http://stackoverflow.com/questions/15725086/visual-studio-2012-wont-let-me-debug

    Good Luck 🙂 .. Visit www.sqlsaga.com for more t-sql code snippets and BI related how to articles.

  • September 12, 2017 at 7:37 am

    #1959093

    cindypsych 73930 - Thursday, February 27, 2014 10:14 AM

    Hi. We have a strange problem when trying to debug a script task in SSIS 2012. Here's the scenario - my colleague and I both use remote desktop connections to connect to the same dev server and use SQL Server Data Tools (Visual Studio) on that server. So it's the same installation, same server, etc. I can debug script tasks with no problem but he cannot debug them.He can open the script, add a breakpoint, and run it. It gets to the script task and opens VSTA. But then nothing happens. No line of code is highlighted. Hitting F5 or F10 doesn't step through the code in any way. He can't move forward to get to the problematic part.I do not have this problem. Using the same exact package as he does, with the same breakpoint, after it opens in VSTA I can use F10 to step through it with no problems.We tried changing the 64-bit debug setting with no effect. It's Yes for me and it works fine. We tried No for him and it didn't help.So, same machine, same package, same code, same breakpoint, debugging works for me and not for him.Any suggestions?Thank you,Cindy

    hi
    we have the same problem, my colleague can debug and i can not ! any idea if this got fixed for you. The config also same SSIS 2012.

  • September 12, 2017 at 8:46 am

    #1959127

    All those using 2012... what SP/CU are you using?  2012 had some nasty regression problems until after 2012 sp3 CU 6 (which isn't the latest now).  Upgrade to the latest SP/CU and try again.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • September 13, 2017 at 7:31 am

    #1959239

    Jeff Moden - Tuesday, September 12, 2017 8:46 AM

    All those using 2012... what SP/CU are you using?  2012 had some nasty regression problems until after 2012 sp3 CU 6 (which isn't the latest now).  Upgrade to the latest SP/CU and try again.

    hi
    the IDE is VS 2015 and I have selected the target server as 2012 and change the use the defauly 64bitxxxxxxx to false. So, it runs as 32 bit and the IDE is 2015 and the SSIS package is created in 2016 version with the target as 2012.
    this is the version info: Microsoft SQL Server Integration Services Designer
    Version 14.0.800.90

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply