Installation problem

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

Installation problem
 
Subscribe
Chris Ducharme




Posts: 18
Joined: 2013-05-09
Hi

We are trying to install our add-in for all users on a machine. The customer is installing as the administrator. The problem is that the user does not see the add-in when they login. I do not know if it makes a difference, but the admin does not have office installed on their login.

Here is the adxRegistrator.log file:
Add-in Express Registrator Log File: 09/19/2017 14:11:57

Installation directory: C:\Program Files (x86)\Minisoft\ARCS\OutlookAddin\
Registrator version: 8.6.4408.0
Operating System: Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit
Process Owner: Administrator
Command Line: "C:\Program Files (x86)\Minisoft\ARCS\OutlookAddin\adxregistrator.exe" /install="ARCSOutlookAddIn.dll" /privileges=admin
Run 'As Administrator': Yes
Process Elevated: Yes
Integrity Level: High
UAC (User Account Control): On
--------------------------------------------------------------
14:11:57 0236 Starting the add-in registration process.
14:11:57 0236 Loading mscoree.dll
14:11:57 0236 Success.
14:11:57 0236 .NET Framework installation directory:
14:11:57 0236 The latest version of .NET Framework: 'v4.0.30319'
14:11:57 0236 Loading CLR: v4.0.30319.
14:11:57 0236 Calling CLRCreateInstance method.
14:11:57 0236 Success.
14:11:57 0236 Calling GetRuntime method.
14:11:57 0236 Success.
14:11:57 0236 Checking if the hosting API of .NET Framework v4.0 beta is installed.
14:11:57 0236 The hosting API is up to date.
14:11:57 0236 Calling GetInterface method for the CorRuntimeHost interface.
14:11:57 0236 Success.
14:11:57 0236 Starting CLR...
14:11:57 0236 Success.
14:11:57 0236 Getting the CLR version.
14:11:57 0236 The CLR v4.0.30319 has been initialized successfully.
14:11:57 0236 Creating a new domain setup.
14:11:57 0236 Success.
14:11:57 0236 Getting the add-in directory.
14:11:57 0236 Success. The directory is 'C:\Program Files (x86)\Minisoft\ARCS\OutlookAddin\'
14:11:57 0236 The 'shadow copy' is disabled.
14:11:57 0236 Creating a new application domain.
14:11:57 0236 Success.
14:11:57 0236 Getting the base directory for the domain.
14:11:57 0236 Success. The directory is 'C:\Program Files (x86)\Minisoft\ARCS\OutlookAddin\'.
14:11:57 0236 Searching for the Add-in Express core library.
14:11:57 0236 Success. The 'AddinExpress.MSO.2005.dll' file is found.
14:11:57 0236 Creating an instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
14:11:57 0236 Assembly identity is 'AddinExpress.MSO.2005'.
14:11:57 0236 Success.
14:11:57 0236 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
14:11:57 0236 Success.
14:11:57 0236 Calling the managed registration procedure (DISPID = 1610743823).
14:11:58 0236 Registration success.
14:11:58 0236 The add-in registration process is completed with HRESULT = 0.

Here is the adxLoader.dll.manifest
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<assemblyIdentity name="ARCSOutlookAddIn" imageRuntimeVersion="v4.0.30319" hash="" id="ARCSOutlookAddIn">
<displayAlerts>true</displayAlerts>
</assemblyIdentity>
<loaderSettings generateLogFile="true" shadowCopyEnabled="true" RegisterForAllUsers="true" privileges="administrator" configFileName="app.config" clrVersion="2">
</loaderSettings>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" />
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
<Reference URI="#ARCSOutlookAddIn">
<Transforms>
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
</Transforms>
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<DigestValue></DigestValue>
</Reference>
</SignedInfo>
<SignatureValue></SignatureValue>
<KeyInfo>
<KeyValue>
<RSAKeyValue>
<Modulus></Modulus>
<Exponent></Exponent>
</RSAKeyValue>
</KeyValue>
</KeyInfo>
</Signature>
</configuration>
Posted 20 Sep, 2017 18:19:24 Top
Andrei Smolin


Add-in Express team


Posts: 14111
Joined: 2006-05-11
Hello Chris,

