I'm using InstallAware 7 to create a desktop installer that installs a MS Outlook plug-in. Since we want to support both local administrators and non-local administrators we are installing all dependancies into the targetdir. The issue I'm having is that when installing patches the patch always comes back during installation with the message "You must restart your system for the configuration changes made to [program name] to take effect. Click yes to restart now or No if you plan to manually restart later."
Of course, the machine doesn't need a reboot since everything is being installed locally not in any shared directory and I terminate both our program and MS Outlook before the installation so no files should be in use. Is there anyway to get around this error or ignore it somehow in the script? I've searched and can't find where this error comes from since it doesn't appear in the MSIcode.
Installer claims reboot is required after patch
-
- Site Admin
- Posts: 364
- Joined: Mon Jul 30, 2007 11:51 am
- Location: USA
- Contact:
If you are totally positive that no reboot is required, then set variable REBOOTCOMPUTER to FALSE after the apply install.
Alejandro Ronquillo
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Re: Installer claims reboot is required after patch
Hello,
I'm facing the same problem.
The only difference is that I'm testing on VISTA OS 64bit.
Your suggestion to set the variable REBOOTCOMPUTER to FALSE after the apply install doesn't solve the problem.
Any other suggestion?
Regards,
Emmanouel
I'm facing the same problem.
The only difference is that I'm testing on VISTA OS 64bit.
Your suggestion to set the variable REBOOTCOMPUTER to FALSE after the apply install doesn't solve the problem.
Any other suggestion?
Regards,
Emmanouel
Re: Installer claims reboot is required after patch
Emmanouel,
It would be nice if we could isolate the cause of this behavior. What version of InstallAware are you using?
I've never seen this sort of behavior on a simple installer. Is there any way you can try to provide instructions or create a sample project that exhibits this behavior?
Perhaps you can comment out blocks of code to help isolate the problem.
It would be nice if we could isolate the cause of this behavior. What version of InstallAware are you using?
I've never seen this sort of behavior on a simple installer. Is there any way you can try to provide instructions or create a sample project that exhibits this behavior?
Perhaps you can comment out blocks of code to help isolate the problem.
Andy Mills
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
InstallAware
Other Help:
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Product Guides - http://www.installaware.com/publication ... guides.htm
InstallAware Help - Press F1 in the InstallAware IDE.
Who is online
Users browsing this forum: No registered users and 86 guests