Bug #13093 Windows installer is unable to overwrite service even though it asks about it
Submitted: 9 Sep 2005 16:58 Modified: 3 Apr 2006 13:33
Reporter: Sergey Petrunya Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:4.1.14, 5.0.13-rc OS:Windows (Windows XP SP2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[9 Sep 2005 16:58] Sergey Petrunya
Description:
When one installs 4.1 from Setup.exe-based installer and wants to create the service,
the installer pops a message box "A windows service with name MySQL already exists. Are you sure you want to use this service name?". (1)

If one clicks yes, on next screen one gets "Cannot create windows service for MySQL. Error: 0." message. 

In my view, if an installer got "Yes" for question (1), it should be able to overwrite the existing service. If it cannot overwrite the existing service it should not allow the user to proceed until a different service name is selected.

How to repeat:
Get any "No install" binary. 
Run mysqld --install so you have a MySQL service installed.
Then get 4.1.14 installer (Setup.exe based)
Select full install and then press next/Yes until you get a message box
"A windows service with name MySQL already exists. Are you sure you want to use this service name?".
Answer yes.
On next screen click "Execute".
See the installer fail with  "Cannot create windows service for MySQL. Error: 0." message.

Suggested fix:
Make installer be able to overwrite the service.
[9 Sep 2005 18:24] MySQL Verification Team
I was able to reproduce with typical install option, using custom option
has another behavior.
[7 Oct 2005 15:35] Valeriy Kravchuk
The same behaviour of 5.0.13-rc installer, even with suggestions, is described in http://bugs.mysql.com/bug.php?id=13846, marked as a duplicate of this report.
[9 Oct 2005 2:10] Steve Owens
I get the same issue even though I have removed the installation, removed the windows service, reinstalled the installation, an run the configuration wizard again.

I even used MikesServiceRemover and reproduced the problem.  No matter what I do, it fails to work.  Get the red x when starting the service and I get the following lines in the .err file:

051008 21:57:48 [ERROR] mysqld: Got signal 11. Aborting!

051008 21:57:48 [ERROR] Aborting

051008 21:57:48 [Note] mysqld: Shutdown complete
[9 Oct 2005 2:19] Steve Owens
051008 22:14:49  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
051008 22:14:49  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43634.
InnoDB: Doing recovery: scanned up to log sequence number 0 43634
InnoDB: Page directory corruption: supremum not pointed to
051008 22:14:49  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex <<< a whole mess of zeores >>>
 asc                                                                                                                                                          <<a whole bunch of white space>>

051008 22:14:49  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
051008 22:14:49  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 
<<< a whole bunch of zeroes >>>>
 asc                                                                                                                                                          <<a whole bunch of white space>>
                                                                                                                   ;InnoDB: End of page dump
051008 22:14:49  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
051008 22:14:49 [ERROR] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld: Got signal 11. Aborting!

051008 22:14:49 [ERROR] Aborting

051008 22:14:49 [Note] C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld: Shutdown complete
[17 Oct 2005 3:11] Jeff Davis
Tried using a different service name, "MySQL2" which died at the "Write Configuration file" step with note "The template configuration file cannot be found at C:\Program Files\MySQL\MySQL Server 4.1\bin\my-template.cnf."
MySql service did install prevously but doesn't have the security password... I wish I could find the SQL scripts that finish the install to try by hand...
[3 Apr 2006 13:33] Michael G. Zinner
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html