MySQL Bugs: #65165: current ver == cluster gpl 7.2.5 win x64 msi fails to start MySQL service causin

Bug #65165	current ver == cluster gpl 7.2.5 win x64 msi fails to start MySQL service causin
Submitted:	1 May 2012 17:14	Modified:	5 Oct 2016 22:33
Reporter:	no one important	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S1 (Critical)
Version:	7.2.5 x64	OS:	Windows (msi x64 installer)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	cluster, fails start service, msi installer, x64

Description:
The current downloadable version of msi cluster does not install.
Bug reproduced on several machines OS independent (limited to MS OS). 
Appears on finalising stage of install independent of selected options.

Bug source: MySQL service is installed with incorrectly defined path.
ie.
"C:\mysql\bin\bin\mysqld" --defaults-file="C:\mysql\bin\my.ini" MySQL
where should be:
"C:\mysql\bin\mysqld" --defaults-file="C:\mysql\bin\my.ini" MySQL

VERY frustrating HARD to find on remote nodes without proper access to system logs.

Not sure where to report my two cents:
On Polish SunSITE the file extension is wrong mysql-cluster-gpl-7.2.5-winx64.man instead of *.msi

How to repeat:
Run mysql-cluster-gpl-7.2.5-winx64.msi, go through config despite options...

Suggested fix:
Correct the path in installer binnaries/config to avoid duplicate /bin folder path.

Would be a lame if not post this ;P
Of course there is a work around:
Manualy or by script change in Registry Editor:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MySQL(if MySQL is the name of the service provided in installer) data value of ImagePath field:

"C:\mysql\bin\bin\mysqld" --defaults-file="C:\mysql\bin\my.ini" MySQL

to the correct one:
"C:\mysql\bin\mysqld" --defaults-file="C:\mysql\my.ini" MySQL.

This is a dirty slow men and time consuming proces, because the installer will still fail causing need to manually add/change security settings.
This is not a 100% workarround or fix - on some machines running w2k8r2 for unknown reasons service fails to start producing 

"Error 1067:The process terminated unexpectedly." 
or 
"Error 1053:The service did not respond to the start or control request in a timely fashion."

Leaving absolutelly no log traces or whatsoever which is at least weird!
No workaround on those machines was developed nor found.

Further digging resulted in next error discovery - probable cause of one of the above errors.
When trying to manually run mysqld error message pops up after commiting command.

120501 11:0707 [ERROR] Error message file 'C:\mysql\share\english\errmsg.sys' had only 722 error messages,
but it should contain at least 724 error messages.
Check that the above file is the right version for this program!

CHECKED, it is... previous versions of that sys shout in the same manner with slightly differed output (no. of err. msg.)

It's realy a pain in....

Confirmed from Japan!

Confirmed from france.
Found some more errors

the wizard C:\Program Files\MySQL\MySQL Cluster 5.5\bin\MySQLInstanceConfig.exe
cannot find my-template.cnf file

Solution:
copy my-template.ini frm mySql installation folder 
paste it into bin folder
rename my-template.ini to my-template.cnf

Service path not correct ( as already posted )
should be
"C:\Program Files\MySQL\MySQL Cluster 5.5\bin\mysqld.exe" 

Path variable to edit and change
....;C:\Program Files\MySQL\MySQL Cluster 5.5\bin\bin\;
to  ;C:\Program Files\MySQL\MySQL Cluster 5.5\bin

its not possible to complete the wizard, because when the first service create fail,  when edition the service path, the wizard fail again with an error saying the service already exist ....

It's like all was done to force people to not use this version ....

7.2.5 x64 -> reproduced, easily
7.2.24 x64-> can't reproduce