FIX: The Server.Transfer method causes a stack overflow and causes the ASP.NET worker process to stop responding

Note Microsoft Visual C++ .NET 2002 and Microsoft Visual C++ .NET 2003 support both the managed code model that is provided by the Microsoft .NET Framework and the unmanaged native Microsoft Windows code model. The information in this article applies only to unmanaged Visual C++ code.When you run a Web-based application that is based on the Microsoft .NET Framework 1.1, you receive an error message when the following conditions are true:

• Your Web-based application calls the Server.Transfer method to transfer to the same page.
• You are sending a POST request through the Server.Transfer method.
• You have applied the hotfix that is described in Microsoft Knowledge Base article 837132 or a later version of the hotfix.

The following is the error message that you receive:After you receive the error message, the ASP.NET worker process stops responding.

This problem occurs because the Server.Transfer method loops back to the same page until all the stack space is exhausted. The Server.Transfer method loops back to the same page because the query string is preserved between each POST request.

Service pack information

The issue that is listed in the "Symptoms" section when calling the Server.Transfer(same page) method with no additional parameters is addressed by installing this service pack.

Note When you call Server.Transfer(same page, true) without additional code, a stack overflow occurs. This behavior is by design. When you need both forms and query data, see the table in the "More Information" section of this article for guidance about how to handle this situation. To avoid this error, add code that is similar to the following:

Visual C# .NETVisual Basic .NET

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this software update.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This hotfix introduces some new behavior in the Server.Transfer method. The following table describes the results that occur when you send a POST request through the Server.Transfer method by using different parameters.

Steps to reproduce the problem

1. Install the hotfix that is described in Microsoft Knowledge Base article 837132, or a later version of the hotfix.
2. In Microsoft Visual Studio .NET, create a new Visual Basic ASP.NET Web Application project.
3. Click Button in the Toolbox, and then draw a button on the WebForm1.aspx page. Name the new button Button1.
4. Double-click Button1, and then add the following code to the Button1_Click event:

   If IsPostBack() Then
       Server.Transfer("WebForm1.aspx")
   End If
   

5. Run the solution, and then click Button1.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: For additional information, click the following article number to view the article in the Microsoft Knowledge Base: