MySQL Bugs: #59428: MySql Connector fails while updating machine.config

Bug #59428	MySql Connector fails while updating machine.config
Submitted:	11 Jan 2011 19:20	Modified:	12 Feb 2011 7:34
Reporter:	Chris Rokusek	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.3.6	OS:	Windows (Home 64)
Assigned to:		CPU Architecture:	Any

Description:
Unable to install mysql connector 6.3.6.  Ran as admin:

   % msiexec /l* log_file -i mysql.data.msi

From log file near error:

InstallFiles: File: TableEditor.build,  Directory: C:\Program Files (x86)\MySQL\MySQL Connector Net 6.3.6\Samples\Table Editor\vb\,  Size: 1314
Action 10:58:38: ManagedDataInstall. Registering data provider in machine.config
CAQuietExec:  Error 0x80070002: Command failed to execute.
CAQuietExec:  Error 0x80070002: CAQuietExec Failed

How to repeat:
Removing previous mysql connectors.  Install 6.3.6.

Tried custom install with no options except Core Components.

Tried moving all machine.configs to another name because I read somewhere that installer would skip the directory.

Grepped for existing mysql entries in machine.config, found none.

Now unable to re-install previous verions 6.3.5 nor 6.2.3 so am stuck.

Suggested fix:
This machine has 6 machine.configs all of which were moved out of the way as an attempt to get the install to skip.

Framework/v2
Framework/v4
Framework64/v2
Framework64/v4
etc/mono/2.0/
etc/mono/4.0/

The mono installation which has a machine.config which I may uninstall next.  Should that matter?  I can provide any of the machine.configs, knowing which one it failed on would help.  Is there a way to tell from the log?

It can be a duplicate of bug #59301. Do you have .Net framework set up somewhere not on C: ?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Posted by developer:
 
This bug was fixed by the same fix that applied to http://bugs.mysql.com/bug.php?id=59301 thus must be closed.