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

Re: Install another software using attached powershell script

Hello Krishna,

We apologize for the delayed reply. My colleague Catalin is out of the office and I will pick up this thread.

The only workaround I could think of will be to check within your PowerShell script code the exit code of the related msi installation, and while this exit code is 1618 (another installation in progress) then wait for a few seconds and retry again to launch the related MSI installation.

I have sent you over email a modified version of your ps1 script which I have successfully tested it on a test machine. Just let me know how this worked.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Install another software using attached powershell script

After further investigating this on our end, this seems indeed to be cause by a bug in our application. The root cause of this problem relies in the fact that the "Wait for custom action to finish before proceeding" flag ("Custom Actions" page --> your custom action --> "Execution Options" section) is ignored for our predefined PowerShell custom actions.
This was fixed in version 16.2 of Advanced Installer released on August 1st, 2019.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”