[RESOLVED] CLSID Is different from registered dll?

This is somewhat of a strange issue. I'm attempting to reference a COM object in a VB.Net application and keep receiving...

"COM object with CLSID {01704EBF-44B5-11D3-9C09-00105A3DD3AC} is either not valid or not registered."

...whenever I try to create an object. I checked my registry to see if it actually was registered and it was. The thing is, the CSLID in my registry is

"{01704EBD-44B5-11D3-9C09-00105A3DD3AC}"
(the last digit of the first section is different)

Now I realize that D and F are really close together and I could have possibly mixed it up. So just to be on the safe side, I unregistered and tried again. Each time I register this component, it always has the same issue.

Can someone pleae shed some light on what I need to do here? I tried forcing the registry to reflect what my referencing app is looking for (not for a permanant fix, but just for debugging reasons), and it still doesn't like it.

Don't know much about .net but I suspect it's the interop stuff . . .

Quote:

---

Originally Posted by sevenhalo

This is somewhat of a strange issue. I'm attempting to reference a COM object in a VB.Net application and keep receiving...

"COM object with CLSID {01704EBF-44B5-11D3-9C09-00105A3DD3AC} is either not valid or not registered."

...whenever I try to create an object. I checked my registry to see if it actually was registered and it was. The thing is, the CSLID in my registry is

"{01704EBD-44B5-11D3-9C09-00105A3DD3AC}"
(the last digit of the first section is different)

Now I realize that D and F are really close together and I could have possibly mixed it up. So just to be on the safe side, I unregistered and tried again. Each time I register this component, it always has the same issue.

Can someone pleae shed some light on what I need to do here? I tried forcing the registry to reflect what my referencing app is looking for (not for a permanant fix, but just for debugging reasons), and it still doesn't like it.

---

You may be looking at the IID, and not the CLSID. There are many, many GUID's associated with the interfaces, the coclases, and the class itself.

Have you tried to use a registry cleaner then reregistering?

If this doesn't work then it can only be one of two things. The interop code, or the code in the COM component self-registrarion is corrupt (which is VERY VERY unlikely)

Thanks for the reply.

Unfortunately, I have no idea what's going on with this anymore :)

I ran into a few more issues trying to get this interop stuff to work. I gave up and found an alternative solution (crappy as that sounds). I apologize for not resolving sooner.