Binary distributions of Apache since 2.0.39 have not been able to be installed as a service under Windows 2000 from the MSI package. What happens is the installation program seems to run perfectly, and claims to have completed successfully. But the little tray icon with the feather in the bottom right of the screen shows a red mark in the circle, raqther than a green mark, and further inspection shows no service has been installed under windows, even though one has been requested during installation. I assume most of us are still running ver. 2.0.39 under windows 2000, because that is the last distribution which actually installs itself as a service from the MSI package. This has me a bit worried, as I would like to get the security fixes available since then.
I won't ask you why you want to run a vulnerable (.39 revision) server. All of the packages successfully install the service. None of them can install the service if you ALREADY have a web server running on port 80. After you REMOVE or STOP the running server (use the command netstat -an to decide if a server is running on port 80), or you modify your httpd.conf file to Listen on a different port, you may use this command from your installed Apache2 directory (usually c:\program files\apache group\apache2) bin\apache -k install -n Apache2 If it can't install, it will yell at you. Future releases will yell at you during installation, but that required the -w option that was just introduced in 2.0.43 (it holds the window open if there is an error, even within the .msi installer, when it's specified.)
Thanks you for the solution you suggest. Unfortunately it does not resolve issue. I am familiar with installing Windows software, and did try to install only after having stopped the Apache service, the MSI prompts to uninstall!! manually -- in addition to stopping the service. And I did thistoo . After uninstalling and removing the previous version from the system, your comment about bin\apache -k install -n Apache2 is perhaps helpful, but still not a resolution. The command you describe results in report of a failure to load "cannot execute C:\php\SAPI\php4apache2.dll"
This bug, too, will be addressed by the installer as of 2.0.44. It won't successfully install [you have plugged in php4apache2.dll built for an older version of Apache! Get an updated binary first!] The console slammed closed because we didn't put the 'hooks' in early enough to report some errors and keep the window open until you dismissed it. So this result is by design, and you need to update your module. We need to release 2.0.44 so users can SEE the problem when attempting to install.
Of course before reporting a bug I did upgrade to the latest version of PHP -- just as I tried to upgrade to a later version of Apache2. I suppose from what you have written that the versions of Apache after 2.0.39 have not worked with any of the available PHP-for-Apache2 distributions. In case I have not understood what you write, is it true that if we want Apache2 with PHP, then the lastest version of Apache we can use is 2.0.39?
*** Bug 14802 has been marked as a duplicate of this bug. ***