COM interop failing for asp.net only.

[GazDev]

We have a COM object which we need to call from an asp.net application but it doesn't work. I know about COM interop and references and tlbimp etc. When I say "doesn't work" I mean that the methods of the com object fail - we haven't managed to debug it yet so we don't know exactly where it fails.

The COM component works fine from a c# windows application but not from a c# asp.net application. If it helps, the COM component extensively uses SQL via ado, amongst many other things. It is a large object model.

Is it something to do with permissions that prevents it from working in an asp.net environment? As I said, it works fine in a normal c# windows app.

Finally, if I register the component in COM+ the situation is improved but we still have big problems with the cOM component not being suitable to be run out of process.

This is driving us nuts please help.

Gaz.

[neel_09]

I know this is an age old topic, but does anyone have a solution to this? I am facing the same problem here. I can access a components method in a normal winforms app, also through javascript on a web app page, but is there a way to achieve this on the server side?