Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP 3 Classic ASP Active Server Pages 3.0 > Classic ASP Databases
|
Classic ASP Databases Discuss using ASP 3 to work with data in databases, including ASP Database Setup issues from the old P2P forum on this specific subtopic. See also the book forum Beginning ASP.NET Databases for questions specific to that book. NOT for ASP.NET 1.0, 1.1, or 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP Databases section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old February 3rd, 2010, 03:50 PM
Friend of Wrox
 
Join Date: Oct 2006
Posts: 112
Thanks: 12
Thanked 0 Times in 0 Posts
Default 500 - Internal server error. ONLY when data received is alot

On one of my intranet web pages where the users access data… the following message comes up only when the data received is a lot…
is there a default amount that I can increase too ???

[FONT='Verdana','sans-serif']500 - Internal server error.[/FONT]

[FONT='Verdana','sans-serif']There is a problem with the resource you are looking for, and it cannot be displayed[/FONT]

[FONT='Verdana','sans-serif']thanking you in advance[/FONT]

[FONT='Verdana','sans-serif']Rino[/FONT]

 
Old February 3rd, 2010, 04:55 PM
Friend of Wrox
 
Join Date: Jun 2008
Posts: 1,649
Thanks: 3
Thanked 141 Times in 140 Posts
Default

First of all, you have to find the *REAL* reason for the error.

And that means DEBUG DEBUG DEBUG.

Try using ON ERROR RESUME NEXT ... ON ERROR GOTO 0 around the possible problem lines and then report on the error found, if any.

If it's simply a matter of sending back too much data to the user, though, an easy answer is to call
RESPONSE.FLUSH
occasionally.

Something like this perhaps:
Code:
count = 0
DO Until RS.EOF
    ... output a bunch of stuff from that RS ...
    RS.MoveNext
    count = count + 1
    If count MOD 100 = 0 Then Response.Flush
Loop
You can adjust the number there (100) upwards or downwards. Upwards to get more efficiency but if you go too high then you'll get the buffer overflow error that is triggering the Error 500. Lower is you really are pumping out a ton of data from each record. But 100 is probably a nice handy starting number that should work for most pages.





Similar Threads
Thread Thread Starter Forum Replies Last Post
zxml - 500 internal server error mknopfler BOOK: Professional Ajax ISBN: 978-0-471-77778-6 1 June 2nd, 2008 02:17 AM
HTTP/1.1 500 Internal Server Error Dmitriy General .NET 0 February 26th, 2008 04:50 PM
Http/1.1 500 Internal Server Error abinashpatra ASP.NET 1.0 and 1.1 Basics 17 May 10th, 2007 02:06 AM
HTTP 500 - Internal server error helmsly BOOK: Beginning ASP 3.0 11 November 8th, 2006 03:15 AM
HTTP 500: Internal Server Error cyberddindia Classic ASP Databases 4 October 5th, 2006 11:36 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.