|
|
|
Tim Farrelly
Posts: 16
Joined: 2020-08-05
|
Hi there,
When I run a setup.exe I can locate the adxregistraor.log. When I run the msi I cannot. It is not in the default location and when I explicitly specify the log location, still nothing.
Here's the log entry from my msi executing a custom action and a trace statement as it is about to call the adxregistrator..
InstallShield 14:57:15: Invoking script function Fn_MyAddinManageAddinRegistration
1: Calling \adxregistrator.exe with arguments: /install="MyAddin.dll" /privileges=admin /LogFileLocation=%Temp%\MyAddin\MyAddin_Adxregistrator.log /ReturnExitCode=true
and the entry showing custom action failure..
CustomAction InfocouncilAddinRegistration returned actual error code 1603
1603 is a "Fatal error during installation."
Any assistance locating (or producing) the adxregistrator log would be appreciated.
Cheers
Tim |
|
|
Posted 21 Mar, 2025 04:09:06
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19095
Joined: 2006-05-11
|
Hello Tim,
Try to start it from an elevated command line. Does it work?
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 21 Mar, 2025 09:53:58
|
|
Top
|
|
|
Tim Farrelly
Posts: 16
Joined: 2020-08-05
|
|
Same result elevated or not Andrei. |
|
|
Posted 23 Mar, 2025 23:15:44
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19095
Joined: 2006-05-11
|
Hello Tim,
Tim Farrelly writes:
When I run a setup.exe I can locate the adxregistrator.log. When I run the msi I cannot.
For a per-machine installation, the MSI must be processed by MSIEXEC.EXE started elevated. SETUP.EXE ensures that.
Make sure that adxregistrator starts elevated: check the header of the adxregistrator.log file.
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 24 Mar, 2025 09:28:06
|
|
Top
|
|
|
Tim Farrelly
Posts: 16
Joined: 2020-08-05
|
Hello Andrei,
I'm sorry I may not be being clear.
In an administrator cmd prompt I am running the command:
msiexec /i "MyAddinProject.msi" /L*V %TEMP%\MSI_Infocouncil.log
It executes up until a custom action which runs the adxregistrator. At this point it fails as detailed above.
I really have two problems. The first is that the adxregistrator is failing, the second is that no log is being produced. In order to solve the first I'm reaching out to you to assist solving the second.
In your experience have you encountered the adxregistrator.log not being produced when running it via msiexec and would you have any suggestions to remedy this.
Many thanks,
Tim |
|
|
Posted 24 Mar, 2025 22:33:01
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19095
Joined: 2006-05-11
|
Hello Tim,
Tim Farrelly writes:
In an administrator cmd prompt I am running the command:
Make sure you run the Command Prompt elevated.
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 25 Mar, 2025 11:40:34
|
|
Top
|
|
|
Tim Farrelly
Posts: 16
Joined: 2020-08-05
|
|
I am and have been running the command prompt elevated |
|
|
Posted 26 Mar, 2025 02:45:48
|
|
Top
|
|
|
Andrei Smolin
Add-in Express team
Posts: 19095
Joined: 2006-05-11
|
Hello Tim,
If you reproduce this on a simple no-code add-in project, please send the add-in project and setup project to me for testing.
Regards from Poland (GMT+1),
Andrei Smolin
Add-in Express Team Leader |
|
|
Posted 26 Mar, 2025 09:40:23
|
|
Top
|
|
Forums
Topics
Search
Help
Login
Register