John,
Here are a couple of things you might look at, in no particular order - though I would check the LoadBehavior first.
(1)
What is the LoadBehavior in the Registry?
HKEY current user> software> microsoft> office> word> addins> Microsoft.Dynamics.GP.BusinessIntelligence.BITemplateMapping> LoadBehavior
It should be 3, sometimes when a Com Add-in load fails, office switches the setting to 2.
(2)
Disable other Add-ins to check for conflicts. Change the LoadBehavior setting to 2 for add-ins listed in HKCU (as above) or HKLM > software > microsoft > office > word > addins
(3)
Turn off any antivirus software. Some antivirus softwares have special plug ins for the office products. Norton for sure has one.
(4)
Run cmd, Type the following on the command line:
C:\>set VSTO_SUPPRESSDISPLAYALERTS=0
C:\>"Program Files (x86)\Microsoft Office\Office14\winword.exe"
check for startup errors
(5)
Turn on UAC if it is turned off
(6)
Make sure your .NET framework is up to date
(7)
Make sure your PIAs (Primary Interop Assemblies) are loaded. You can get them for Office 2010 here: www.microsoft.com/.../details.aspx
(8) - below is advice from a friend -
Make sure all the required dependencies for your Add-In are present/installed on the target machine. You can enable Fusion logs to detect missing dependencies.
To enable Fusion logs, you can either use the “Assembly Binding Log Viewer” (fuslogvw) .NET framework tool or make registry entries to enable logging. [Please do make appropriate backup before making any registry changes]. Here are the registry entries that need to be made:
a) Open regedit and browse to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion”
b) Create a DWORD value by name “EnableLog” and set its value to 1.
c) Create a DWORD value by name “ForceLog” and set its value to 1.
d) Create a DWORD value by name “LogFailures” and set its value to 1.
e) Create a String value by name “LogPath” and set its value to “c:\Fusion”
f) Create the folder “c:\Fusion”
After reproducing the issue, look at each of the files created under “C:\Fusion\ Default \<Application.exe>\” folder. Fix any failures and retry.
To know more about Assembly Binding Log Viewer (fuslogvw), please refer:
Assembly Binding Log Viewer (Fuslogvw.exe)
msdn2.microsoft.com/.../e74a18c4(VS.80).aspx
Kind regards,
Leslei
