Word Add-in Doesnt Show on 64bit

Add-in Express™ Support Service
That's what is more important than anything else

Word Add-in Doesnt Show on 64bit
Addin-Express 2009, Office 2003, 64bit, loader 6.3.3052.0 
Magdalena Magdalena




Posts: 5
 Joined: 2009-05-28
Hi there,

I'm using Addin-Express 2009 v5.2.2024 to create a custom Office Word 2003 (SP3) addin command bar, but uses the adxloader.dll v6.3.3052.0.

Please note that I dont add adxloader64.dll to the project, since your documentation adxnet2010.pdf says that it is "64-bit loader; required for Office 2010 64-bit" and this add-in is for Office 2003.

Created a setup project manually on VS2008 and it was built using "Any CPU" configuration.
Installed it on different 32-bit machines work fine and the addin shows on Word 2003.


Installing on a 64-bit machine Windows Server 2003 doesn't complain, the addin is listed under "Add or Remove Programs", however the addin wont show up when loading Word 2003.


This is the content of adxloader.log after the addin installation:


Add-in Express Loader Log File: 02/11/2011 14:21:44

Startup directory: M:\Program Files (x86)\<company_name>\<product_name>\
Loader version: 6.3.3052.0
Operating System: Microsoft Windows Server 2003, Enterprise x64 Edition Service Pack 2 (build 3790)
Process Owner: System
Command Line: M:\WINNT\SysWOW64\MsiExec.exe -Embedding 549624768EEF7DDFDFAA38A55127B524 E Global\MSI0000
Run 'As Administrator': Yes
Process Elevated: No
Integrity Level: Untrusted
UAC (User Account Control): Off
------------------------------------------------------------------------
14:21:44 752 3172 Starting the add-in registration process.
14:21:44 752 3172 Getting the latest CLR version.
14:21:44 752 3172 The latest CLR version is 'v4.0.30319'.
14:21:44 752 3172 Loading CLR: v4.0.30319.
14:21:44 752 3172 Calling CLRCreateInstance method.
14:21:44 752 3172 Success.
14:21:44 752 3172 Calling GetRuntime method.
14:21:44 752 3172 Success.
14:21:44 752 3172 Calling GetInterface method.
14:21:44 752 3172 Calling GetInterface method for the CorRuntimeHost interface.
14:21:44 752 3172 Success.
14:21:44 752 3172 Starting CLR...
14:21:44 752 3172 Success.
14:21:44 752 3172 The CLR v4.0.30319 has been initialized successfully.
14:21:44 752 3172 Creating a new domain setup.
14:21:44 752 3172 Success.
14:21:44 752 3172 Getting the add-in directory.
14:21:44 752 3172 Success. The directory is 'M:\Program Files (x86)\<company_name>\<product_name>\'
14:21:44 752 3172 The configuration file is 'M:\Program Files (x86)\<company_name>\<product_name>\app.config'
14:21:44 752 3172 The 'shadow copy' is disabled.
14:21:44 752 3172 Creating a new application domain.
14:21:44 752 3172 Success.
14:21:44 752 3172 Getting the base directory for the domain.
14:21:44 752 3172 Success. The directory is 'M:\Program Files (x86)\<company_name>\<product_name>\'.
14:21:44 752 3172 Searching for the Add-in Express core library.
14:21:44 752 3172 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
14:21:44 752 3172 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
14:21:44 752 3172 Assembly identity is 'AddinExpress.MSO.2005'.
14:21:44 752 3172 Success.
14:21:44 752 3172 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
14:21:44 752 3172 Success.
14:21:44 752 3172 Creating an instance of the XML parser class.
14:21:44 752 3172 Success.
14:21:44 752 3172 Loading the manifest file (M:\Program Files (x86)\<company_name>\<product_name>\adxloader.dll.manifest).
14:21:44 752 3172 Success.
14:21:44 752 3172 Getting the root element of the manifest (M:\Program Files (x86)\<company_name>\<product_name>\adxloader.dll.manifest).
14:21:44 752 3172 Success.
14:21:44 752 3172 Getting the 'assemblyIdentity' element of the manifest (M:\Program Files (x86)\<company_name>\<product_name>\adxloader.dll.manifest).
14:21:44 752 3172 Success.
14:21:44 752 3172 Searching for the 'name' attribute of the 'assemblyIdentity' element.
14:21:44 752 3172 Success. The name is '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956'.
14:21:44 752 3172 Calling the managed procedure to register the '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly.
14:21:44 1008 Connecting to the application domain of the Add-in Express loader.
14:21:44 1008 Success.
14:21:44 1008 Loading the '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly.
14:21:44 1008 Success.
14:21:44 1008 Registering the '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly (user).
14:21:44 1008 Registering the '<assembly_name>.AddinModule' type.
14:21:44 1008 Searching for static methods that contain the 'ComRegisterFunction' attribute.
14:21:44 1008 Calling the 'AddinRegister' static method.
14:21:44 1008 The '<assembly_name>.AddinModule' type has been registered successfully.
14:21:44 1008 The ' <assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly has been registered successfully.
14:21:44 1008 The managed registration process is complete with HRESULT = 0.
14:21:44 752 3172 The add-in registration process is completed with HRESULT = 0.


