OK, I've built installer (call it main installer) that has 4 prerequisites: .NET Framework 4.0; .NET Framework 4.5; Installer Package 1 (IP-1); and Installer Package 2 (IP-2).
When I run main installer, the .NET Framework packages are detected as installed, and skipped. The two Installer Packages are not installed, prerequisites check box shows them checked, not found.
OK, then I click next, to run the prerequisites, and that seems to be the end of running the main installer. Neither IP-1 nor IP-2 run, no other installer dialogs display. Even though I have a verbose log option selected on main installer, no log file is generated.
When run on their own, outside of main installer, IP-1 and IP-2 both run with no problem. IP-1 and IP-2 are both of type Single .exe setup (resources inside), both built with AI.
Main installer has worked previously, but now the wheels fell off. Any ideas on how to tell what went wrong?
Thank you.
Suggested Articles
Re: Prerequisites do not install
Rebooting windows 7 fixed it, I should've known. Must be the old running out of open file descriptors. Not a very graceful way to handle things, the installer silently exits in this case. You get no indication, nothing, just a blank screen, and the user is wondering what is happening. The things software companies get away with nowadays.
Re: Prerequisites do not install
Hello,
I'm glad you got this working by yourself.
Our EXE bootstrapper is a wrapper over the MSI. When you have pre-install prerequisites, the bootstrapper installs them before it runs the MSI.
The "Enable verbose logging" option uses the default Windows Installer functionality regarding logging. So, the logging will start when the MSI is start, after the prerequisites are installed.
That is why no log is created in your situation.
In order to create a log when the bootstrapper is used, you can launch the EXE from command line with the following option /EXElog <path_to_log_file>.
For more informations about our bootstrapper check our EXE setup file article.
If you want to create installation logs for the prerequisites you can add the command line statements in the Install Command Lines field from the Prerequisite Setup Files Tab.
To specify the <path_to_log_file> you can use the TempFolder or Windows Volume property. For informations about these properties you can check Paths of the folders in the "Files and Folders" Page article.
If you have other questions, please let us know.
Best regards,
Dan
I'm glad you got this working by yourself.
Our EXE bootstrapper is a wrapper over the MSI. When you have pre-install prerequisites, the bootstrapper installs them before it runs the MSI.
The "Enable verbose logging" option uses the default Windows Installer functionality regarding logging. So, the logging will start when the MSI is start, after the prerequisites are installed.
That is why no log is created in your situation.
In order to create a log when the bootstrapper is used, you can launch the EXE from command line with the following option /EXElog <path_to_log_file>.
For more informations about our bootstrapper check our EXE setup file article.
If you want to create installation logs for the prerequisites you can add the command line statements in the Install Command Lines field from the Prerequisite Setup Files Tab.
To specify the <path_to_log_file> you can use the TempFolder or Windows Volume property. For informations about these properties you can check Paths of the folders in the "Files and Folders" Page article.
If you have other questions, please let us know.
Best regards,
Dan