Re: Random occurance of 0x8002801D (Re-phrasing the problem)
Check whether your server registers it for you. E.g. check the
arguments to RegisterClassObjects. The last argument should
be FALSE to avoid registering a bundled type library. No idea
who unregisters it, however. BTW, #import may also be registering
the TLB, I'm not sure. Depends which function it uses to load
the type library. Not an issue in production obviously...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================
"Dilip" <rdilipk@lycos.com> wrote in message
news:1159802982.454804.81530@h48g2000cwc.googlegroups.com...
Alexander Nickolov wrote:
Both your proxy/stub DLL and the type library offer marshaling
support for your dual interfaces. It depends what you register
last. Based on the error you get I'd assume the type library is
registered after the proxy/stub DLLs and takes over the marshaling
support for your dual interfaces. If it is subsequently unregistered,
your dual interfaces would have no marshaling support. However,
if after that the type library is registered again, the marshaling
support would magically reappear.
Thanks for the response. Unfortunately I do not register the type
library at all. I only register the proxy/stub DLL. The only reason I
use the TLB is during compile time so that the client can simply
#import it in code and generate the necessary .tlh/.tli files. That is
why I am finding it hard to understand why I sometimes get that
insanely random 'Library Not Registered' error.