Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
hethy
Starting Member
8 Posts |
Posted - 2002-08-16 : 15:14:11
|
| Has anyone else using SQL Server 2000 gotten this error:[url]http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q174853&[/url]when executing a series of sp_makewebtask statements? Sometimes the error will show up, sometimes it won't. But meanwhile I'm running the same statements over and over again (dropping them after creating them so I can run the sp_makewebtask statements again to see if I can figure out what is making it die). Sometimes it gives me the error after the third sp_makewebtask statement executes, sometimes it gives me the error after the 6th statement executes, so I don't think it's a problem with the statement itself/themselves.This is how I've been running my sp_makewebtask statements (is that an example of "serial execution"?). I ultimately have quite a few statements to run, which is why I'm not using the Web Assistant Wizard to create and run each one.. EXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page1.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=11', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page1"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page2.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=12', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page2"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page3.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=13', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page3"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page4.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=14', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page4"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page5.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=15', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page5"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page6.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=16', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page6"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page7.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=17', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page7"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page8.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=18', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page8"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page9.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=19', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page9"GOEXECUTE sp_makewebtask @outputfile = 'E:\Contract\dev\page10.asp', @query = 'SELECT field1,field2 FROM table1 WHERE fieldID=20', @templatefile = 'E:\dev\template.tpl', @dbname = 'db1', @rowcnt = 0, @whentype = 10, @datachg = N'TABLE=table1', @procname="proc_page10"GO |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-16 : 15:19:52
|
| I think it's even simpler than that: could any of these pages be accessed via web while they're being created? If someone is accessing a page, the web server will open it as a regular file and other processes will be prevented from modifying or deleting it until it's closed. Considering that it's an intermittent problem this seems the most likely explanation. |
 |
|
|
hethy
Starting Member
8 Posts |
Posted - 2002-08-16 : 15:46:46
|
| No one is accessing the web pages right now -- all this is just in my own local dev environment. But, some progress maybe -- I am finding a pattern now. I really thought it was random before (sorry, I should've run more structured tests before posting earlier), but now I see that I can run 8 of those sp_makewebtask statements at a time, and they'll run. It's executing the 9th one that gives me that access violation error. I changed the order of the sp_makewebtask statements, so I know it's not any one statement that's messed up, it's just whichever statement I run as the 9th statement, that gives me the error. For that 9th statement that gives me the violation, btw, it *does* append the triggers for table1 (I check it by going to Enterprise Manager/SQL Server/Databases/db1/tables/table1 -- All Tasks/Manage Triggers), although somehow the webtask proc itself doesn't get created normally because I can only drop the 9th proc created using DROP PROC rather than SP_DROPWEBTASK.Any thoughts? TIA |
 |
|
|
|
|
|
|
|