FIX: Requests Are Incorrectly Treated as Non-Postback Requests

This article has been archived. It is offered "as is" and will no longer be updated.
Requests are incorrectly treated as non-postback requests. When this behavior occurs, you may experience the following problems:
  • Postback events do not fire.
  • The IsPostBack property returns false.
When you batch compile a page, the namespace _ASP is used for the resulting assembly. When you do not batch compile a page, the namespace ASP is used for the resulting assembly. If a user requests a page that is contained in the namespace _ASP, and then the page is modified and the user is posted back, the namespace might change to ASP when the page is recompiled.

Because the namespace is different, the Control tree for the second request does not match the original Control tree. This problem causes ASP.NET not to interpret the request as a postback. ASP.NET determines that a request is a postback request based on the following conditions:
  • Request.Forms or Request.QueryString collection is not empty
  • Page Control tree has not changed
  • Not the initial request
Note This problem occurs most frequently in Web farm scenarios.

How to Obtain the Hotfix

This issue is fixed in the June 2003 ASP.NET Hotfix Package 1.1. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
821156 INFO: ASP.NET 1.1 June 2003 Hotfix Rollup Package
You cannot obtain this fix individually. You must install the rollup.

Note When you request this hotfix, you receive the rollup. The English version of this hotfix has the file attributes (or later) 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.
	           Date         Time   Version       Size       File name		   -----------------------------------------------------------------------		   07-Jun-2003  00:44  1.1.4322.910    253,952  Aspnet_isapi.dll		   07-Jun-2003  00:44  1.1.4322.910     20,480  Aspnet_regiis.exe		   07-Jun-2003  00:44  1.1.4322.910     32,768  Aspnet_wp.exe		   15-May-2003  23:49                   33,522  Installpersistsqlstate.sql		   15-May-2003  23:49                   34,150  Installsqlstate.sql		   07-Jun-2003  12:52  1.1.4322.910  1,216,512  System.dll		   07-Jun-2003  00:39                   14,472  Webuivalidation.js		   07-Jun-2003  12:52  1.1.4322.910  1,249,280  System.Web.dll

If you applied the hotfix in this article for Microsoft ASP.NET included with the .NET Framework 1.0, and if you upgraded to Microsoft ASP.NET included with the .NET Framework 1.1, apply the hotfix package from the following Microsoft Knowledge Base article:
821156 INFO: ASP.NET 1.1 June 2003 Hotfix Rollup Package
Additionally, if you upgraded to the .NET Framework 1.1, and if you experience the symptoms in this article, apply the hotfix package from this Microsoft Knowledge Base article.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 818537 - Last Review: 02/27/2014 21:18:33 - Revision: 4.3

Microsoft .NET Framework 1.0, Microsoft ASP.NET 1.0

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbnetframe100presp3fix kbfix kbbug KB818537