MySQL Bugs: #31674: service doesn't start after upd 5.1.19 to 5.1.22 because mysqld-nt.exe renamed

Bug #31674	service doesn't start after upd 5.1.19 to 5.1.22 because mysqld-nt.exe renamed
Submitted:	17 Oct 2007 20:19	Modified:	30 Jul 2008 14:53
Reporter:	Carsten Segieth	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S3 (Non-critical)
Version:	5.1.22	OS:	Windows (2003, XP)
Assigned to:	Iggy Galarza	CPU Architecture:	Any

Description:
When updating on Windows from 5.1.18 or .19 to 5.1.22, using the ...essential...msi, the updated server does not start. The MySQL Server Instance Configuration Wizard shows "Error: 0".

Problem is, that with 5.1.22 there is no "mysqld-nt.exe" in the package, only a "mysqld.exe". From this the 'ImagePath' in the service entry in the RegDB is wrong.

After changing the file name in 'ImagePath' from "mysqld-nt" to "mysqld" the service started as expected.

How to repeat:
- install 5.1.18 essential.msi
- configure the server (I used 'MYSQL_51' as service name)
- start the server from the configuration wizard

- launch 5.1.22 essential.msi, re-configure the server
- try to start it from the config wizard, see that this fails
- open RegDB, go to HKLM/System/CurrentControlSet/Services/MYSQL_51
- change value of 'ImagePath' as noted above
- click BACK in configuration wizard and try again to start the server

Suggested fix:
the Configuration Wizard needs to update the RegDB entry

I have this error. Similar experience except I was not upgrading from version x to 5.1.22.  I have version 5.1.22 on my computer, it just stopped working. I uninstalled and reinstalled the server and dot net connector from the original zip files that I downloaded from one of your mirror sites.  When I run the configuration Wizard I get the error;
"Could not start the service MySQL.Error 0" 
I could not manually start the service from control panel applet but this time got a different error;
"Error 1067: The process terminated unexpectedly"
I went to the event viewer where I found the following four items;
1. "Plugin 'InnoDB' init Function returned error."
2. "Plugin 'InnoDB' registration as a STORAGE ENGINE failed."
3. "Unknown/unsupported table type: INNODB"
4. "Aborting"
5. "C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown Complete"

I followed the suggested resolution in the original bug report #31674 but my machine didn't have any references to mysqld-nt.exe. The ImagePath data from my regdb is below;
"'C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld' --defaults-file='C:\Program Files\MySQL\MySQL Server 5.1\my.ini' MySQL"

Can anyone suggest a solution to me please.

workaround: change the name in the registry manually

I'm experiencing the same problem. Can you please expand on the prior comment (i.e., change the value in the registry manually). What value should be changed? From what to what?

Thanks for your help.

Verified that an upgrade is detected, the user is informed of the change and is prompted to approve the necessary changes for the upgrade to be successful, and that the installation works properly after being given user approval.

Ok to push.

A note has been added to the 5.1.24 changelog (change affects other versions, but the problem only affect 5.1): 

When upgrading from MySQL 5.1.19 to any version between MySQL 5.1.20 to MySQL 5.1.23, the MySQL	Instance Configuration Wizard would fail to account for the change in name for the mysqld-nt.exe to mysqld.exe, causing MySQL to fail to start properly after the upgrade.