FIX: ASP.NET Session variables are incorrectly accessible between applications when you use SQLServer Session Mode

Retired KB Content Disclaimer

View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

Under certain circumstances, you can share session variables between applications when you use SQLServer session mode.

Back to the top

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 .NET Framework 1.0 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:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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.

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
   -------------------------------------------------------------
   17-Jun-2003  01:18  1.0.3705.435    200,704  Aspnet_isapi.dll
   17-Jun-2003  01:13                    4,169  Aspnet_perf.h
   17-Jun-2003  01:18                  513,302  Aspnet_perf.ini
   17-Jun-2003  01:18                  510,714  Aspnet_perf2.ini
   17-Jun-2003  01:18  1.0.3705.435     28,672  Aspnet_rc.dll
   17-Jun-2003  01:18  1.0.3705.435     24,576  Aspnet_regiis.exe
   17-Jun-2003  01:18  1.0.3705.435     28,672  Aspnet_wp.exe
   17-Jun-2003  00:26  1.0.3705.435  1,953,792  Mscorlib.dll
   17-Jun-2003  00:36  1.0.3705.435  2,269,184  Mscorsvr.dll
   17-Jun-2003  00:35  1.0.3705.435  2,269,184  Mscorwks.dll
   01-Aug-2002  21:38                       15  Smartnav.htm
   17-Oct-2002  17:55                    8,728  Smartnav.js
   17-Jun-2003  01:26  1.0.3705.435  1,196,032  System.web.dll

Back to the top

STATUS

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

Back to the top

MORE INFORMATION

For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

Back to the top

APPLIES TO

Microsoft ASP.NET 1.0

Back to the top

kbhotfixserver kbqfe kbqfe kbnetframe100presp3fix kbfix kbbug KB822162

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top