After installation, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Word\Addins\<assembly_name>\LoadBehaviour was set to 3.

However, after loading up Word, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Word\Addins\<assembly_name>\LoadBehaviour was set to 2.


- We tried "Repair" from "Add or Remove Program", the addin still doesnt show up in Word.
- Addin is not listed under "Disabled Items" list in Word.
- Loading up Word repeatedly on 64-bit machine doesnt seem to write anything to adxloader.log.

Can you please help me on how to make the add-in appear on 64-bit machine?


Thank you!


Magdalena
Posted 11 Feb, 2011 00:50:36 Top
Eugene Astafiev


Guest


Hi Magdalena,

Thank you for providing me with the adxloader.log file. It looks good. I didn't notice anything strange on my road.

Please try to install the latest build of http://www.add-in-express.com/downloads/adxnet.php. Then please don't forget to replace the adxloader.dll in the Loader folder of your add-in project with a new one (see the Redistributables folder).

Note that you need to use the adxloader.dll for the Add-in Express 2009 package (not 2010). You can download an appropriate version of the loader from http://www.add-in-express.com/downloads/adxloader.php. See the Add-in Express Loader 2009 for Office and .NET entry.

What Office version do you use on the problematic PC?
Posted 11 Feb, 2011 06:23:57 Top
Magdalena Magdalena




Posts: 5
 Joined: 2009-05-28
Hi Eugene,

Thanks for the prompt reply.

On the problematic PC, Office Word 2003 SP3 is installed (part of Microsoft Office Prof Edition 2003).

I've upgraded to Addin Express 2009.5.3.2030.
Modified the addin project to replace the adxloader.dll with the new one, rebuilt the addin project, rebuilt the setup project and installed it on the 64bit machine.

Installation didnt complain but addin still wont show up in Word.

adxloader.log for the installation:


Add-in Express Loader Log File: 02/14/2011 12:26:08

