Bug #37641 Cannot create Windows service for MySQL.Error: 0
Submitted: 25 Jun 2008 18:03 Modified: 26 Jun 2008 18:53
Reporter: Keith Collie Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Config Wizard Severity:S2 (Serious)
Version:5.0.51b OS:Windows (XP)
Assigned to: CPU Architecture:Any

[25 Jun 2008 18:03] Keith Collie
Description:
Receiving the indicated error after clicking the "Execute" button in the "MySQL Server Instance Configuration" wizard. First of all, I did not accept the default installation path. I selected a path on a different partition containing more available space. The "path" variable was set correctly, but when I opened the Services dialog, the path to "mysqld-nt.exe" was set incorrectly to a path on the C: drive. I changed it the registry and the MySQL service was then able to start, but I still get the error indicated with a red "x" in the "Start service" listing.

How to repeat:
1. Launch the MySQL Server Instance Configuration Wizard and click "Next".
2. Accept the default "Detailed Configuration" option and click "Next".
3. Accept the default "Developer Machine" option and click "Next".
4. Accept the default "Multifunctional Database" option and click "Next".
5. Select a different drive partition for the InnoDB tablespace installation path and click "Next".
6. Accept the default "Decision Support (DSS)/OLAP option and click "Next".
7. Select "Enable TCP/IP Networking" and "Enable Strict Mode", then click "Next".
8. Accept the default "Standard Character Set" option and click "Next".
9. Select to "Install As Window Service", "Launch the MySQL Server automatically"
   and "Include Bin Directory in Windows PATH" options, then click "Next".
10. Enter and retype the root password, do not create an anonymous account,
   then click "Next".
11. Click "Execute" and note the failure at "Start service".
[26 Jun 2008 4:49] Valeriy Kravchuk
Thank you for a problem report. Please, specify the exact version, 5.0.x, of MySQL server used.
[26 Jun 2008 12:31] Keith Collie
Exact version amended.
[26 Jun 2008 12:32] Keith Collie
Update: After uninstalling then reinstalling, the problem did not appear.
[26 Jun 2008 18:49] Valeriy Kravchuk
So, I assume this is not a bug.
[26 Jun 2008 18:53] Keith Collie
It may be that the port is not opened on initial installation attempt, when Windows Firewall is running.
[11 Mar 2011 6:17] Venkatesh Sheshgiri
Try to give a different port number other than 3306, I tried it and the problem was solved.