Bill,good site

Bill — Sun, 13 May 2007 14:14:29 GMT

MSN I NIIPET

re: How to troubleshoot the COM Add-ins loading issues

ca0v — Thu, 10 Apr 2008 18:39:58 GMT

Does Office do any logging to explain why it changes the LoadBehavior from 3 to 2?

re: How to troubleshoot the COM Add-ins loading issues

NovemberJim — Mon, 05 Jan 2009 00:59:41 GMT

This link to a blog entry on the same topic has some additional suggestions:

http://blogs.msdn.com/vsod/archive/2008/04/22/Troubleshooting-com-add-in-load-failures.aspx

Office cannot find the ProgID even though it's in the Registry

NovemberJim — Fri, 09 Jan 2009 21:14:06 GMT

I have a puzzling situation on Vista with a COM Addin not being able to find my Addin's COM type even though the registry entries seem to be there. My customer is repeatedly seeing LoadBehavior go from 3 to 2 when he attempts to connect to the Addin, so I wrote a diagnostic program for him to run. The diagnostic program runs independently of Office to see if it can load my Add-In. First it walks thru the registry and reports that it finds all registry keys/values that are required:

1) HKCU/./MSProject/Addins/ProgID.Connect

2) HKCU/Software/Classes/ProgID.Connect/CLSID

3) HKCU/Software/Classes/CLSID/{B3A3...}/InprocServer/(default)

It reports that it finds all of these and that all have their expected values.

It tries to load the the addin with the call CreateObject("ProgID.Connect"). This fails with a generic error message ("cannot load ActiveX component").

Then it tries to look up the COM type associated with my Addin so that it can attempt to load the addin with CreateInstance(myCOMType). When it executes myCOMType= Type.GetTypeFromProgID("ProgID.Connect"), it return a null reference. What's going on here? Why can't Type.GetTypeFromProgID find a ProgID that's clearly in the registry?