MySQL Bugs: #25717: 'unidentified' error installing & configuring 5.1

Bug #25717	'unidentified' error installing & configuring 5.1
Submitted:	19 Jan 2007 10:52	Modified:	20 Feb 2007 15:33
Reporter:	Yahoo Serious (Silver Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	5.1.14	OS:	Windows (Windows 2000 SP4)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	qc

Description:
I have a Windows 2000 (test/development) system with MySql 4.1 and 5.0 installed.  I am trying to add 5.1 as typical as possible.  So I use the installer, and after that the configurator.  When it finishes (tries to start the service?) it gets an 'unidentified' error.

How to repeat:
( - maybe install MySql 4.1 (port 3306) and 5.0 (port 3307) first, make sure they do not start up automatically and are not running.)
 - start installation of mysql-essential-5.1.14-beta-win32.msi
 - choose "Custom", change default path to "E:\..."
 - press "Back", choose "Typical"
 - choose "Skip sign-up"
 - choose "Configure ... now", and press "Finish"
 - choose "Standard configuration"
 - keep "Install .... service",
   change name to "MySql51", and
   choose NOT to "Launch ... automatically"
 - choose NOT to "Modify security settings"
 - press "Execute"
( - press "Finish"??
I re-installed to reproduce all the steps, but I don't remember this last "Finish")
>> Note the 'obscure' error message
(If reconfiguring with the Configuration Wizzard I get an extra application error before this error.)

Suggested fix:
good luck.

Runtime error 216 at 00403D76

Attachment: Mysql51ConfigError.jpg (image/jpeg, text), 4.80 KiB.

Application error: instruction at 00403D76 referenced memory at 0x00f42d18

Attachment: Mysql51ConfigApplicError.jpg (image/jpeg, text), 16.68 KiB.

Have you installed 4.1 and 5.0 with the same procedure (using the installer)?.
Thanks in advance.

Yes, using the installer.  
But I installed them with more custom parameters, I can attach the ini's if that would help.  
BTW, the MySQL4-service is called "MySQL", the MySQL 5.0 service "MySQL5", maybe that matters too?  Both were not running though and I was calling MySQL 5.1 service "MySQL51".

Please, try to repeat with a newer version, 5.1.15, and inform about the results. What port did you use for 5.1?

I did not reproduce it (but did not try extensively), so it seems to be fixed in 5.1.15
(I used the default, port 3306, for 5.1 also)