Bug 46070

Summary: MSI installer does not validate custom installation
Product: Apache httpd-2 Reporter: Gia Kien Tran <6174604>
Component: Win32 MSI InstallerAssignee: Apache HTTPD Bugs Mailing List <bugs>
Severity: normal Keywords: MassUpdate
Priority: P2    
Version: 2.2.10   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   

Description Gia Kien Tran 2008-10-22 22:28:20 UTC
This bug occurs when user try install a new Apache web server custom installation but left all the components unchecked. The msi installer doesn’t validate what the user has chosen and move to the last stage. Normally an Apache folder will be created under Program Files but it does not in our case.

Moreover, running the msi installer again we can see it is aware of this existing custom installation and give two options of Repair and Remove. After clicking Repair and it’ll run the repair procedure. However if you attempt to run the installer again, it will no longer give you the Repair and Remove options, that mean the previous repairing procedure caused the installation removed.

Steps to reproduce:
1. Download Apache HTTP Server 2.2.10 - Win32 Binary including OpenSSL 0.9.8i (MSI Installer) from http://httpd.apache.org/download.cgi
2. Install Apache HTTP server 2.2.10 with Custom installation chosen.
3. Uncheck all the Features except Apache HTTP Server 2.2.10 in the next screen and click Next, then wait till it finished.
4. Run the msi installer again and attempt to Repair.
5. Run the installer for the 3rd time, you can see now the previous installation has been removed despite Repair was chosen.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:03 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.