Re: InvalidCastException Using AzMan from ASP.NET
From: Ying-Shen Yu[MSFT] (v-yiy_at_online.microsoft.com)
Date: 02/06/04
- Next message: Swati: "Re: regasm and .NET framework versions"
- Previous message: Pradeep M M: "Capture Ctrl+Alt+Del"
- In reply to: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Next in thread: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Reply: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Reply: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 06 Feb 2004 11:50:22 GMT
Hi Chris,
Thanks for the detail information.
80004002(E_NOINTERFACE) might be caused by many issues, however mostly the
error was caused by
threading model mismatch or permmision denied.
First I'd like you check the sample in this article,
<Role-Based Access Control for Multi-tier Applications Using Authorization
Manager>
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/windowsserver2003/maintain/security/athmanwp.asp
especially make sure you are running the application server in a service
account. To configure your ASP.NET application server to run in a service
account, you create a separate IIS 6.0 worker process which runs in the
security context of the service account created for the application server.
You can then configure your ASP.NET application to use this dedicated IIS
worker process. For more information on IIS 6.0 worker processes, see the
Microsoft Internet Information Services page on the Microsoft Web site at
http://www.microsoft.com/technet/prodtechnol/iis/default.asp.
Alternatively, you can use ASP.NET to configure the context in which an
application runs using the Web.config file for your ASP.NET application. In
that case, you should configure the ASP.NET application to run as the
dedicated service account.
In Addition, I'd like you try turning on the ASP Compatibility mode, add
the aspcompat=true attribute to the Page Directive. Adding this attribute
accomplishes two things:
1) ASP.NET uses Single-Threaded Apartment (STA) threads when accessing the
COM component. The default is to use Multi-Threaded Apartment, or MTA,
threading.
2) ASP.NET provides access to the ASP-intrinsic objects in a
backward-compatible fashion.
Also, just to confirm does this problem also occur if deployed your program
on some other windows 2003 servers?
Thanks!
Best regards,
Ying-Shen Yu [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, "online" should be removed before
sending.
- Next message: Swati: "Re: regasm and .NET framework versions"
- Previous message: Pradeep M M: "Capture Ctrl+Alt+Del"
- In reply to: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Next in thread: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Reply: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Reply: Chris Bilson: "Re: InvalidCastException Using AzMan from ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|