SQL Server Home
Breakpoint bug with SSIS script task in BIDS
7/12/2007 9:04:20 AM
User(s) can reproduce this bug
Updated... I have now added something to reproduce the problem. If you're going to close this again saying it's a duplicate, could you please at least point us in the direction of the duplicate entry so that we can follow it!
As reported in following forum entry:
I have an SSIS package which is predominantly made up of script tasks. Putting a break point into a script task and pressing F5 to debug has the following symptoms:
1. I get the message: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience." there is a debug button and a close button.
Clicking on Debug instead of close brings up the Visual Studio Just in time debugger dialog which says:
An unhandled exception ('System.Runtime.InteropServices.COMException') occured in DTAttach.exe 
It then gives me options to continue debugging in a new instance of Microsoft CLR debugger 2005 or a new instance of Visual Studio 2005. Choosing the CLT debugger brings up the dialog box saying:
"An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in Microsoft.SqlServer.ScriptTask.dll
Additional information: File position not valid for new breakpoint."
2. Choosing close instead of Debug comes up with the message:
"Microsoft Visual Studio for Applications has lost the link to .
Your work will be exported to C:\document and settings\ghooton\personal when you quit the application"
3. Clicking OK continues executing the package but does not break at the break point set.
SQL Server 2005 - Developer Edition
Windows XP SP2 Professional
Operating System Language
Steps to Reproduce
1. Unzip all the files from the attached zip file into a folder.
2. Open the Integration Services Project1.sln file.
3. View the ReproduceBug.dtsx package and note that the only break point is in the 'Script with break point' task.
4. View the scripts of the 'Source' and 'Destination' data flow components of the initial 'Data Flow Task'. Note that the 'Source' adds 2 rows to the output buffer. Note also that the 'Destination' contains a single variable 's' that has different assignments made. Finally note that neither have break points assigned.
5. Run the package.
6. The debugger opens with what looks like the correct window at the correct break point. On further investigation you will notice that the yellow area highlighting the running code is different to the line shown. If you add a watch on the variable s you will notice it has a value of 5 showing that actually the code executing is in the 'Destination' script of the Dataflow component rather than the window that is currently open.
7. Press F10 to step through the code. Instead of the executing line of code going onto the End Sub line, it goes onto an empty line and the s variable's value has changed to '6'. Again showing that the code that is actually executing is in the 'Destination' script. Stepping through the code will actually step through the 'Destination' script code rather than that which is on screen and will eventually cause problems when it runs out of lines to execute.
8. Press F5 to continue execution until the next break point. The code breaks in the same 'Script with break point' script window but is actually executing the 'Destination' script code for the SECOND row that was added via the 'Source' script code.
As described in the Steps to Reproduce.
The break point and the executing code should be in sync.
to post a comment.
Please enter a comment.
on 3/30/2010 at 5:40 AM
Get a refund on 2005 as the product is not fit for purpose!
on 11/6/2008 at 7:29 AM
Seriously Microsofot, you're not going to fix this in 2005?!?? I have this problem day in and out with SSIS (2005 Enterprise), and have to reboot my machine in order for the error to go away (atleast for a short time). It's an extreme pain, and telling me I'll have to wait for 2008 and possibly inherit a whole new boatload of problems is the solution I'm being offered? This is poor product follow up, and quality assurance.
on 7/18/2008 at 10:57 AM
Thanks for your feedback, we appreciate it.
This issue has been fixed in SQL Server 2008 RC0 build. Please use this link to download the RC0 build: http://www.microsoft.com/downloads/details.aspx?FamilyId=35F53843-03F7-4ED5-8142-24A4C024CA05&displaylang=en
on 4/27/2008 at 2:49 AM
Can you tell me which one it's linked to then so that I can follow it and find a solution? I can't seem to see a link on this one.
on 4/25/2008 at 4:49 PM
Your issue is a duplicate of existing case. We are linking the two cases together and closing this case. Thank you for your submission and support of SSIS.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft