Can't Design a Script

I've placed a Script Task in a package, but the "Design Script..." button only closes the dialog and nothing happens. I've tried a Script Task in an empty package, too.

This is a vanilla 2003 virtual PC. No previous beta/CTP versions installed. RTM bits of SQL 2005 and VS.NET 2005 Pro. I can edit macros in VS.NET, so I'm sure the VSA environment is around. No event log entries. Typically run as non-admin, but tried as admin, too.

Anyone ever seen this?

Yeah, it happens sometimes. Reboot your machine.

Can't delete Web Assistant task

I used the Web Assistant tool to monitor a couple of tables. When I was fin
ished with the monitoring after a couple of weeks, I didn't want to monitor
the tables anymore. I deleted the proceedure, and now when I add data to th
e tables, I get an error me
ssage:
Failed@.CDBBaseGroupObj::dbwrite attribute xref.Database error:[Microsoft][ODBC SQL Serv
er Driver][SQL Server] SQL Web Assistant: Could not execute the SQL statemen
t.
I click "OK" on the error message and proceed as normal.
Can anyone point me in the right direction of getting rid of this error mess
age popping up?
thanks,
SKClarkWhen you select the option to monitor tables in the Web Assistant, it
also creates triggers. If all you did was manually drop the stored
procedure, then the triggers likley still exist. At this point you'll
need to delete them manually. In future, use sp_dropwebtask, which
will clean up all of the objects.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Tue, 10 Feb 2004 08:51:08 -0800, "SKClark"
<anonymous@.discussions.microsoft.com> wrote:

>I used the Web Assistant tool to monitor a couple of tables. When I was finished w
ith the monitoring after a couple of weeks, I didn't want to monitor the tables anym
ore. I deleted the proceedure, and now when I add data to the tables, I get an erro
r m
essage:
>Failed@.CDBBaseGroupObj::dbwrite attribute xref.Database error:[Microsoft][ODBC SQL Ser
ver Driver][SQL Server] SQL Web Assistant: Could not execute the SQL stateme
nt.
>I click "OK" on the error message and proceed as normal.
>Can anyone point me in the right direction of getting rid of this error mes
sage popping up?
>thanks,
>SKClark|||cool...I found 3 triggers attached to a table. I deleted them and now the
error message doesn't show up anymore.
Thanks for your help!!! :-)
-- Mary Chipman wrote: --
When you select the option to monitor tables in the Web Assistant, it
also creates triggers. If all you did was manually drop the stored
procedure, then the triggers likley still exist. At this point you'll
need to delete them manually. In future, use sp_dropwebtask, which
will clean up all of the objects.
-- Mary
MCW Technologies
http://www.mcwtech.com
On Tue, 10 Feb 2004 08:51:08 -0800, "SKClark"
<anonymous@.discussions.microsoft.com> wrote:

>I used the Web Assistant tool to monitor a couple of tables. When I was finished w
ith the monitoring after a couple of weeks, I didn't want to monitor the tables anym
ore. I deleted the proceedure, and now when I add data to the tables, I get an er[/
color]
ror message:
>thanks,
>SKClark

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.

Can't Debug a script task

After upgrading to CTP16 (Sept.), I can't seem to debug my script task. 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?

This should be posted to SQL Server Integration Services. Please acknowledge and I'll move the thread to the appropriate group.