Reboot Request During InstallValidate Step - Advanced Installer Community
ellikoPre
Posts: 2
Joined: Mon Feb 04, 2019 3:49 pm

Reboot Request During InstallValidate Step

Hi,
Sometimes, during the upgrade process, we get a message dialog saying "The setup must update files or services that cannot be updated while the system is running. If you choose to continue, a reboot will be required to complete the setup.". This happens during the InstallValidate step.
This doesn't happen consistently - sometimes it does and sometimes it doesn't.

The log says:
MSI (s) (8C:7C) [19:13:57:668]: RESTART MANAGER: Did detect that a critical application holds file[s] in use, so a reboot will be necessary.
MSI (s) (8C:7C) [19:13:57:668]: Note: 1: 1610

We have 2 services for which we have custom actions that are responsible for stopping them. We run the custom actions right before the InstallValidate step.

I don't understand why we get the message, and the logs don't say what's the cause for the message. How can I tell what's causing the reboot request?
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: Reboot Request During InstallValidate Step

Hello and welcome to our forums,

Indeed, that message may be thrown when your service is not correctly stopped before the "InstallValidate" standard action. I can not say for sure what causes it.

In order for me to further investigate this, could you please send me a copy of your .AIP file and a verbose log of the installation process by e-mail at support at advancedinstaller dot com?

Kind regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
ellikoPre
Posts: 2
Joined: Mon Feb 04, 2019 3:49 pm

Re: Reboot Request During InstallValidate Step

Hi Catalin,
thank you for the reply!

I have sent the .aip and log files to the support mail.

Waiting for your analysis.
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: Reboot Request During InstallValidate Step

Hello Elli,

Thanks for the sent files.

After investigating your sent log file, it seems that both custom actions are succeeding (both return value 1). This makes me think that it's not the service(s) that holds files in use.

Even though in the log it seems that the StopService custom action successfully ends, I would suggest the following:

- Add a MessageBox custom action after each of the StopService custom action (to stop the installation process)

- Build and Run the setup

- When each message box is spawned:

- Please open a run window (WIN+R) and type services.msc. There, please check and see if the service is indeed stopped.

I have also investigated your sent project and it seems correctly configured.

I would say that the biggest issue is here is that this is not consistently reproducing (as you have mentioned in the e-mail).

In order for me to further investigate this, could you please send me a download link for both the old and the new version of your setup?

P.S: I have also answered your e-mail ticket.

Kind regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”