updater creates a log file; how can I get at it? - Advanced Installer Community
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

updater creates a log file; how can I get at it?

Hi,
Is there a tag associated with the .log file that is created with the Updater when it does a silent install. I know that I can find that log file in the \Update folder where I specified for the Setup file to be downloaded to. And I know that the name of the file will be the same as that of the Setup file execpt with .LOG on the end. But what I'd like to know is there away to use a tag like "[MSILogFIleLocation]" so that I can copy that .log file out of it's "temporary" home and into a more permanent location away from the \Update folder?

I do something similar already with the "first time installs" scneario where I have a BAT file that is just
copy %1 %2
and so I call a custom action to launch that bat file and part of the CA is to set these two values in the Command LIne: textbox

"[MsiLogFileLocation]" "[PublicDocumentsFolder][Manufacturer]\[ProductName]\Install\Install.log"

But for "updater" installed upgrades to the system I don't know how to capture the log file that the msiexec generates and put it into the same "install" folder as where I have my "install.log" file.

EDIT: Also, I noticed that the log file created by the Updater does not appear to be a verbose log, which I would prefer. Where can I set a flag to tell the Updater to create a verbose log?

Thanks.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: updater creates a log file; how can I get at it?

Hello,
Is there a tag associated with the .log file that is created with the Updater when it does a silent install. I know that I can find that log file in the \Update folder where I specified for the Setup file to be downloaded to. And I know that the name of the file will be the same as that of the Setup file execpt with .LOG on the end. But what I'd like to know is there away to use a tag like "[MSILogFIleLocation]" so that I can copy that .log file out of it's "temporary" home and into a more permanent location away from the \Update folder?
I'm afraid I don't fully understand what you mean. Please keep in mind our Updater tool doesn't generate a log when it is used. If you have a debug version of our Updater tool (this indeed generates a log in the related location) sent from our support team in order to investigate a related issue, then please keep in mind that you there is no Windows Installer property which store the Updater log location. Also, it is recommended to use the Updater release version of our application.
But for "updater" installed upgrades to the system I don't know how to capture the log file that the msiexec generates and put it into the same "install" folder as where I have my "install.log" file.
For this you can simply add, in the "Command" field from your updates configuration project -> Updates page -> Properties tab, a command line like this:

Code: Select all

/L*V %PUBLIC%\Documents\<Manufacture_value>\<ProductName_value>\Install\Install.log
If you have any question let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: updater creates a log file; how can I get at it?

Hi Daniel,
Perhaps I'm confused about the name of which process is which, but the Updater is in charge of the downloading of new updates, then when the installation of that new update occurs, I would like to capture the results of that insallation in a log file. For first-time installers I have renamed the MSILogFileLocation that is created to save it to a folder that is easier for users to find and send for troubleshooting. But for updates, when they are occurring silently I would still like to capture/save any "install.log" files that might be created by the msiexec process...

I will give your suggested Command Line a try and see if it does what we would like it to do, however, as it is right now I have the follwoing command line in that location:

Code: Select all

/exelog
So, it's that "/exelog" that explains better what we currently have. The log file is created alongside the setup file that is being launched by the updater process.

I will let you know the results of replacing that Command Line with the one you suggested.

Thanks.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: updater creates a log file; how can I get at it?

Hello Kevin,

The /exelog is an EXE bootstrapper proprietary command. This command can be used when building the updates package as an EXE setup package. However, in order to get a verbose log of the installation you should still use an MSI proprietary command line similar with the one I previously specified:

Code: Select all

/L*V PathToLog\Install.log
If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: updater creates a log file; how can I get at it?

Hi,
When I try to alter the Command Line in the "update cfg" project from this:

Code: Select all

/exelog
to this:

Code: Select all

/exelog /L*V "%PUBLIC%\Documents\ProMicro\Overture Demo\MyOverture\Update.log"
I tried the above with and without the double-quotes. I found that the silent installation stopped working correctly.

I waited for 20 minutes and the silent installation didn't finish, when it usually finishes in under 5 minutes. I had to do an End Task in Task Manager to close the updater.exe; which was showing 0% CPU and

What could I be doing wrong here?
Thanks.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: updater creates a log file; how can I get at it?

Hello Kevin,

First of all I apologize for my delayed answer. We are quite busy at the moment.

I've tested the scenario and I can replicate the behavior. This seems to be an Advanced Installer issue. It seems that the Updater tool doesn't correctly parse and format the received command line in order to pass it to the updates EXE setup. A fix will be available in a future version of Advanced Installer, thank you for bringing this to our attention. I'll let you know as soon as a fix will be avaiolable. Until then, I'm afraid the only workaround would be to create only an EXE log for your updates installation. So, you should revert back the "Command Line" field from your updates config project like this:

Code: Select all

/exelog
We'll update this thread as soon as an update will be available. Thank you for your understanding.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: updater creates a log file; how can I get at it?

Hello,

This was fixed in version 11.6 of Advanced Installer released on October 23rd, 2014.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”