MySQL Bugs: #68440: Installer throws exception Index 0 is out of range

Bug #68440	Installer throws exception Index 0 is out of range
Submitted:	20 Feb 2013 4:05	Modified:	22 Jul 2015 21:59
Reporter:	Brian Castro	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL for Windows: Installer	Severity:	S2 (Serious)
Version:	5.6.10.1	OS:	Windows (Windows 8, x64)
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
Using MySQL Installer 5.6.10.1, Index 0 is out of rage is thrown. Having issues with bug #68381, I was trying different configurations to see if one would succeed, none did.

How to repeat:
After the service configuration failure, select try again, just checking and unchecking "Show advanced options" checkbox on the configuration page right before the root password page and continuing with the install attempt, the exception is thrown.

Since I can't get MySQL Server installed due to bug #68381, I have no way to verify if this would too happen on a successful installation.

Suggested fix:
Not select this option at all, or if selected leave it that way and this goes away.

Hello Brian,

are you experiencing this on a localized (non-english) windows version?

Also, with 5.6.10.1 that service configuration err appears fixed on all of our test machines - did you try a new installation with 5.6.10.1 from scratch? If not, please remove the MySQL Products (using installer) incl. the installer itself and try again from the 5.6.10.1 package.

thanks in advance
tax

Hi Tax, I have a clean en-US Windows installation and the same goes for MySQL, or at least I'm trying to get it installed.

These are the different errors (a new message after *****) that I show in the windows logs:

======== Unhandled exception ========
------------------Exception: Index 0 is out of range.
Parameter name: index

Stack Trace
   at System.Windows.Forms.Control.ControlCollection.get_Item(Int32 index)
   at WexInstaller.InstallWizardControl.get_CurrentPanel()
   at WexInstaller.MainForm.CanClose()
   at WexInstaller.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
   at System.Windows.Forms.Form.RaiseFormClosingOnAppExit()
   at System.Windows.Forms.Application.ExitInternal()
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at WexInstaller.Program.Main()

======== End Unhandled exception ========

*****************************************************************************

The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Aborting

the message resource is present but the message is not found in the string/message table

*****************************************************************************
The description for Event ID 100 from source MySQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

the message resource is present but the message is not found in the string/message table

*****************************************************************************

The MySQL Server service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.

*****************************************************************************

A timeout was reached (30000 milliseconds) while waiting for the MySQL Server service to connect.

Was tested against 1.4.9 and we weren't be able to reproduce it, 1.4.X redo all the configuration wizard, we added more verfications and locks to prevent the configuration wizard crash.

this bug is not hppening anymore in recent bundles