Service Component in ASP.NET (No Such Interface Supported)

  • Thread starter Thread starter Abid Ali
  • Start date Start date
A

Abid Ali

hi all,

i have developed a serviced componenet which being successfully accessed in
windows application. but when I access this component from ASP.NET it fails
at the time
of initialization and gives error.

"No such interface is supported"

any idea or suggesstion will be highly appreciated

Abid Ali
 
It could be a security issue. A component or registry key is available
to the user running the windows application but not to the ASP.NET
worker process account. You could try identity impersonate="true" in
the web.config to see if it helps.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Serviced Component and ASP.NET 2
Project properties -> References error 1
writing COM controls to work in ASP.NET 1
IE "no such interface supported" 1
Using .NET 2.0/3.0 component in ASP.NET 1.1 6
Simple web Iterface for Window Services, Or start Process from IIS? 1
Debugger (No Such Interface Supported?) 4
ASP.NET and COM interop/security issue.. ('NullReferenceException') 1

Back
Top