Bug #7548 Unable to complete installation of 4.1.8 after mulitple installs
Submitted: 27 Dec 2004 18:15 Modified: 6 Jan 2005 23:18
Reporter: Mark Truluck Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:4.1.8 OS:Microsoft Windows (Windows XP SP2)
Assigned to: Michael G. Zinner CPU Architecture:Any

[27 Dec 2004 18:15] Mark Truluck
Description:
I have a new Windows XP SP2 Dell Latitude D800 w/ 1GB Ram & 60MB HD and installing 4.1.8.  I have done this a number of times, running both install and uninstall through MSI, and can not, unfortunately, give exact repro steps.  I also tried to installl 4.0.23 after the first failure, but subsequently deleted it - I don't know if this caused any issues (none that I can figure out,anyway ).  However, the end result is that when running the 4.1.8 setup, I am now unable to successfully complete the installation. 

On the MySQL Server Instance Configuratoin Wizard I choose:

Install as a "typical" installation

Developer Machine
Transactional DB
Decision Support
Enable TCP/IP on 3306
Best support for multilingualism
install as service/include bin dir in windows Path
I have a root password but no anonymous account
When I press execute, it successfully prepares the config, writes the config file, starts service ( I verified in the services list ) but fails to apply security settings.  The error message is: "The security settings could not be applied. Error Number 2017.  Can't open named pipe to host:. pipe:mysql(2).

Uninstall does not fully clean the files, so I also had an issue with running the server as standalone.  I subsequently deleted the files by hand.

The following is the output from my attempt to do this manually:

C:\Program Files\MySQL\MySQL Server 4.1\bin>mysqld-max-nt.exe --console
InnoDB: Error: log file .\ib_logfile0 is of different size 0 18874368 bytes
InnoDB: than specified in the .cnf file 0 5242880 bytes!
041227  9:16:26 [ERROR] Can't init databases
041227  9:16:26 [ERROR] Aborting

041227  9:16:26 [Note] mysqld-max-nt.exe: Shutdown complete

<-- here I renamed the \.ib_logfile[01], .\ibdata1 & markt.err files -->

C:\Program Files\MySQL\MySQL Server 4.1\bin>mysqld-max-nt.exe --console
InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
041227  9:18:29  InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
041227  9:18:29  InnoDB: Log file .\ib_logfile0 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
041227  9:18:29  InnoDB: Log file .\ib_logfile1 did not exist: new to be created

InnoDB: Setting log file .\ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
041227  9:18:37  InnoDB: Started; log sequence number 0 0
mysqld-max-nt.exe: ready for connections.
Version: '4.1.8-nt-max'  socket: ''  port: 3306  Source distribution

How to repeat:
Install on a similar machine and install, uninstall several times.  Setup should fail, as should connecting via the client box or a dos box using "mysql -u root -p".
[27 Dec 2004 22:22] Miguel Solorzano
Are you using the same values for InnoDB files sizes for every
install you did ?
Notice that when un-installing the MySQL installer not removes
the files created by InnoDB or any new database created.
[6 Jan 2005 23:18] Michael G. Zinner
I think this is related to the fact that the data directory is not removed automatically when you uninstall the server.

Therefore, if you have set a root password for the original installation, de-install and reinstall using a different password will fail.

The Configuration Wizard now presents a dialog informing about that fact. The simple workaround is to re-execute the Configuration Wizard from the Windows Start Menu and specify the old password on the Security Settings page.

I closed this bug for now. Please verify the fix with 4.1.9.
[4 Oct 2012 6:50] Marko Mäkelä
For what it is worth, Bug#13494 will be fixed in MySQL 5.6.8.