error: 80070002

[eschneider]

I having trouble deploying my Word addin again...

I get the following error from AddinSpy:

The scan for secondary extensibility interfaces failed on this native
add-in. System.IO.FileNotFoundException: Creating an instance of the COM
component with CLSID {2A9EA273-C231-4E8F-A050-FF9F09CC6DB9} from the
IClassFactory failed due to the following error: 80070002.
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean
publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle&
ctor, Boolean& bNeedSecurityCheck)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean
fillCache)
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean
skipVisibilityChecks, Boolean fillCache)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at AddInSpy.NativeAddInScanner.GetSupportedInterfaces(String guid)

Anyone have any ideas?
Also in Word Options / Advanced / Show add-in user interface errors is
checked, why doesn't show me the error?

Thanks,
Schneider

 

[eschneider]

In my case I forgot to add that COM Shim wizard project output
"ManagedAggregator" to the set-up installer.

Here is how I Found the problem:

Created a small program which tries to create the addin (this has less noise
than Word):
public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load

Dim obj As Object

'This is similar to how Word creates you addin

obj = CreateObject("YOU PROG ID")



End Sub

copied this program to my failing set-up project folder.

Run FileMon.exe
http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx
Start the test app.
Filter FileMon to show only the test app process.

Look for anything that says NOT FOUND;
Usually this will point you in the direction of the problem.

Why Word can't tell me all this is beyond me....

I hope this saves someone else a good days work.

Thanks,
Schneider

 

[eschneider]

Also there are two event logs for Office, and Office fails to write and
event item for this problem. I also checked the other system logs.
A detailed stack trace would make life easier for most developers.

Addin spy showed a little more detail than the Word Addin screen.