Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 639
  • Last Modified:

SQL Web Assistant: Web task not found!!!

Hi,
I cant solve the problem:

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'

[Microsoft][ODBC SQL Server Driver][SQL Server]SQL Web Assistant: Web task not found. Verify the name of the task for possible errors.

This is happenin continously when I try to call a stored procedure or execute some T-SQL commands on my ASP page.
Thanks.
0
rizamasirov
Asked:
rizamasirov
  • 3
  • 3
1 Solution
 
JWTCommented:
Are you using sp_runwebtask?  or perhaps the SQL Web Assistant?

Can you post the ASP code in the proc call?

My first instinct would be to look at the sproc name to make sure it is spelled correctly.  Also check your permissions.  The user must have SELECT permission on the sproc to run it.

In general, I would reccomend using ADO for sproc calls from ASP pages.

Good Luck
0
 
rizamasirovAuthor Commented:
It doesnt differ from useing sproc or T-SQL. For example:

Line 41 : conn.execute("UPDATE kayitlar SET title='"&title(I)&"',descr='"&descr(I)&"',createdate='"&CrDate&"',secret_status='"&secret_status(I)&"' WHERE id = '"&Cint(PID_Checked(I))&"'")

-----------------------------------------------

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'

[Microsoft][ODBC SQL Server Driver][SQL Server]SQL Web Assistant: Web task not found. Verify the name of the task for possible errors.

/album/Kmasterupdate.asp, line 41


I have no idea about "sp_runwebtask" or "SQL Web Assistant". How can I check it out?
Thanks
0
 
JWTCommented:
If you are not using "sp_runwebtask" or "SQL Web Assistant" don't worry about it.  It looks like you are using ADO.

OK - so I didn't think this would be an easy solution.

Try this - does the table kayitlar have any triggers on it?

To view the triggers on a table use

sp_helptrigger 'tablename'

If so that trigger may reference an old trigger, or the trigger name may be mispelled.

Also - try running your query in Query Analyzer directly against the database.
0
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
rizamasirovAuthor Commented:
Triggers:
------------------------------------------
life Web Page_1 dbo     0     0     1    
life Web Page_2 dbo     1     0     0    
life Web Page_4 dbo     0     1     0    
------------------------------------------

I dont know how I did this  :(((
How can I drop all triggers? Because I dont know how to use them.

Here is the output of Query An.
-------------------------------------------
UPDATE kayitlar SET title='AA',descr='assadasd',createdate='02.02.2003',secret_status=1 WHERE id = 93
-------------------------------------------
Server: Msg 16882, Level 11, State 1, Line 0
SQL Web Assistant: Web task not found. Verify the name of the task for possible errors.

(1 row(s) affected)
-------------------------------------------
0
 
JWTCommented:
Yup it was the triggers!

Whew - I was wonderin' about this one.  Anyway, to drop them just issue a

DROP TRIGGER nameOfTriggerHere in QA.

Good Luck
0
 
rizamasirovAuthor Commented:
Thanks! Great solution! :))
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now