Bug #20886 Server Instance Config Wizard
Submitted: 6 Jul 2006 9:51 Modified: 7 Jul 2006 12:08
Reporter: Jon Webb Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5022 OS:Windows (Windows Server 2003 R2)
Assigned to: CPU Architecture:Any

[6 Jul 2006 9:51] Jon Webb 
Description:
first installation on new server worked like a charm. (no problems)
After many 'developments' we wanted to go back to the original setup.

using the Server Instance Config Wizard, we see that innodb_data_home_dir is left out. (tried re-config, tried removing instance and adding new, tried uininstalling everything and starting from scratch). we did notice that the paths have \ in windows and in the documentation, but the my.ini writes / in all paths.
we are now trying: innodb_data_home_dir="C:/MySQL50datafiles/"

How to repeat:
on machine with mysql5011...
re-config instance
Config: Detailed, Server Machine, Transactional DB Only,
        Tablespace=C:\MySQL50datafiles\,
        Decision Support, Enable TCP (port3306), Enable Strict, 
        Standard Char Set, Install as Service, 
        Name=MySQL50, Lauch Auto, Include Bin Path,
        Root PW=blabla, 
        (Enable Root Acces from Remote = No, Create Annon Acc = No)
        Finished
start service fails (as usual for us, i assume restart is always needed)
[6 Jul 2006 12:28] MySQL Verification Team 
Thank you for the bug report.
When you did the intial setup, you selected the InnoDB files path?
Otherwise the innodb_data_home_dir is the data directory (this is
documented in the Manual). So try to setup my.ini file pointing
innodb_data_home_dir to your actual \data directory.
Also notice the service can be aborted if the data and log files
sizes are different than before created.
If you get a service start issue, try to see the error messages
starting the server as standaloen within a DOS prompt:

mysqld-nt --defaults-file="path_for_my.ini" --standalone --console

Thanks in advance.
[6 Jul 2006 18:21] Jon Webb 
To fix these issues, we uninstalled mysql. We also deleted the mysql folder (as there are still bits left over), and we went to REGEDIT and deleted as many keys as we could that still related to mysql.
Next we reinstalled mysql, run the instance wizard, and everything works like a charm.

So the solution: uninstall, manually remove any folders, manually remove any keys. (obviously, with great care!)
Thanks, Jon
[7 Jul 2006 12:08] MySQL Verification Team 
Thank you for the feedback. I am closing this bug report however
as a note we don't recommend to use REGEDIT as a normal procedure
for to resolve installation issues.