Script Task scripts will not stop at breakpoints.

JWardRogers

I can not debug any of my scripts. They execute just fine, but if I have a breakpoint set in the script code (in VSA), I get the message:

SQL server integration services script task has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost.

Debug Close

When I choose "Close" I get this:

sMicrosoft Visual Studio for Applications has lost the link to .

Your work will be exported to <<my Local Settings My Documents path>> when you quit the application.

OK

When I click "OK" my package executes normally, but no breakpoints will fire from that point on.

Phil Brammer


No need to post your message twice....

Script Tasks, not Script Components, correct

One workaround is to use a MSGBOX().

JWardRogers

I was in the process of deleting my other post when you replied. I didn't want to post in a thread that had something marked as an answer.

Yes, this is for script tasks. I certainly could use MsgBox() but that is hardly an answer to this problem. I could also write text out to a file, call a web service, insert a record into a table, etc. None of those things take the place of stepping through code. Is there a fix in the works for this issue It really makes script tasks of limited use, or at least it makes them take much longer to develop.

Phil Brammer

And you are following these steps

http://technet.microsoft.com/en-us/library/ms140033.aspx

JWardRogers

With the exception of right-clicking (I was clicking in the margin to set the breakpoint), yes, that is exactly what I did.

Phil Brammer

Do you have any SQL Server service packs applied

JWardRogers

How would I tell

Phil Brammer

JWardRogers wrote:

How would I tell

In BIDS, go to Help->About and select SSIS. What is the version number reported there

JWardRogers

9.00.1399.00

Phil Brammer

That's the original.

Try grabbing the SQL Server Service Pack 2 and installing that. Many fixes are contained in SP1 and SP2 as well.

JWardRogers

Phil Brammer wrote:

That's the original. Try grabbing the SQL Server Service Pack 2 and installing that. Many fixes are contained in SP1 and SP2 as well.

But unfortunately not the fix for my problem. :-(

SP2 is installed and it is still behaving the same way.

Version is now 9.00.3042.00

JWardRogers

I'm still having the same problem...

Phil Brammer

XP Vista

JWardRogers

Server 2003 version 5.2.3790 (service pack 1.0)

Hot Fix: KB931836

4GB RAM

Phil Brammer

JWardRogers wrote:

Server 2003 version 5.2.3790 (service pack 1.0) Hot Fix: KB931836 4GB RAM

Do you also develop on a local workstation Have you tried breakpoints on that if so