Oct 27, 2021
01:22 PM
Objective I need to be able to restart a system after a suite installer InstallScript custom action finishes. Background I have a requirement to do the following: Uninstall an instance of SQL Server 2012 Express (done) Create that instance using SQL Server 2016 Express (done - except when there is a PendingFileRenameOperations ) Sometimes the uninstall of SQL Server 2012 Express will create a new PendingFileRenameOperations. If this exists, then the next step to install SQL Server 2016 will fail. If the user just restarts after getting the error, then the suite installer does not call the OnResuming event - which contains a step to collect setup information that the installer writes to a config file in the OnRebooting event. This leaves the suite installer starting over and trying to access database settings and values that do not exist since the install for SQL Server 2016 did not finish. What I have so far I can correctly detect if the system requires a reboot by querying the appropriate registry keys If I just force an exit of the setup, that does not cause the installer to restart after the user has restarted the system and logged back in. I have thought about manually writing to the RunOnce registry key, but I am not certain of the syntax for this. I already check for PendingFileRenameOperations and RunOnce registry keys when starting the install and correctly ask the user to restart the computer before starting the install. However, this does not fix this current issue, where the Uninstall of SQL Server 2012 Express instance will generate a PendingFileRenameOperations . Thank you in advance.
... View more
Labels
- Labels:
-
InstallShield 2020 R2
Sep 23, 2021
01:39 PM
I am having the same problem. I was testing a new abort condition and discovered that the installer hangs after having evaluated the conditions without showing a dialog with the appropriate message. I created a new InstallSuite project and added a small MSI package for testing. I created a new Exit Condition (any message works) Condition: All, Property Comparison, PROPERTYNAME, string, equal, compare to:[~] This should always result in a condition that causes the setup to abort and display a message to the end user. When I test this install, it seems to work in my development environment. However, when I copy it to a test virtual machine, the message box will not show up and the setup is hung. I have to use Task Manager to exit the setup. When I enable logging, I can see that the setup has evaluated the condition because my message is displayed in the log file. However, it is not displayed to the end-user.
... View more
Latest posts by DLeeRI
| Subject | Views | Posted |
|---|---|---|
| 81 | Oct 27, 2021 01:22 PM | |
| 111 | Sep 23, 2021 01:39 PM |
Activity Feed
- Tagged How to force a restart from InstallScript Custom Action using Suite Project file on InstallShield Forum. Oct 27, 2021 01:24 PM
- Tagged How to force a restart from InstallScript Custom Action using Suite Project file on InstallShield Forum. Oct 27, 2021 01:24 PM
- Tagged How to force a restart from InstallScript Custom Action using Suite Project file on InstallShield Forum. Oct 27, 2021 01:24 PM
- Tagged How to force a restart from InstallScript Custom Action using Suite Project file on InstallShield Forum. Oct 27, 2021 01:24 PM
- Posted How to force a restart from InstallScript Custom Action using Suite Project file on InstallShield Forum. Oct 27, 2021 01:22 PM
- Posted Re: IS Suite is stuck on splash screen while executing Launch Conditions on InstallShield Forum. Sep 23, 2021 01:39 PM
