Hi all,
has anyone been successful in forcing impersonation of the ASPNET
account that calls a component through com interop? I have tried doing
it programmatically, through IIS, through the web config file and all
do not work. The ASPNET account always seems to access my com
components.  I have a .net web service trying to call a com+ component
programmed in VB6.
thanks in advance

Hi,
I am not absolutely sure, but I think impersonation account is not delegated 
to COM+ components. You can only use this account to distinguish if user is 
allowed to run your component.

Regards,
Ladislav

"esource" wrote:


> Hi all,
> has anyone been successful in forcing impersonation of the ASPNET
> account that calls a component through com interop? I have tried doing
> it programmatically, through IIS, through the web config file and all
> do not work. The ASPNET account always seems to access my com
> components.  I have a .net web service trying to call a com+ component
> programmed in VB6.
> thanks in advance
> 
>