Resolution of the IIS6 ASP page execution causing the response buffer to exceed its configuration limits

  • 2020-05-14 05:29:02
  • OfStack

Response object error 'ASP 0251:80004005 '

Exceeds the response buffer limit

The execution of this ASP page caused the response buffer to exceed its configuration limit.

Because there is so much data in the page, there are thousands of them, resulting in "exceeding the response buffer limit." The execution of this ASP page caused the response buffer to exceed its configuration limits.
If response.buffer =false, you can check it, but it's slow. How to solve ?

We can increase the buffer of Buffer by turning off the iisadminservice service in the service first.

Find windows\system32\inesrv\ metabase.xml, open, find AspBufferingLimit and change it to the desired value, the default is 4194304, i.e. 4096KB, 4M.

It is recommended to change it to 41943040 (40M) or the appropriate value, depending on whether the server memory is large enough.

Then restart the iisadminservice service.

Matters needing attention:

1, to pay attention to the server memory is enough.
2. In addition, due to the large amount of data, the processing time of ASP needs to be modified accordingly, that is:
Modify the default value of "AspScriptTimeout" 90 (seconds)
Change the default value of "AspSessionTimeout" to 20 minutes.
3. When running IIS, the metabase.xml file under windows\system32\inesrv\ was locked. The modification cannot be saved
net stop iisadmin, save OK, net start w3svc.
4. The metabase.xml file in win7 cannot be copied or modified, so you can directly set the modification in iis. The location is iis-- function view --asp-- limit property -- response buffer limit and maximum request entity body limit.


Related articles: