Breakpoint bug with SSIS script task in BIDS - by Hoots

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 287124 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 7/12/2007 9:04:20 AM
Access Restriction Public


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 [3148]

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.

Sign in to post a comment.
Posted by Hoots on 3/30/2010 at 5:40 AM
Get a refund on 2005 as the product is not fit for purpose!
Posted by Justin B 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.
Posted by Microsoft 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:

SSIS Team.
Posted by Hoots 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.
Posted by Microsoft 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.