Bug #72075 Unhanded Exception: Current profile has no WMI enabled
Submitted: 19 Mar 2014 11:52 Modified: 26 Apr 2014 15:30
Reporter: Mark Rouse Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.0.8 OS:Windows (64-bit XP)
Assigned to: CPU Architecture:Any

[19 Mar 2014 11:52] Mark Rouse
Description:
Brand new clean installed using the Windows Installer package of MySQL 5.6.16.0 community edition.  I run through the steps in the Wizard; everything installs fine,; I configure the server no problems.

When I logged into the server through the workbench, and select the Options file, I get the following errors:

Runtime error: Unable to execute command chcp.  Please make sure that the C:\Windows\System32 directory is in your PATH environment variable.  I check it is.

I also get the Unhanded Exception: Current profile has no WMI enabled error

How to repeat:
Install using the Windows Intstaller package
[19 Mar 2014 13:00] MySQL Verification Team
Please try version 6.1.2. Thanks.
[19 Mar 2014 13:41] Mark Rouse
Have tried version 6.1.2 of the Workbench and I still get the same error.
[19 Mar 2014 15:37] Mark Rouse
The Windows Installer automatically puts the data and my.ini in the following location:

c:\Documents and Settings\All Users\Application Data\MySQL\MySQL Server 5.6\my.ini.

Is this correct?  Should it not point to a c:\ProgramData\MySQL\MySQL Server 5.6 folder instead?
[19 Mar 2014 15:41] Mark Rouse
Add the MySQL56 service points to the defaults-file as:

c:\Documents and Settings\All Users\Application Data\MySQL\MySQL Server 5.6\my.ini.
[26 Mar 2014 15:30] MySQL Verification Team
Thank you for the feedback. If you change the path for the my.ini file editing the server profile in the Manager Server Instances dialog fix the issue?.
[27 Apr 2014 1:00] Bugs System
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".