Skip to main content

Response buffer limit exceeded

Error message when a Web browser sends a request for an active server page to a Web server that is running IIS 6.0: "Response buffer limit exceeded"

Response object error 'ASP 0251 : 80004005'
Response Buffer Limit Exceeded
/PageName.asp, line LineNumber


CAUSE
This issue occurs because of a change in behavior that was introduced in IIS 6.0 and added to IIS 5.0. These versions of IIS enforce a default ASP response buffer limit of 4 MB. This limit prevents large ASP responses from adversely affecting the IIS process that hosts the Web application. If an ASP request generates a response that is larger than the configured buffer limit, you experience the symptoms that are mentioned in the "Symptoms" section.


Method 4: Increase the buffer limit

You can increase the buffering limit if one of the following conditions is true:
• The client is not a Web browser.
• You cannot redesign the application to take advantage of a paging technology, such as the GridView class.
If you must increase the buffer limit, select a buffer limit that allows for the largest known response size. If you do not know the largest response size in advance, you can increase the buffer limit to a large value during testing. After you finish testing, use the largest value that is in the sc-bytes field in the IIS log file for the response that is generated for the page.

To increase the buffering limit, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command, and then press ENTER:
cd /d %systemdrive%\inetpub\adminscripts
3. 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:
1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command, and then press ENTER:
cd /d %systemdrive%\inetpub\adminscripts
3. Type the following command, and then press ENTER:
cscript.exe adsutil.vbs GET w3svc/aspbufferinglimit

Popular posts from this blog

Android Developer Learning Resource

Developing In Eclipse, with ADT http://developer.android.com/guide/developing/eclipse-adt.html Signing Your Applications http://developer.android.com/guide/publishing/app-signing.html Compile and sign with Eclipse ADT To create a signed and aligned .apk in Eclipse: Select the project in the Package Explorer and select File > Export . Open the Android folder, select Export Android Application, and click Next . The Export Android Application wizard now starts, which will guide you through the process of signing your application, including steps for selecting the private key with which to sign the .apk (or creating a new keystore and private key). Complete the Export Wizard and your application will be compiled , signed , aligned , and ready for distribution. DroidDraw is a graphical user interface (GUI) builder for the Android platform http://code.google.com/p/droiddraw/

RMO programming

http://msdn2.microsoft.com/en-us/library/ms151819.aspx SQL Server Express does not include SQL Server Agent, which is typically used to run replication agents. If you use a pull subscription (in which agents run at the Subscriber), you must synchronize the subscription using Windows Synchronization Manager or RMO. For more information, see the following topics: Windows Synchronization Manager RMO programming: How to: Synchronize a Pull Subscription (RMO Programming) Replication does not support the Run As Normal User (RANU) feature of SQL Server Express. For more information about this feature, see the SQL Server Express documentation.