FileSite 9, Word 2007 and custft_EAI_advanced(85SP3U2-9x).dotm = Type MisMatch Error

System

We have the FileSite 9 and custft_EAI_advanced(85SP3U2-9x).dotm Footer ID addin working on one test FileSite 9 PC and not another.

We are testing at the moment with a view to installing the FileSite 9.0 client on 300+ client PCs. The current success rate of 50% is obviously no where near acceptable.

I've traced the error in the Addin to the AutoExec code within the NRTAuotMacros module:

The specific line casing the error is:

Set objIManageExtensibility = _
Application.COMAddIns("WorkSiteOffice2007Addins.Connect").Object

This is returning a 13 (Type Mis-match error).

Here's the code in context...

Public Sub AutoExec()

Dim objIManageExtensibility As WorkSiteAddinInterfaces.iManageExtensibility
' An object used for extending the functionality of WorkSite Office 2000
' integration.

' Get the WorkSite O2K extensibility object.
Set objIManageExtensibility = _
Application.COMAddIns("WorkSiteOffice2007Addins.Connect").Object

' Set up a sink to the extensibility object.
Set objSinkObject = New SinkObject
objSinkObject.SinkIManageExtensibility objIManageExtensibility

End Sub


We have:

Repaired the File Site 9 client
Uninstalled and reinstalled the File Site 9 client.
Copied the relevant dlls from the working machine to the 'broken' machine and have also unregistered/ re-registered these...
Copied a clean copy of the custft_EAI_advanced(85SP3U2-9x).dotm to the 'broken' machine...
Added the dll to the trusted locations in Words security.
Allowed all VBA and Active X controls

With the same end result - a debug error on Word opening and no document IDs being inserted...*sigh* and I had such high hopes of File Site 9 actually working straight out of the box...

Both PCs are based on an identical image.
Both test user accounts have Administrator rights to the PC (excessive perhaps but useful for troubleshooting).

Any ideas before I make a business case for buying Humming Bird?

Migrateduser

Starting a habit here on answering my own problems...spoke to our Application Support Team and it turns out that the test PC had, had Worksite 8.2 installed and then FileSite 9.0 installed on top.

Wonderful work on InterWoven's part here - the FileSite 9.0 installer does'nt check for and/or uninstall pre-exisiting versions of the software...so we had 8.2 and 9.0 co-existing on the same PC.

One round of uninstalls and a reinstall of FileSite 9.0 later and everything works.