This is actually a really bad idea. Placing the ASPNET user in the
administrators group basically means that any code that runs on the web
server under default ASP.NET settings is going to have administrative
rights.
That's a disaster waiting to happen.
Rather, impersonate with a specified account in the web.config file, or
register the COM component in a COM+ application, indicating the account it
should run under, and then access from ASP.NET.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Seraph Jiang" <Se*********@gmail.com> wrote in message
news:Oq*****************@TK2MSFTNGP10.phx.gbl...
Did you check if the ASP.Net account had been added to Administrators
group.
The com may use some methodes need admin privilege.
And if it still doesn't work, you can try impersonate with a specified
account to lauch web app.
config impersonate parameter in you web.config file
<hi******@gmail.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com... Hi Everybody,
I designed a com controller and i'm calling the com component from the
webservice. It works perfectly in windows 2000. But it throws error in
Windows 2003 during the instantiation of the COM component.
The error is
System.UnauthorizedAccessException: Access is denied. at
System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) at
System.Activator.CreateInstance(Type type, Boolean nonPublic) at
ACDR.Service1.InvokeDiadem(String strJobId, String strRequestor, String
strType, String strTestName, String strRunNumber, String strFileName)
Please help....
Thanks,
Raj