ForceReboot action in Called MSI - problem after reboot

[NewsArchive]

Yes, this is a problem with setup.exe behaviour. I've reported about this
already. Windows is not fully loaded before your ForceReboot begis reboot
as it was explained me in InstallShield when I was there on Lab a few days
ago. They've filed already the feature on this issue. Now the workaround is
to install Windows Installer 1.1 before your installation.

Hey, InstallShield fellows, you see I am not alone with this problem!

Galina Grigorin,
Nortel Networks.

Freddy Hinds <freddyh@alibre.com> wrote in article
<38bd8369.0@news.installshield.com>...
> Here are the errors If it helps any ...
>
> SYSTRAY.EXE - DLL initialization failed
> The application failed to initialize because the window station is
shutting
> down.
>
> after hitting OK got same error dialog but for ...
>
> NTACMON.EXE
> WINMSUIT.EXE
> DESKTRAY.EXE
> PQINIT.EXE
>
> ran across same problem on another machine ... though the error dialog
were
> slightly different ... SYSTRAY.EXE started it off, but the errors that
> followed were different ... I think it just depends on what programs are
> running in the task tray ...
>
> Also ... after swimming through all the error dialogs the system finally
> reboots ... BUT the install does not resume once the system comes back
up.
>
> Freddy Hinds wrote in message <38bc7050.0@news.installshield.com>...
> >shutdown. I can't remember the exact error messages, but I can find out
if
> >necessary.
>
>
>
>

[rsinclair]

I'm calling another MSI file (Access 2000 SP1 runtime) and it has a ForceReboot action in it that we have determined is very necessary. The problem I have run into is that when the computer restarts, the Access install completes but it does not launch back into our installer.

Does anyone have any suggestions on how to handle this, or if there is something I'm missing.

TIA,
Russell Sinclair