FIX: You experience high memory usage in the W3wp.exe process on a Windows Server 2003-based computer that has Internet Information Services (IIS) 6.0 installed

Article translations Article translations
Article ID: 916984 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

You experience high memory usage in the W3wp.exe process on a Microsoft Windows Server 2003-based computer that has Microsoft Internet Information Services (IIS) 6.0 installed.

This problem occurs during the transfer of a large HTTP response that is generated by an Active Server Pages (ASP) application to a client computer. An example of an ASP method that can generate this large HTTP response is the Response.BinaryWrite method. The memory usage in the W3wp.exe process may be as high as the size of the whole HTTP response that is being transferred. Typically, this problem occurs when the client computer uses a slow connection link.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Windows Server 2003 Service Pack 1 installed to apply this hotfix.

Restart requirement

If the Asp.dll file is being used when you apply this hotfix, you must restart the computer after you apply this hotfix.

If you do not want to restart the computer after you apply this hotfix, stop all IIS services before you apply this hotfix. To stop all IIS services, type Iisreset /stop at a command prompt, and then press ENTER.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003, Itanium architecture
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Asp.dll6.0.3790.26711,063,93630-Mar-200605:44
Wasp.dll6.0.3790.2671379,39230-Mar-200605:44
Windows Server 2003, x64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Asp.dll6.0.3790.2671611,32830-Mar-200605:44
Wasp.dll6.0.3790.2671379,39230-Mar-200605:44
Windows Server 2003, x86
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Asp.dll6.0.3790.2671379,39230-Mar-200606:22

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

MORE INFORMATION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows


In IIS 6.0, an ASP Web application uses asynchronous writes to the Http.sys file to transfer data to a client computer. If the client computer uses a slow connection and slowly retrieves the requested data, the data is queued in memory on the Web server.

After you apply this hotfix, you can configure the number of bytes that can be queued in memory. If the limit that you configure is reached, the file transfer is paused until the client computer retrieves enough data so that the amount of queued data is lower than the configured limit.

Important This hotfix only affects ASP applications. This hotfix does not affect Microsoft ASP.NET applications.

To limit the amount of data that can be queued in the W3wp.exe file, follow these steps:
  1. Apply the hotfix that is described in this article.
  2. Click Start, click Run, type regedit, and then click OK.
  3. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP\Parameters
  4. If the
    VectorSendThrottleLimit
    subkey exists, go to step 7. If the
    VectorSendThrottleLimit
    subkey does not exist, go to step 5.
  5. On the Edit menu, point to New, and then click DWORD Value.
  6. Type VectorSendThrottleLimit, and then press ENTER.
  7. In the right pane, right-click VectorSendThrottleLimit, and then click Modify.
  8. In the Value data box, type the value that you want, and then click OK.
Warning If you set the
VectorSendThrottleLimit
subkey to a value that is less than the amount of data that an ASP page sends to a client, IIS stops responding (hangs). For example, if you set the
VectorSendThrottleLimit
subkey to 1000, any ASP page that transfers more than 1000 bytes is not dispayed in the client browser. Additionally, the IIS thread that handles the request is blocked until you restart the IIS service.

Note By default, this feature is disabled, and the
VectorSendThrottleLimit
subkey does not exist. When this feature is disabled, the value for this subkey is 0.

Properties

Article ID: 916984 - Last Review: October 9, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft Internet Information Services 6.0
Keywords: 
kbautohotfix kbwinserv2003sp2fix kbHotfixServer kbfix kbbug kbqfe KB916984

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com