os-windows/4939: Installing on top of 1.3.6 caused Apache 1.3.9 to fail to start as service

[Ivan Van Laningham <iv...@callware.com>]

>Number:         4939
>Category:       os-windows
>Synopsis:       Installing on top of 1.3.6 caused Apache 1.3.9 to fail to start as service
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Aug 31 15:00:04 PDT 1999
>Last-Modified:
>Originator:     ivanlan@callware.com
>Organization:
apache
>Release:        1.3.9
>Environment:
Windows NT 4.0, Build 1381, Service Pack 5
Binary installation.  AMD K6 200, 128MB memory.
NT Resource Kit *Not* installed.  (I have instsrv.exe, etc., in the system32
directory, but I had no use for anything else from the RK on this system--it's
weak enough without extra cruft.  I've never even tried to run IE on it.)
>Description:
I installed 1.3.9 on top of 1.3.6, which had been working
flawlessly since it was released.  I did stop 1.3.6; after installation, I
used the menu entry to try to install as service, and that failed silently.
Attempting to use the SCM to start Apache failed with Error 1067, "Application
terminated unexpectedly."  Using instsrv worked, but the SCM still wouldn't
start Apache.  Using menu entries to start it worked, but it *always* put up
a DOS box regardless of the method I chose, so it was always a console app.

In order to get it working, I had to completely uninstall 1.3.6, including the
removal of all the registry entries.  I had to manually remove the Apache
service from the SCM (the uninstall ought to do this for me).
I then re-installed 1.3.9, and used the
menu entry to register the service.  Again, this failed silently.  Using cmd
line instrv worked, but *failed* to install the Apache entry in the SCM!

"apache -i -n Apache" from the command line *did* make Apache show up as a
SCM entry, and starting from there works now.
>How-To-Repeat:
See "Full Description."
>Fix:
Well, the workaround is to tell people to uninstall previous installations
first; I don't know enough about InstallShield to be able to suggest a
fix.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]