|
|
|
Harald Binkle
Guest
|
Hi,
I have two different addins. One registers fine but the other one does not register.
The install.log created by adxregistrator.exe shows no error.
But the addin doesn't show up in Outlook, nowhere.
There are even no registry entries created in HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\AddIns for that addin.
Registering the addin using VisualStudio works fine, but calling adxregistrator seems not.
I'm on the latest version.
Any idea why the setup-registration doesn't work?
Greetings
Harry
Add-in Express Registrator Log File: 11/24/2015 15:59:05
Installation directory: C:\Program Files (x86)\JAM Software\JAM Outlook Tools\
Registrator version: 8.0.4330.0
Operating System: Microsoft Enterprise Edition (build 9200), 64-bit
Process Owner: System
Command Line: "C:\Program Files (x86)\JAM Software\JAM Outlook Tools\adxregistrator.exe" /install=JamOutlookTools.dll /privileges=admin /log=Install.log
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: System
UAC (User Account Control): On
--------------------------------------------------------------
15:59:05 0260 Starting the add-in registration process.
15:59:05 0260 Loading mscoree.dll
15:59:05 0260 Success.
15:59:05 0260 .NET Framework installation directory:
15:59:05 0260 The latest version of .NET Framework: 'v4.0.30319'
15:59:05 0260 Loading CLR: v4.0.30319.
15:59:05 0260 Calling CLRCreateInstance method.
15:59:05 0260 Success.
15:59:05 0260 Calling GetRuntime method.
15:59:05 0260 Success.
15:59:05 0260 Checking if the hosting API of .NET Framework v4.0 beta is installed.
15:59:05 0260 The hosting API is up to date.
15:59:05 0260 Calling GetInterface method for the CorRuntimeHost interface.
15:59:05 0260 Success.
15:59:05 0260 Starting CLR...
15:59:05 0260 Success.
15:59:05 0260 Getting the CLR version.
15:59:05 0260 The CLR v4.0.30319 has been initialized successfully.
15:59:05 0260 Creating a new domain setup.
15:59:05 0260 Success.
15:59:05 0260 Getting the add-in directory.
15:59:05 0260 Success. The directory is 'C:\Program Files (x86)\JAM Software\JAM Outlook Tools\'
15:59:05 0260 The 'shadow copy' is disabled.
15:59:05 0260 Creating a new application domain.
15:59:05 0260 Success.
15:59:05 0260 Getting the base directory for the domain.
15:59:05 0260 Success. The directory is 'C:\Program Files (x86)\JAM Software\JAM Outlook Tools\'.
15:59:05 0260 Searching for the Add-in Express core library.
15:59:05 0260 Success. The 'AddinExpress.MSO.2005.dll' file is found.
15:59:05 0260 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
15:59:05 0260 Assembly identity is 'AddinExpress.MSO.2005'.
15:59:05 0260 Success.
15:59:05 0260 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
15:59:05 0260 Success.
15:59:05 0260 Calling the managed registration procedure (DISPID = 1610743823).
15:59:06 0260 Success.
15:59:06 0260 The add-in registration process is completed with HRESULT = 0.
|
|
|
Posted 24 Nov, 2015 10:21:39
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello Harry,
Could you please reinstall your add-in, start Outlook and check if this creates/updates adxloader.log. If negative, please check section Troubleshooting add-in loading, see the PDF file in the folder {Add-in Express}\Docs on your development PC.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 25 Nov, 2015 04:31:18
|
|
Top
|
|
|
Harald Binkle
Guest
|
Hello Andrei,
Thanks for your answer.
I followed the point and found the assembly signing option in the project ative. After disabling I come one step further: now the registry entries are created and the addin is listed in the active addins of Outlook.
But it's still not loaded, no menu, no form region.
The axdloader.log file is not created.
The install.log still shows no errors.
I just compiled the my second addin too. Now that one shows the same problems, without any code changes done to it.
The difference, which seems to be the change it I upgraded addin-express from V7 to V8.
So this occurs since using V8.
Any further ideas on this? |
|
|
Posted 25 Nov, 2015 05:51:09
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
That section in the manual describes your further steps.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 25 Nov, 2015 06:11:06
|
|
Top
|
|
|
Harald Binkle
Guest
|
Hi,
the manual doesn't say anything about an version upgrade (V7-->V8) may cause this issues?
The addin compiled with V7 installes fine, but the same compiled with V8 doesn't.
Any help be appriciated. |
|
|
Posted 25 Nov, 2015 08:01:34
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Do you have the same Windows and Outlook version/bitness on the target machine?
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 25 Nov, 2015 08:06:04
|
|
Top
|
|
|
Harald Binkle
Guest
|
Hi,
Thanks, that was the correct question.
Checking the bitness made me check the versions of the dll loaded and I found V7 dlls mixed up with V8 dlls.
Setting all to V8 works now.
But as a hint for you: the loader did not create a log file or throw any exception.
there was nothing telling me I was using wrong dlls.
Only after switching of dll signing the loaded logged that it could no load a ddl, but didn't tell me which dll can't be loaded.
Harry |
|
|
Posted 25 Nov, 2015 09:38:57
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Harry,
I'm really interested. Unfortunately, I'm not sure that I understand the issue. What dlls from version did cause the issue? Do you have an explanation of the issue?
Here's the logic I used. adxloader.log is created when Office loads adxloader.dll (adxloader64.dll). The adxloader.log file missing means Office hasn't started loading your add-in. This may occur due to a problem at the registration phase. But adxregistrator.log is okay in your case.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 25 Nov, 2015 10:17:14
|
|
Top
|
|
|
Harald Binkle
Guest
|
Hello Andrei,
The first problem I ran into was:
after installing V8 over V7 I enabled signing in the VS-Addin-Express options of the project.
That leaded to the fact that the addin was nowhere shown. No registry entries on loader log, only the install log with no errors.
That made me starting this thread.
After I read the document (thanks to you) I found that issue and the registry entries are created, but I missed to update the AddinExpress.MSO.2005.dll of V7 to V8 which leads to strange loading behavior an the same machine. Some times it loaded, some times no.
But after several tries I got a loader log reporting an assembly loading issue, but it didn't tell which assembly.
That pointed me to comparing all assemblies and I found that V7 AddinExpress.MSO.2005.dll which obviously can't be loaded by V8 loader.
Greetings
Harry |
|
|
Posted 30 Nov, 2015 10:37:14
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 18829
Joined: 2006-05-11
|
Hello Harry,
Harald Binkle writes:
That pointed me to comparing all assemblies and I found that V7 AddinExpress.MSO.2005.dll which obviously can't be loaded by V8 loader.
This isn't so. The loader loads your assembly and its dependencies; just replacing AddinExpress.MSO.2005.dll cannot influence the adxloader.log creation. There was something else.
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 01 Dec, 2015 05:14:11
|
|
Top
|
|
Forums
Topics
Search
Help
Login
Register