Response Buffer Limit Exceeded

Question

I am running a simple query to get data out of my database  amp  display them  I m getting an error that says Response Buffer Limit Exceeded       Error is   Response object error  ASP 0251   80004005    Response Buffer Limit Exceeded    abc test maintenanceDetail asp  line 0   Execution of the ASP page caused the Response Buffer to exceed its configured limit     I have also tried Response flush in my loop and also use response buffer   false in my top of the page  but still I am not getting any data   My database contains 5600 records for that  Please give me some steps or code to solve the issue

User · Answer

One other answer to the same error message (this just fixed my problem) is that the System drive was low on disk space. Meaning about 700kb free. Deleting a lot of unused stuff on this really old server and then restarting IIS and the website (probably only IIS was necessary) cause the problem to disappear for me.

I'm sure the other answers are more useful for most people, but for a quick fix, just make sure that the System drive has some free space.

User · Answer

I know this is way late  but for anyone else who encounters this problem   If you are using a loop of some kind  in my case  a Do-While  to display the data  make sure that you are moving to the next record  in my case  a rs MoveNext

User · Answer

It can be due to CursorTypeEnum also  My scenario was the initial value equal to CursorTypeEnum adOpenStatic 3  After changed to default  CursorTypeEnum adOpenForwardOnly 0  it backs to normal

User · Answer

In my case i just have writing this line before rs Open        Response flush  rs Open query  conn

User · Answer

I rectified the error  ASP 0251   80004005  Response Buffer Limit  as follow   To increase the buffering limit in IIS 6  follow these steps   Click Start  click Run  type cmd  and then click OK  Type the following command  and then press ENTER  cd  d  systemdrive  inetpub adminscripts Type the following command  and then press ENTER  cscript exe adsutil vbs SET w3svc aspbufferinglimit LimitSize Note LimitSize represents the buffering limit size in bytes  For example  the number 67108864 sets the buffering limit size to 64 MB  To confirm that the buffer limit is set correctly  follow these steps   Click Start  click Run  type cmd  and then click OK  Type the following command  and then press ENTER  cd  d  systemdrive  inetpub adminscripts Type the following command  and then press ENTER  cscript exe adsutil vbs GET w3svc aspbufferinglimit  refers to https   support microsoft com en-us kb 944886

User · Answer

You can increase the limit as follows    Stop IIS  Locate the file  WinDir  System32 Inetsrv Metabase xml Modify the AspBufferingLimit value  The default value is 4194304  which is about 4 MB  Changing it to 20MB  20971520   Restart IIS

User · Answer

Here is what a Microsoft support page says about this  https   support microsoft com en-us help 944886 error-message-when-you-use-the-response-binarywrite-method-in-iis-6-an  But it   s easier in the GUI   In Internet Information Services  IIS  Manager  click on ASP  Change Behavior   gt  Limits Properties   gt  Response Buffering Limit from 4  MB to 64  MB  Apply and restart

User · Answer

Thank you so much    lt  Response Buffer   False   worked like a charm   My asp HTML table that was returning a blank page at about 2700 records  The following debugging lines helped expose the buffering problem  I replace the Do While loop as follows and played with my limit numbers to see what was happening    Replace   Do While not rs EOF   etc      your block of code that writes the table rows  rs moveNext   Loop  with   Do While reccount  lt  2500  if  rs EOF then recount   2501    etc      your block of code that writes the table rows  rs moveNext   Loop  response write  recount      amp  recount  raise or lower the  2500 and 2501 to see if it is a buffer problem  for my record set  I could see that the blank page return  blank table  was happening at about 2700 records  good luck to all and thank you again for solving this problem  Such a simple great solution

User · Answer

I faced the same kind of issue  my IIS version is 8 5  Increased the Response Buffering Limit under the ASP - gt  Limit Properties solved the issue    In IIS 8 5  select your project  you can see the options in the right hand side  In that under the IIS  you can see the ASP option       In the option window increase the Response Buffering Limit to 40194304  approximately 40 MB         Navigate away from the option  in the right hand side top you can see the Actions menu  Select Apply  It solved my problem

User · Answer

The reason this is happening is because buffering is turned on by default  and IIS 6 cannot handle the large response    In Classic ASP  at the top of your page  after  lt   Language  VBScript   gt  add   lt  Response Buffer   False  gt   In ASP NET  you would add Buffer  False  to your Page directive   For example   lt   Page Language  C   Buffer  False   gt

User · Answer

If you are looking for the reason and don t want to fight the system settings  these are two major situations I faced    You may have an infinite loop without next or recordest movenext Your text data is very large but you think it is not  The common reason for this situation is to copy-paste an Image from Microsoft word directly into the editor and so the server translates the image to data objects and saves it in your text field  This can easily occupies the database resources and causes buffer problem when you call the data again

User · Answer

If you are not allowed to change the buffer limit at the server level  you will need to use the  lt  Response Buffer   False   method   HOWEVER  if you are still getting this error and have a large table on the page  the culprit may be table itself  By design  some versions of Internet Explorer will buffer the entire content between  before it is rendered to the page   So even if you are telling the page to not buffer the content  the table element may be buffered and causing this error   Some alternate solutions may be to paginate the table results  but if you must display the entire table and it has thousands of rows  throw this line of code in the middle of the table generation loop    lt   Response Flush     For speed considerations  you may also want to consider adding a basic counter so that the flush only happens every 25 or 100 lines or so     Drawbacks of not buffering the output    slowdown of overall page load tables and columns will adjust their widths as content is populated  table appears to wiggle  Users will be able to click on links and interact with the page before it is fully loaded   So if you have some javascript at the bottom of the page  you may want to move it to the top to ensure it is loaded before some of your faster moving users click on things    See this KB article for more information http   support microsoft com kb 925764  Hope that helps

[asp-classic] Response Buffer Limit Exceeded

Examples related to asp-classic

Examples related to buffering