SQL Web Assistant: Web task not found

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I am trying to run cmd.ExecuteNonQuery() in order to perform an update and
even though the database is updated OK I keep getting the following error
message:

"SQL Web Assistant: Web task not found. Verify the name of the task for
possible errors.
Exception Details: System.Data.SqlClient.SqlException: SQL Web Assistant:
Web task not found. Verify the name of the task for possible errors."

I am using Visual Studio 2003, ASP.Net and the database is SQL server 2000.

Any help on this would be appreciated as this is beginning to drive me mad!

If more information is required please let me know.

Thanks in advance.
J
 
It sounds like you're trying to execute the system stored procedure
sp_runwebtask, which takes the name of a procedure to run as one of
its arguments. The error message indicates that it can't find this
particular procedure. If this is not the case and you're doing
something entirely different, I'd advise sticking a SQL Profiler trace
on the call to see both sides of the conversation.

--Mary
 
I just had a sudden flash -- I think I may know what is going on.
Someone (has to be a sysadmin on your SQL Server) has gone in and
fooled around with the Web Assistant Wizard. When you choose certain
options, it creates a trigger on the table. What probably happened is
that whoever this person was, when they were done playing, they didn't
clean up after themselves, and only deleted the stored procedure,
leaving the trigger behind. Therefore, when you do your update, the
trigger fires and can't find its stored procedure, hence the message.
I may be wrong, but it's a possibility you should check out.

Mary
 
Hi Mary,

Thanks for your posts. You were spot on, someone has been playing about with
Web Assistant Wizard and there were some triggers on a table. As soon as I
deleted them everything worked fine.

Thank you very much for your help.

Jen
 
On Thu, 03 Feb 2005 14:59:00 -0500, "Mary Chipman [MSFT]"

Good shootin' Mary. Right on target! Thanks for energizing some more of our
brain cells.

I just had a sudden flash -- I think I may know what is going on.
Someone (has to be a sysadmin on your SQL Server) has gone in and
fooled around with the Web Assistant Wizard. When you choose certain
options, it creates a trigger on the table. What probably happened is
that whoever this person was, when they were done playing, they didn't
clean up after themselves, and only deleted the stored procedure,
leaving the trigger behind. Therefore, when you do your update, the
trigger fires and can't find its stored procedure, hence the message.
I may be wrong, but it's a possibility you should check out.

Mary
Click to expand...

Otis Mukinfus
http://www.otismukinfus.com
 
Back
Top