0

Need your help with an legacy ASP application hoisted on IIS 7. The application connects to oracle 10 and fetches data. If the rows exceed 500 then Internal Server 500 error is shown in the browser. How to overcome this ? Is there any logs I can check to fine out this error. Is there anything i need to do on timeout parameters.

Any pointers will be of great help.

Thanks a zillion.

µMax
  • 337
  • 1
  • 6
  • 15
  • 3
    Check this post for getting additional error information: http://stackoverflow.com/questions/1453791/classic-asp-on-iis7-refusing-to-send-errors-to-browser-on-500-internal-server-e – sgeddes Jan 17 '13 at 04:16
  • 1
    Also disable IE friendly error messages. – Shadow The GPT Wizard Jan 20 '13 at 09:45
  • 2
    If you are running IIS7 and want decent error messages, as well as disabling Friendly HTTP Error Messages, you need to go into IIS Manager, go to your website, in the ASP section go to: Compilation > Debugging Properties > Send Errors to Browser = True. This should make them a little more helpful:) – Hank Jan 21 '13 at 10:14
  • 3
    Also > Default Web Site —> Click Error Pages properties and select Detail errors – Hank Jan 21 '13 at 10:16

1 Answers1

0

If you have tried the methods above to see what kind of error you are getting and it is buffer related, then you need to increase the response buffer limit. in IIS 7, click on the website, click on ASP, click on limits properties, increase the response buffer limit and script time-out limit as well. Hope this helps.

Hamada
  • 146
  • 1
  • 8
  • Or, you can also add `response.flush` something in your code, like every 100 records. So, results are sent to the client before the entire page is generated. – DanB Oct 25 '18 at 14:17