Chris Ducharme writes:
the admin does not have office installed on their login


Sorry?

Please reinstall your add-in. Make sure that {My Documents}\Add-in Express\adxloader.log in the profile of the user who starts the host application gets updated when the user starts the host Office application. If the file is updated, send a copy of it to the support email address or post it here.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 21 Sep, 2017 03:44:56 Top
Chris Ducharme




Posts: 18
Joined: 2013-05-09
Sorry, i meant to say that the outlook when the admin logs in is not setup.


There is no adxloader.log created when the user logs in.
Posted 21 Sep, 2017 10:14:20 Top
Andrei Smolin


Add-in Express team


Posts: 14111
Joined: 2006-05-11
Hello Chris,

I don't understand what occurs (or doesn't occur) when an administrator logs in. Please confirm that Office (and Outlook) is installed on that machine.

If the add-in gets installed correctly - the log above confirms this - and still, there's no adxloader.log, you need to check section Troubleshooting add-in loading, see the PDF file in the folder {Add-in Express}\Docs on your development PC.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 22 Sep, 2017 05:23:17 Top
Chris Ducharme




Posts: 18
Joined: 2013-05-09
Yes, outlook is installed on the machine, but the admin who is installing the add-in does not have outlook setup, so he can run it.

The problem:
We have an add-in the works and installs fine, if we install it per user. I am having problems getting it to install per machine.

When i install it per machine, it does not try to load for any of the users. (No adLoader log file is being created)
The adxRegistrator (in the first message) appears to complete successfully.

I have read through the articles about the per machine/per user setup, but it appears that i am missing something. Currently when i go from per user to per machine setup, these are the changes i make.

1. In the AddInModule, i change RegisterForAllUsers from False to True
2. In the setup project i change all (3) Custom Actions from /Privileges=user to /Privileges=admin
3. In the setup project Post Build Event I change the /UAC=off to /UAC=on.
“{Add-in Express}\Bin\adxpatch.exe” “$(BuiltOutputPath)” /UAC=on /RunActionsAsInvoker=true

Is there something else that i need to do.

Thanks

Chris
Posted 25 Sep, 2017 12:37:59 Top
Andrei Smolin


Add-in Express team


Posts: 14111
Joined: 2006-05-11
Hello Chris,

It looks like you have the GenerateInstallInfo property of the add-in module set to true; if so, make sure the manifest is writable, set the property to false and rebuild the project.

Chris Ducharme writes:
Currently when i go from per user to per machine setup, these are the changes i make.


I assume you also change the default location of the installation folder. The list of changes is okay.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 26 Sep, 2017 04:50:56 Top
Chris Ducharme




Posts: 18
Joined: 2013-05-09
Yes, i am changing the folder for installation through the setup.exe GUI.

I made the changes to make GenerateInstallInfo = false. Now when i install it on my dev machine, the add-in appears. I will not be able to try it on our client machine until later today.

When installing it for all users of the machine, where should it put the registry keys? Currently with this install, it put the keys in: HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\ARCSOutlookAddIn.AddinModule is that correct, or should it have put the keys under the HKEY_LOCAL_MACHINE? When i register it using Visual Studio (Add-In Express->Register), it puts the keys in HKLM.
Posted 26 Sep, 2017 09:25:10 Top
Andrei Smolin


Add-in Express team


Posts: 14111
Joined: 2006-05-11
Hello Chris,

Registering from VS is a special case: the keys are created in HKLM to let you debug the add-in with administrative privileges.

When you register a per-machine add-in, it creates it keys in HKLM; a per user add-in writes to HKCU. Still, a per-machine add-in creates a key in HKCU when the user loads it; the key HKLM\Software\Mirosoft\Office\{an Office application}\Addins\{your add-in GUId} containing the FriendlyName, Description and CommandLineSafe values is the one created when you register the add-in.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 26 Sep, 2017 09:38:20 Top
Chris Ducharme




Posts: 18
Joined: 2013-05-09
Thanks. This took care of the problem.
Posted 27 Sep, 2017 13:01:09 Top
Andrei Smolin


Add-in Express team


Posts: 14111
Joined: 2006-05-11
You are welcome!

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 28 Sep, 2017 02:58:36 Top