Thursday, March 8, 2012

Can't debug Script tasks

After upgrading to CTP16 (Sept.), I can't seem to debug my script tasks. Everytime I run the package with a breakpoint in script task I get following error: "SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience. "

If I remove the breakpoint the scrip task runs successfully. So my question is how do I debug a script task with CTP 16?
As per my knowledge, there was no debugging support for script component.
So, you are left with few options like MessageBox.Show or rowcount etc.

Don't know if debugging support is there in sept/nov versions.

hth,
Nitesh|||No he said script task not script component and the script task does indeed support debugging.

As for the problem, do you get any error information in the error pane or progress pane. Do you get a minidump in 90\shared\ErrorDumps?

Thanks,
Matt|||Thank you for you reply Matt. No. I do not get any error info in error pane, output windows, or errordumps folder. I just get a dialog box with the error message listed above.

My Script task is set to Precompile and all the other properties are deafulted. I was under the impression that I would only get the error when there was syntax or logic problem, however, that's not true since I can take the breakpoint out and the script runs successfully.|||

If you set precompile to false then open and save the script does that make the breakpoints work or do you still get the same problem?

Thanks,
Matt

|||I have tried setting the precompile to false and it does break. However, it's not consistant. I guess CTP16 still has debugger issues hope they fix it in sql 2005 rel.

No comments:

Post a Comment