After successfully completing step 1 and 2, at step 3 (Start service) it fails with the error "Could not start the service MySQL.Error:0" After looking for what may be causing this for a while, I finally found out the cause; I went to Administrative Tools, Services, and went to the service MySQL in that list (generated by the InstanceConfig tool), and checked its properties. For Path to exacutable: I found this in the line there: "...Wamp\bin\mysql\mysql5.0.45\bin\bin\mysqld-nt" --defaults-file=...".

The problem is caused at the "\bin\bin\" part. There should only be one bin, "\bin\". "...\mysql5.0.45\bin\mysqld-nt..." would be the correct path. Posted in this screenshot here [img223.imageshack.us] . So this error is caused by that file being generated like that. And I cannot manually change that path either, because if I do the InstanceConfig then tells me there is already a MySQL service running and I must remove that one before running it. Its InstanceConfig that must generate it correctly.



=========================================================

Never mind, I managed to fix it. The problem with the bin/bin (or bin\bin) path was in the registry key HKEY_LOCAL_MACHINE -> SOFTWARE -> MySQL AB -> MySQL Server 5.0 -> Location , where the location of MySQL Server 5.0 was actually into bin subfolder instead of being only into the MySQL folder. I had to delete the \bin at the ending of that path and it seen it correctly after that.

There was another bug afterwards, about the service "terminating unexpectedly" which was fixed by deleting the files ib_logfile0 ib_logfile1 and ibdata1 from the folder Data like written in another bug on mysql.com. Now it all works well again