|
Tim Kempster
Posts: 13
Joined: 2025-09-24
|
I have a problem installing on Windows 11 64 bit where the Office install is 32 bit. The same installer works fine on 64 bit windows and 64 bit office.
I have an Outlook plugin and a windows (all users) installer. The adxregistrator log file shows a clean install (shown below). However the addin is not added to Outlook. When I explore File->Add-ins->COM Addins it's not visible. However if I add it by hand "Add" and then go to the adxloader.dll file in the install dir of my addin it is added to Outlook. On a 64 bit office install it points to adxloader64.dll.
It seems to me that the registration if failing because it is perhaps trying to register the 64 bit adxloader. My setup file is built with target platform x86.
Any help much appreciate?
-------
Add-in Express Registrator Log File: 12/11/2025 13:41:35
Installation directory: C:\WINDOWS\SysWOW64\config\systemprofile\AppData\Local\Thinking-Machine Limited\Outlook Print\
Registrator version: 10.2.4714.0
Operating System: Microsoft Windows 10 Professional (build 22631), 64-bit
Process Owner: System
Command Line: "C:\WINDOWS\SysWOW64\config\systemprofile\AppData\Local\Thinking-Machine Limited\Outlook Print\adxregistrator.exe" /install="OutlookPrint.dll" /privileges=admin
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: System
UAC (User Account Control): On
--------------------------------------------------------------
13:41:35 0612 Starting the add-in registration process.
13:41:35 0612 Loading mscoree.dll
13:41:35 0612 Success.
13:41:35 0612 .NET Framework installation directory:
13:41:35 0612 The latest version of .NET Framework: 'v4.0.30319'
13:41:35 0612 Loading CLR: v4.0.30319.
13:41:35 0612 Calling CLRCreateInstance method.
13:41:35 0612 Success.
13:41:35 0612 Calling GetRuntime method.
13:41:35 0612 Success.
13:41:35 0612 Checking if the hosting API of .NET Framework v4.0 beta is installed.
13:41:35 0612 The hosting API is up to date.
13:41:35 0612 Calling GetInterface method for the CorRuntimeHost interface.
13:41:35 0612 Success.
13:41:35 0612 Starting CLR...
13:41:35 0612 Success.
13:41:35 0612 Getting the CLR version.
13:41:35 0612 The CLR v4.0.30319 has been initialized successfully.
13:41:35 0612 Creating a new domain setup.
13:41:35 0612 Success.
13:41:35 0612 Getting the add-in directory.
13:41:35 0612 Success. The directory is 'C:\WINDOWS\SysWOW64\config\systemprofile\AppData\Local\Thinking-Machine Limited\Outlook Print\'
13:41:35 0612 The 'shadow copy' is disabled.
13:41:35 0612 Creating a new application domain.
13:41:35 0612 Success.
13:41:35 0612 Getting the base directory for the domain.
13:41:35 0612 Success. The directory is 'C:\WINDOWS\SysWOW64\config\systemprofile\AppData\Local\Thinking-Machine Limited\Outlook Print\'.
13:41:35 0612 Searching for the Add-in Express core library.
13:41:35 0612 Success. The 'AddinExpress.MSO.2005.dll' file is found.
13:41:35 0612 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
13:41:35 0612 Assembly identity is 'AddinExpress.MSO.2005'.
13:41:35 0612 Success.
13:41:35 0612 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
13:41:35 0612 Success.
13:41:35 0612 Calling the managed registration procedure (DISPID = 1610743823).
13:41:36 0612 Registration success.
13:41:36 0612 The add-in registration process is completed with HRESULT = 0. |
|
|
Tim Kempster
Posts: 13
Joined: 2025-09-24
|
|
To answer my own question the problem was I think that I wasn't targetting [ProgramFilesFolder][Manufacturer]\[ProductName] as my Application Folder. This meant for some reason the adxregistrator.exe could not find the OutlookPrint.dll in the /install="OutlookPrint.dll" /privileges=admin command because it wasn't running in the install folder. |
|
|
Andrei Smolin
Add-in Express team
Posts: 19190
Joined: 2006-05-11
|
Thank you, Tim.
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
Forums
Topics
Search
Help
Login
Register