Bug #8895 Configuration Wizard fails against a 4.0x installation
Submitted: 2 Mar 2005 17:09 Modified: 7 Mar 2005 12:22
Reporter: Steven Casey Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:MySQL Configuration Wizard 1.04 OS:Windows (Windows 2K)
Assigned to: CPU Architecture:Any

[2 Mar 2005 17:09] Steven Casey
Description:
Using the Configuration wizard against a 4.0.23 database, fresh installation.  The wizard places an extra \bin in the path and also in the registry for starting the server.  Hence, it places <installation_dir>\mysql\bin\bin in the path.  I've modified the path so it reflects the true path, also mae the change in the registry, but it still fails to start the service  I'm suspecting it's wrong parameters set in the my.ini, or the win.ini being put in the wrong place.  Will test further

How to repeat:
run the installation of 4.0.23.  Put the Configuration Manager executable, the template file and the win.ini in the <install dir>\mysql\bin.  Launch the wizard, specify your parameters, then execute.  The server will fail to start.

Suggested fix:
So far, modifying the PATH in the environment variables, and also in the registry, got me closer.  I suspect the win.ini has the wrong parameters as well, or is being put in the wrong place.
[2 Mar 2005 23:12] Steven Casey
sorry...the win.ini mentioned should have been the my.ini...sorry for the confusion.
[3 Mar 2005 3:34] Steven Casey
traced down the problem entry in the my.ini to the following "innodb_log_file_size ="
It really doesn't like it.  If I put it at the end of the file, the service starts ok.
[7 Mar 2005 12:22] Michael G. Zinner
The Configuration Wizard only works with 4.1 servers as e.g. names of binaries have been changed. As 4.1 is now in GA there is no reason why one should not upgrade from 4.0

Therefore we have currently no plans to extend the Config Wizard to deal with 4.0 installations due to a limitation of resources.