jfaiga
Posts: 25
Joined: Wed Sep 13, 2006 8:21 am

Completion of silent auto update

Hi,
I have a silent auto update, and I would like to know from a command line whether the latest update has completed (ie whether the install is still running or not).
There are certain things that I could check, such as the registery, or installed files, however checking these only indicate that that section of the update install is completed.
What is the best approach to know when the complete install is finished?
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

The updater needs to update by him self and because of this it's copied to a temp location and launched from there to download and install updates. Thats why you can not wait for the updater to finish.

But we shall consider to implement a better mechanism to allow other process to wait until the updater stops. I add this on our TODO list and will be available in a future release. Thank you for your suggestion.

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
jfaiga
Posts: 25
Joined: Wed Sep 13, 2006 8:21 am

msiexec.exe and updater.exe

Hi,
Can you confirm that this functionality is not in 4.6 ?

If not do you have a recommendation for how I could monitor it myself?

At the moment I am checking whether the updater.exe or msiexec.exe processes are running on the machine in question.
However the problem is that it seems the msiexec.exe stays alive for 10 minutes, even when it takes under a minute to do the automated update.

Therefore I need a way to check whether it has actually finished or not.

One option is to use pslist and check when the msiexec process doesnt have Wait:DelayExec.
Another option is to check in the application log for:
"Product: ... 3.0.4.10 -- Configuration completed successfully."
However is there not something I could put in the installer project itself that is always the last thing to get installed/update?

Or do you have any other options?

Alternatively is the behaviour of msiexec lingering due to the command line parameters that update.exe uses when calling msiexec?
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,
Can you confirm that this functionality is not in 4.6 ?
This functionality was added with 4.6 version of Advanced Installer. Also we have a tutorial on how you can achieve that please see:
http://www.advancedinstaller.com/user-g ... dater.html

Best Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
jfaiga
Posts: 25
Joined: Wed Sep 13, 2006 8:21 am

Hi Gigi,

Thanks for reply.

Based on the URL that you referred me to is it correct to say that as long as the updater.exe is not running, then the automated installation is not happening?

In other words is the lingering existance of the the msiexec.exe something that I can ignore?

Also, the fact that the updater.exe process continues running till the install is completed - is this independent of the parameters that it was called with? ie does it make a difference in this regard whether the parameters were "/checknow" or "/silentall -nofreqcheck" (which I am using).

Regards
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi Jonni,
In other words is the lingering existance of the the msiexec.exe something that I can ignore?
Yes, because you cannot wait for the msiexec.exe to end, this process is not closed immediately after installation is finished.
Also, the fact that the updater.exe process continues running till the install is completed - is this independent of the parameters that it was called with? ie does it make a difference in this regard whether the parameters were "/checknow" or "/silentall > -nofreqcheck" (which I am using).
Yes it works with any supported command line parameter ("/checknow" or "/silentall -nofreqcheck") except "/configure [HWND]" command (but in this case you don't need to wait for updater).

Kind Regards,
Gigi
_______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

Return to “Common Problems”