On 23/10/2021 00:17, Shawn Coffman wrote:
> Would this be the same if a sub-installer was being called from another
> installer? In other words, our software has two installers. One is s
> sub-installer (child) that is called from w/in the other installer. On
> 98% of the time when run in silent mode, the install completes
> successfully. But there is 2% of times where it seems to stall on the
> sub-installer. Unfortunately, we are unable to find any logging that
> indicates why the sub-installer has stopped. In our investigation, we
> discovered the machine needed to be rebooted which lead to my statement
> about a reboot.
Most likely, you're missing some command line parameter telling the
child install to run fully silently and it is stopping with an error
dialog or something.
Read the docs on the command line parameters and make sure that you're
passing everything necessary. Also ensure that your child script does
not contain any calls to MsgBox or similar blocking dialog functions.
If you want more help with this, then at minimum you'll need to post
exactly what you're doing at the moment (including example code and
parameters). As Bill said, the best way is to reproduce the problem
with a MCVE -- not only does that make it easier for people to
understand and assist, but usually during the course of trying to build
one you will figure out the solution on your own.