Comments by Fingerstyler (Top 8 by date)

I have meticulously imported all the keys etc throughout the registry that i manually created to look just like a class that works. This was several .reg files. The .net app still produces the same error as in beginning "80040154". This is more puzzling because now at least the CLSID exists, but so do all other keys/data. I was expecting it to work or prodcue a new error. What's next....is there anything next?

Thanks barneyman, i just don't 100% understand what i'm seeing with dependency walker and the procmon, but what i do notice is that each class in the COM and .net have interface registered and coclass that is not registered. There are several like this where the first uuid of the interface is in the registry, the coclass uuid is not (henceforth no objects of those classes can be created). Is that any help?

<pre> [
odl,
uuid(F86DE170-2A5B-11CF-A2A6-08005AC10759),
helpstring("ICALWorkitemWorkstepList Interface"),
dual,
oleautomation
]
interface _ICALWorkitemWorkstepList : IDispatch {
[id(0x80013001), propget]
HRESULT Count([out, retval] long* retval);
[id(0xfffffffc), propget]
HRESULT _NewEnum([out, retval] IUnknown** retval);
[id(0x80013002), propget]
HRESULT Item(
[in] long lOrdinal,
[out, retval] _ICALEnumItem** retval);
};
[
uuid(F86DE171-2A5B-11CF-A2A6-08005AC10759)
]
coclass CALWorkitemWorkstepList {
[default] interface _ICALWorkitemWorkstepList;
};</pre>

If that is true, is there anymore that i can do?

1. i found the CLSID of the dll that i beleive hosts the class, however,
2. when i run the process monitor:
a. VB6 app with cmdBotton that does no more than "Dim mycalWWList As New CALWorkitemWorkstepList" - i was expecting another registry read in HKCR\CLSID but nothing more appears in that path filter of HKCR\CLSID for process montitor.

b. VB.net app with cmdBotton that does no more than "Dim mycalWWList As New CALWorkitemWorkstepList" - right away shows registry result NAME NOT FOUND. Then of course the 80040154 error.