> I'm attempting to instantiate and use a COM component that was built with
VB
> 6 within an ASP.Net page written with VB.Net. The component leverages COM+
> services and runs in an application that is a library app. I've used the
> tlbimp.exe tool to generate a strongly-named assembly out of this
component.

> I'm able to instantiate and use the resultant assembly just fine when
> leveraging a Windows form application built with VB.Net, however when
> attempting to use the assembly through ASP.Net, the following exception is
> thrown:

>     System.Runtime.InteropServices.COMException: ActiveX component can't
> create object

> This would be old general-purpose "can't create the component" hresult
> of -2146827859. Intellisense don't complain about anything I've done and I
> can complie and run just fine. The actual declaration and instantiation of
> the component doesn't cause an issue, but the first use of a method of the
> throws the exception.

> The same behavior occurs if I attempt to leverage the original component
in
> ASP.Net (without creating a strongly-named assembly).

> Are there known issues with the interoperability of ASP.Net/VB.Net and
> legacy COM components?

> Software profile:
>     .Net Framework version 1.0.3705.288
>     Windows 2000 Server SP3 (+ up to date QFE's)
>     VS.Net 7.0.9466

> Regards,

> KS