Startup directory: M:\Program Files (x86)\<company_name>\<product_name>\
Loader version: 5.3.2030
------------------
12:26:08 748 5092 Starting the add-in registration process.
12:26:08 748 5092 Getting the latest CLR version.
12:26:08 748 5092 The latest CLR version is 'v4.0.30319'.
12:26:08 748 5092 Loading CLR: v4.0.30319.
12:26:08 748 5092 Calling GetCLRMetaHost method.
12:26:08 748 5092 Success.
12:26:08 748 5092 Calling GetRuntime method.
12:26:08 748 5092 Success.
12:26:08 748 5092 Calling GetInterface method.
12:26:08 748 5092 Calling GetInterface method for the CorRuntimeHost interface.
12:26:08 748 5092 Success.
12:26:08 748 5092 Starting CLR...
12:26:08 748 5092 Success.
12:26:08 748 5092 The CLR v4.0.30319 has been initialized successfully.
12:26:08 748 5092 Creating a new domain setup.
12:26:08 748 5092 Success.
12:26:08 748 5092 Getting the add-in directory.
12:26:08 748 5092 Success. The directory is 'M:\Program Files (x86)\<company_name>\<product_name>\'
12:26:08 748 5092 The configuration file is 'M:\Program Files (x86)\<company_name>\<product_name>\app.config'
12:26:08 748 5092 The 'shadow copy' is disabled.
12:26:08 748 5092 Creating a new application domain.
12:26:08 748 5092 Success.
12:26:08 748 5092 Getting the base directory for the domain.
12:26:08 748 5092 Success. The directory is 'M:\Program Files (x86)\<company_name>\<product_name>\'.
12:26:08 748 5092 Searching for the Add-in Express core library.
12:26:08 748 5092 Success. The 'AddinExpress.MSO.2005.dll' file has been found.
12:26:08 748 5092 Creating an instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
12:26:08 748 5092 Assembly identity is 'AddinExpress.MSO.2005'.
12:26:08 748 5092 Success.
12:26:08 748 5092 Unwrapping the instance of the 'AddinExpress.MSO.ADXLoaderSupport' class.
12:26:08 748 5092 Success.
12:26:08 748 5092 Creating an instance of the XML parser class.
12:26:08 748 5092 Success.
12:26:08 748 5092 Loading the manifest file (M:\Program Files (x86)\<company_name>\<product_name>\adxloader.dll.manifest).
12:26:08 748 5092 Success.
12:26:08 748 5092 Getting the root element of the manifest (M:\Program Files (x86)\<company_name>\<product_name>\adxloader.dll.manifest).
12:26:08 748 5092 Success.
12:26:08 748 5092 Getting the 'assemblyIdentity' element of the manifest (M:\Program Files (x86)\<company_name>\<product_name>\adxloader.dll.manifest).
12:26:08 748 5092 Success.
12:26:08 748 5092 Searching for the 'name' attribute of the 'assemblyIdentity' element.
12:26:08 748 5092 Success. The name is '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956'.
12:26:08 748 5092 Calling the managed procedure to register the '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly.
12:26:08 1004 Connecting to the application domain of the Add-in Express loader.
12:26:08 1004 Success.
12:26:08 1004 Loading the '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly.
12:26:08 1004 Success.
12:26:08 1004 Registering the '<assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly (user).
12:26:08 1004 Registering the '<assembly_name>.AddinModule' type.
12:26:08 1004 Searching for static methods that contain the 'ComRegisterFunction' attribute.
12:26:08 1004 Calling the 'AddinRegister' static method.
12:26:08 1004 The '<assembly_name>.AddinModule' type has been registered successfully.
12:26:08 1004 The ' <assembly_name>, PublicKeyToken=13fc0ab42cd7a956' assembly has been registered successfully.
12:26:08 1004 The managed registration process is complete with HRESULT = 0.
12:26:08 748 5092 The add-in registration process is completed with HRESULT = 0.



And I notice that under the installation Application Folder, it created a "<assembly_name>.dll.manifest" text file with content:


Log entry added at 12:27:03 PM:
-----------Caption----------------
Office document customization
-----------Message----------------
The customization assembly associated with this document could not be loaded. The application manifest might be corrupted. You can still edit and save the document. Contact your administrator or the author of this document for further assistance.
-----------Details----------------
(null)


I'm not sure which application manifest it referred to, but this is the content of adxloader.dll.manifest:


<?xml version="1.0" encoding="utf-8"?>
<configuration>
<assemblyIdentity name="<assembly_name>, PublicKeyToken=13fc0ab42cd7a956" />
<loaderSettings generateLogFile="true" shadowCopyEnabled="true" privileges="user" configFileName="app.config" />
</configuration>



Regards,


Magdalena
Posted 14 Feb, 2011 01:13:27 Top
Eugene Astafiev


Guest


Hi Magdalena,

Thank you for providing me with the adxloader.log file. It looks good, I didn't anything strange on my way.

Are you able to reproduce the issue with a newly created empty add-in project? Does it work?
Posted 14 Feb, 2011 06:36:16 Top
Magdalena Magdalena




Posts: 5
 Joined: 2009-05-28
Hi Eugene,

It seems that setting RegisterForAllUsers = true solves my problem of not showing on the problematic PC (which is the 64bit Terminal Server machine).

It was set to false previously and I didnt realise about this as the addin shows up correctly in different machines (even in several virtual desktops).

Sorry to bother you and thanks again for the help!


Regards,


Magdalena
Posted 15 Feb, 2011 00:47:11 Top
Eugene Astafiev


Guest


You are welcome, Magdalena!
Posted 15 Feb, 2011 09:28:04 Top