Why you might ask would I want to install an old, depreciated version of Apache (v1.3.41) on a Windows 2008 x 32 server instance. Well, in this case I have an application that I need to support that uses a very old version of cold fusion that only supports 1.3.x, so I don't have a choice.
This should however have been a pretty straight forward process, download apache, install it as service, start the service, confirm that it returns the default webpage, then get the application configured and running. The only problem is that Apache would not start as a service after the installation. It ran just fine from the command line, but when started as a service it would raise an error 1067 and exit. The error in the event log is:
Faulting application Apache.exe, version 0.0.0.0, time stamp 0x478f7539, faulting module ApacheCore.dll, version 0.0.0.0, time stamp 0x478f7537, exception code 0xc0000005, fault offset 0x00026a7b, process id 0x9e4, application start time 0x01cca96325cefb6e.
Turns out that Windows 2008 has this security feature called "User Account Control" that prevents apache from installing properly as a service. This can be disabled by clicking on Control Panel-> User Accounts. Turn it off, reboot, and reinstall apache and everything is fine.
Oh, don't turn UAC back on or Apache will again refuse to start with a 1067 error. I'm sure there is a good reason and a workaround, but I don't think it is worth spending anymore time on.