OK.  Will do.  I only posted in case some more information had been found on
the problem since then, but this is still MUCH more information than we've
been able to find elsewhere.  I've also verified that our IT support staff
has not installed SP1 on our Windows 2003 server, so the suggestions below
might just work out.

Thanks for your help.

Keith

Below I have copied my post from the data.ado group - it contains my ASP code
and the IISState log for the problem thread.  I can provide module versions,
if you wouldn't mind telling me which dll's to examine.  I did just install
the MDAC 2.8 upgrade, but the behavior was the same before as after.  I'm not
sure how to provide a stack trace, but I'll see if I can Google something on
it.  I'd be happy to provide anything I can  to help solve this issue.

//bob

--snip--
Like many others, I am struggling with a problem in Win2K3 and IIS6 using an
ADO Stream object and an SQL FOR XML stored procedure.  Let me preface by
saying that the ASP code has worked flawlessly on Win2K and IIS 5 for over a
year.  Now on Win2K3, the page will work for a while, then it becomes
unresponsive.  It returns no error, it just hangs the connection so that no
other site page will respond until the browser is closed and re-opened.  
Sometimes recycling the app pool will clear it up temporarily, sometimes I
have to restart IIS.  Page will work fine for a few hours or even days, then
it stops responding.  CPU and memory utilization seem normal in TaskMan.

First, here's the ASP code:

<%
 dim cn
 set cn = server.CreateObject("ADODB.Connection")
 cn.open MM_iiWeb_STRING
 dim result
 result =  getSQLXML(cn, "exec proc_getLinkCatXML", "linkpage.xsl", ".")
 response.Write result
 if cn.state=1 then cn.close()
 set cn = nothing   

%>

<%
function getSQLXML(byref cn, byval sql, byval xslfile, byval basepath)
 dim cmd
 dim objOutStream
 Set objOutStream = Server.CreateObject("ADODB.Stream")
 objOutStream.open
 Set cmd = Server.CreateObject("ADODB.Command")   
 cmd.ActiveConnection = cn
 cmd.CommandText = sql
 cmd.Properties("Base Path").Value = Server.MapPath(basepath)   
 cmd.Properties("XML Root") = "root"
 cmd.Properties("XSL") = xslfile
 cmd.Properties("Output Stream") = objOutStream
 cmd.Execute , , adExecuteStream   

 getSQLXML =  objOutStream.ReadText
 objOutStream.Close
 set objOutStream = nothing
 set cmd = nothing   
end function
%>

When it hangs, here is IISState log info for the thread:

Thread ID: 15
System Thread ID: bc0
Kernel Time: 0:0:0.109
User Time: 0:0:0.968
Thread Type: ASP
Executing Page: C:\INETPUB\WWWROOT\IIWEB\TEMPLATES\LINKS.ASP

# ChildEBP RetAddr  
00 025de3d8 77f4262b SharedUserData!SystemCallStub+0x4
01 025de3dc 77e418ea ntdll!NtDelayExecution+0xc
02 025de444 77e416ee kernel32!SleepEx+0x68
03 025de450 0439c4f9 kernel32!Sleep+0xb
04 025de464 04382a20 msado15!CQuery::Cancel+0x50
05 025de49c 0437d84d msado15!CCommand::Cancel+0x58
06 025de4ac 0437516f msado15!CCommand::Term+0xd
07 025de4c8 04373951 msado15!CStdSymbiontObject::InternalRelease+0x6c
08 025de4d8 7710736a msado15!ATL::CComObject<CRecordset>::Release+0x11
09 025de4e8 7346384b OLEAUT32!VariantClear+0xad
0a 025de4fc 734641cf vbscript!VAR::Clear+0xab
0b 025de50c 7346416a vbscript!CScriptRuntime::Cleanup+0x59
0c 025de84c 73465184 vbscript!CScriptRuntime::Run+0x2ccc
0d 025de504 80020102 vbscript!CScriptRuntime::Run+0x99
WARNING: Frame IP not in any known module. Following frames may be wrong.
0e 025de504 80020102 0x80020102
0f 00000000 00000000 0x80020102

I have seen the same problem posted several times in various newsgroups and
message boards for the past 8 months or so, but I have seen no explaination,
solution, or workaround offered.  I would appreciate any insights.

//bob

--end snip--