Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You may receive an AuthManager initialization exception when you visit an ASP site and an ASP.NET site

You may receive an AuthManager initialization exception when you visit an ASP site and an ASP.NET site

View products that this article applies to.

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.

↑ Back to the top

Cause

This 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.

↑ Back to the top

Resolution

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

No prerequisites are required.

Restart requirement

After you install this hotfix, run the IISReset command at a command prompt

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) 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

↑ 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.

↑ Back to the top

Workaround

To 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.

↑ Back to the top

More information

When you visit the Commerce Server 2000 retail site after you visit the Commerce Server 2002 retail site by using Microsoft Internet Explorer, you may receive the following exception when this error condition occurs:
	
Commerce.AuthManager.1 (0x80004003)
	AuthManager(CommerceServer): Initialization of ASP objects failed.
	/retail/include/std_access_lib.asp, line 309

When you visit the Commerce Server 2000 retail site before you visit the Commerce Server 2002 retail site, you may receive the following exception:
	AuthManager (CommerceServer): API should be called only from ASP
[COMException (0xc1004c24): AuthManager (CommerceServer): API should be called only from ASP.]
   Microsoft.CommerceServer.Interop.AuthManagerClass.IsAuthenticated(Int32 TimeWindow) +0
   Microsoft.CommerceServer.Runtime.AuthManager.IsAuthenticated(Int32 timeWindow) +50

[CommerceAuthenticationException: Failed to authenticate.]
   Microsoft.CommerceServer.Runtime.AuthManager.IsAuthenticated(Int32 timeWindow) +143
   SVTNet.C_additem.Page_Load(Object sender, EventArgs e) in d:\inetpub\wwwroot\SVTNetX\_additem.aspx.cs:62
   System.Web.UI.Control.OnLoad(EventArgs e) +67
   System.Web.UI.Control.LoadRecursive() +35
   System.Web.UI.Page.ProcessRequestMain() +714
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: KB831212, kbcommserv2002presp3fix, kbfix, kbbug, kbqfe, kbhotfixserver, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 831212
Revision : 7
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 335