Phil Wilson
11/8/2007 8:03:00 PM
I think that's the kind of type initialization error that you get when code
in the constructor fails, so that's where I'd look.
--
Phil Wilson
[MVP Windows Installer]
"Mark" <mmodrall@nospam.nospam> wrote in message
news:F281914B-D767-4B3E-A430-1A3E22915B07@microsoft.com...
> Hi...
>
> One of my colleagues is have a problem that's driving him crazy.
>
> We have a number of assemblies that expose some C# objects as COM. One
> particular one is throwing an 80131534 error on instantiation from an ASP
> page. The error message doesn't really say diddly about what it doesn't
> like, just that it can't make one of those objects.
>
> We checked the registry, and it looks like it's registered fine. He made
> a
> little vbs script instantiating one of the objects and ran it from cmd,
> and
> that worked fine, so it seems like the plumbing is okay in general.
>
> But we're at a loss why ASP is having trouble instantiating one of these.
> Does the old asp engine have a shadow cache somewhere that it could be
> wedged?
>
> Thanks
> Mark
>