PRB: Cannot Access COM+ Components in Application Center 2000 by Using ASP.NET (329580)



The information in this article applies to:

  • Microsoft Application Center 2000
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Internet Information Services version 6.0
  • Microsoft ASP.NET (included with the .NET Framework) 1.0
  • Microsoft ASP.NET (included with the .NET Framework 1.1)

This article was previously published under Q329580

SYMPTOMS

On a Windows Server 2003 computer, when you try to call a COM+ component that is deployed in Application Center 2000 component load balancing (CLB) in an ASP.NET Web application, you may receive one of the following error messages:
Permission Denied
-or-
Failed to query interface

WORKAROUND

To work around the problem:
  1. On the Internet Information Services (IIS) server, locate the processModel attributes section of the Machine.config file. The Machine.config file is located at %Windows folder%\Microsoft.NET\Framework\v1.x.yyyy\Config\Machine.config, where v1.x.yyyy is the version of the .NET Framework.
  2. Use one of the following options to set the userName and password values:
    • Set the userName and password values to use a domain account.
    • Use a local account that is common to all the computers used for the application.
    • Set userName to "SYSTEM" and password to "AutoGenerate". When you do this, ASP.NET behaves similar to Active Server Pages (ASP) on Microsoft Windows 2000 when the System account is used.

MORE INFORMATION

This problem may also occur when you access a COM+ component by using ASP.NET from the Windows 2000 operating system with the .NET Framework installed. When an ASP.NET application tries to create a component remotely, ASP.NET tries to impersonate one of the following users:
  • On Windows 2003 Server, when IIS 5.0 is not running in Isolation mode, ASP.NET uses the Application Pool user.
  • On Windows 2003 Server with IIS 5.0 running in Isolation mode, or on Windows 2000 with the .NET Framework installed, the user information is read from the Machine.config file.

Modification Type:MajorLast Reviewed:5/15/2003
Keywords:kbSecurity kberrmsg kbprb KB329580 kbAudDeveloper