Article ID: 188352 - View products that this article applies to.
This article was previously published under Q188352
ASP caching in low memory situations may cause "Server Too Busy" errors and/or blank pages returned to client browsers. Memory usage by the Inetinfo process will be very high.
This problem occurs because too much data is being cached and the default number of ASP files to cache is set to unlimited in Internet Information Server (IIS) 4.0. ASP attempts to cache ASP files until the process runs out of virtual memory. The IIS computer stops processing pages and returns the "Server Too Busy" error or blank pages to client browsers.
Note that there are other causes of the "Server Too Busy" errors.
Windows NT Server or Workstation 4.0To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
Windows NT Server 4.0, Terminal Server EditionTo resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.
ASP has been modified to flush the cache when it receives an "Out of Memory" error. This enables it to recover gracefully. Please see the following paragraphs for information on how to do additional tuning of the ASP cache, so that it does not flush the ASP cache frequently, thus nullifying the benefits of caching.
Tune the AspScriptFileCacheSize (the number of ASP files to cache) settings for IIS. This setting is documented in IIS Help. The settings depend on a number of factors, including the amount of data in the server- side Include files and the number of ASP files that are cached. It is reasonable to start with a number like 250, and then monitor the ASP cache hit ratio using Performance Monitor. If it is below 90 percent, then raise the number. If it is above 90 percent, then any changes to the Web's pages can and will most likely change the tuning parameters.To change the ASP process options, do the following:
216383Some improvement can be made by increasing the per-process address space from 2 GB to 3 GB. For additional information, please see the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/216383/EN-US/ )Memory Allocations May Fail When There Are Large Free Blocks
171793Note that more physical RAM may be required to reduce possible paging after this change is made.Redesign the Web application. Disable ASP caching.
(http://support.microsoft.com/kb/171793/EN-US/ )Information on Application Use of 4GT RAM Tuning
Article ID: 188352 - Last Review: June 11, 2012 - Revision: 6.0