You may receive an AuthManager initialization exception when you visit an ASP site and an ASP.NET site (831212)
The information in this article applies to:
- Microsoft Commerce Server 2002
SYMPTOMS When you visit an Active Server Pages (ASP) site, such as the Microsoft Commerce Server 2000 retail site, and a Microsoft ASP.NET site, such as the Commerce Server 2002 retail site, that are on the same server, you may receive an AuthManager initialization exception. CAUSEThis problem occurs on computers that are running Microsoft Internet Information Services (IIS) 6.0 if the ASP site code resides on the same computer as the ASP.NET site code. AuthManager checks to see if there is an ASP context or an ASP.NET context at initialization, and then caches the result. When both sites reside in the same application pool, the sites run in the same process. The first AuthManager initialization call is successful. If the ASP site (the Commerce Server 2000 retail site, for example) is hit first, AuthManager assumes that there is an ASP context, and then fails in ASP.NET context.RESOLUTIONHotfix informationA 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 Commerce Server 2002 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. PrerequisitesNo prerequisites are required. Restart requirementAfter you install this hotfix, run the IISReset command at a command prompt Hotfix replacement informationThis hotfix does not replace any other hotfixes. File information
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
--------------------------------------------------------------
22-Oct-2003 19:39 4.5.3340.0 192,997 Mscsauth.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.WORKAROUNDTo work around this problem, separate the ASP site and the ASP.NET site in different application pools. The compatibility mode in IIS 5.0 also provides a Dllhost process so that the ASP code can operate separately.
Modification Type: | Minor | Last Reviewed: | 10/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbHotfixServer kbQFE kbBug kbfix kbCommServ2002preSp3fix KB831212 |
---|
|