Response Buffer Limit Exceeded

[scribbler]

Can anyone tell me why this error is likely to appear ?
I have 3 tables open, first 2 report fine but 3rd table gives me the error below when I try to response.write the fields to screen. I am only expecting a small number of records to be returned. I am using a loop to go through and response.write each record to screen and if I take out the loop leaving the report to display just one all works fine. I only expected something like this if the server took a while to go through the records but I get the error within seconds of refreshing the page. I have even closed and set the first 2 recordsets to = nothing once used in case that was the problem.


Response object error 'ASP 0251 : 80004005'
Response Buffer Limit Exceeded
/testform.asp, line 0
Execution of the ASP page caused the Response Buffer to exceed its configured limit.

 

[onpnt]

try adding
<%response.buffer=false%>
to the very first line in the page

___________________________________________________________________

_{onpnt.com
SELECT * FROM programmers WHERE clue > 0
(0 row(s) affected) -->faq333-3811}

 

[scribbler]

Sorry Guys but Found the error after hours of testing..... I had word blindness.... I omitted the rs.MoveNext from my loop

 

[onpnt]

cool you found the problem.

just a side note on setting the buffer size Buffer to beware of

good reading. take a minute to go through it

___________________________________________________________________

_{onpnt.com
SELECT * FROM programmers WHERE clue > 0
(0 row(s) affected) -->faq333-3811}

 

[dilettante]

I guess I had forgotten AspBufferingLimit in the IIS metabase myself.

Food for thought... I'm making extensive use lately of a home-brew "compiled ASP" program generator to create VB6 CGI programs from source code styled almost exactly like ASP pages (but allowing most VB6 capabilities). It uses an object model that's almost a direct knock-off of ASP's, right now with much of Server, Request, and Response implemented - but no Session as of yet because I tend to avoid Session in my ASP anyhow and have not needed it.

This thread and onpnt's comment made me think about something... right now I let the Response.Write buffer (given Response.Buffer = True) grow indefinately large. I haven't tripped over a goof like the one above yet, but it is only a matter of time.

Maybe I ought to implement a property like Response.BufferingLimit and give it a reasonable default. Then if I overflow this value I can generate a trappable error and deal with it however in my "ASP" page or let the default error handler return my stock 500 Server Error page. IIS used to default to around 4MB for the buffer limit.

I should make a Request.MaxAllowed too (like AspMaxRequestEntityAllowed) I suppose to catch attempts to overflow me on input. I think the web server already limits this, but why take a chance?

Thanks!


Oh. Why the wacky development system? It lets me use VB and ASP skills together to create applications for non-IIS web servers on Windows platforms. Right now I'm sort of amazed by the apparently quite secure and trivial to administer AnalogX SimpleServer:

http://WWW web

server.

I've had a forum and blog collaboration site up on a Windows 95 box behind a NAT with port 80 mapped through for 5 weeks now. Not hacked yet even though the server logs show 4 to 10 penetration attempts per day! Of course I'm waiting for the other shoe to drop.