Command line Exception registering Add-in

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

Command line Exception registering Add-in
Trying to register addin with ADXRegistrator in WiX, getting exception  
Glenn Gidlof




Posts: 4
Joined: 2015-11-13
Using the following Custom actions in my WiX install I am getting an Exception Message: Wrong command line in the asdregistrator.log

the definition of the custom action is as follows:
<CustomAction Id="_F9739287_04AF_425B_BC20_9314457BC620" Execute="deferred" Impersonate="no" FileKey="filEDEDA767ECF1AB1264AE67E6DDC98BDD" adx:VSName="adxregistrator.exe" ExeCommand="/Uninstall"/>

<CustomAction Id="_8DC7D2AE_1D6E_4D9C_AA27_E7C32889CEFA" Execute="rollback" Impersonate="no" FileKey="filEDEDA767ECF1AB1264AE67E6DDC98BDD" adx:VSName="adxregistrator.exe" ExeCommand="/Rollback" />

<CustomAction Id="_438B56D0_7FD3_44EB_A71B_61F41B06841A" Execute="deferred" Impersonate="no" FileKey="filEDEDA767ECF1AB1264AE67E6DDC98BDD" adx:VSName="adxregistrator.exe" ExeCommand="/Install" />

<CustomAction Id="RegisterDll" Execute="deferred" Impersonate="yes" FileKey="filEDEDA767ECF1AB1264AE67E6DDC98BDD" ExeCommand='/install="$(var.LR.Ribbon.FilesDirReg)\e1LRRibbon.dll" /privileges=administrator /returnExitCode=false' />

<CustomAction Id="UnregisterDll" Execute="immediate" Impersonate="yes" FileKey="filEDEDA767ECF1AB1264AE67E6DDC98BDD" ExeCommand='/uninstall="[Ribbon.Folder]\e1LRRibbon.dll" /privileges=administrator' Return='ignore' />



and here is the error section from the log file:

17:18:05 0400 Unwrapping the instance of the 'AddinExpress.Deployment.ADXRegistrator' class.
17:18:05 0400 Success.
17:18:05 0400 Calling the managed registration procedure.
17:18:05 0400 Managed Error:
Date and Time: 11/13/2015 5:18:05 PM
Machine Name: DELL-DEV
IP Address: fe80::d905:c30e:dc44:5b87%12
Current User: NT AUTHORITY\SYSTEM

Application Domain: C:\Program Files (x86)\Event 1\Liberty Reports\Ribbon\
Assembly Codebase: file:///C:/Program Files (x86)/Event 1/Liberty Reports/Ribbon/AddinExpress.MSO.2005.DLL
Assembly Full Name: AddinExpress.MSO.2005, Version=6.6.3059.2005, Culture=neutral, PublicKeyToken=4416dd98f0861965
Assembly Version: 6.6.3059.2005

Exception Source: AddinExpress.MSO.2005
Exception Type: System.ArgumentException
Exception Message: Wrong command line.
Exception Target Site: RegisterAssembly

---- Stack Trace ----
AddinExpress.Deployment.ADXRegistrator.RegisterAssembly(commandLine As String)
AddinExpress.MSO.2005.DLL: N 0079 (0x4F) IL



17:18:05 0400 The add-in registration process is completed with HRESULT = -2147467259.



can you suggest where to look to find the error?

I try the same command from a command window and it is successful.
Posted 13 Nov, 2015 20:32:26 Top
Andrei Smolin


Add-in Express team


Posts: 14094
Joined: 2006-05-11
Hello Glenn,

You can let Add-in Express create a setup project for you. In this case, you'll see the correct format of the Command. Say, I have the following commands in my test add-in:

    <!-- The 'adxregistrator.exe' custom action. -->
    <CustomAction Id="_CBD9642D_2568_4CAD_83C4_72EA1D687202" FileKey="_0BBBC40A_042D_E348_A2CF_7CCB287D6D0E" Execute="deferred" ExeCommand="/install=&quot;_ExcelPanes.dll&quot; /privileges=user" Impersonate="yes" />
    <!-- The 'adxregistrator.exe' custom action. -->
    <CustomAction Id="_C44F1775_24B5_43E2_9C42_1BA17EC223B0" FileKey="_0BBBC40A_042D_E348_A2CF_7CCB287D6D0E" Execute="rollback" ExeCommand="/uninstall=&quot;_ExcelPanes.dll&quot; /privileges=user /generateLogFile=false" Impersonate="yes" />
    <!-- The 'adxregistrator.exe' custom action. -->
    <CustomAction Id="_974FD6A7_FA08_4F5F_8F11_FD5D14F1680E" FileKey="_0BBBC40A_042D_E348_A2CF_7CCB287D6D0E" Execute="deferred" ExeCommand="/uninstall=&quot;_ExcelPanes.dll&quot; /privileges=user" Impersonate="yes" />


That is, the Command attribute contains 1)the command which also specifies the DLL to process, 2) privileges, 3) Impersonate.

Hope this helps.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 16 Nov, 2015 04:41:56 Top
Glenn Gidlof




Posts: 4
Joined: 2015-11-13
I am using WiX to register the add in DLL, and using custom actions like you described above.

I was able to able to eliminate the error that I was seeing in the log file, I had an incorrect path to my .dll.
Posted 16 Nov, 2015 15:12:04 Top
Andrei Smolin


Add-in Express team


Posts: 14094
Joined: 2006-05-11
Thank you for letting me know.

Regards from Belarus (GMT+3),

Andrei Smolin
Add-in Express Team Leader
Posted 17 Nov, 2015 01:57:41 Top