Bug #65942 I can't create a new server instance in Workbench 5.2.40 CE, the error is "Could
Submitted: 18 Jul 2012 16:05 Modified: 30 Sep 2012 20:25
Reporter: Amin Chavarria Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.40 OS:Windows (Vista Home Premium SP2)
Assigned to: CPU Architecture:Any

[18 Jul 2012 16:05] Amin Chavarria
Description:
I can't create a new server instance in Workbench 5.2.40 CE, the error is "Could not connect to target machine".

The windows service "MySQL" is running.
I'm logged on as Administrator.

SO: Windows vista SP2
Server MySQL: 5.1.43-community

The service is running, this is my output:

C:\Users\amin>NET start
Se han iniciado estos servicios de Windows:

...
Llamada a procedimiento remoto (RPC)
McAfee Framework Service
McAfee McShield
McAfee Task Manager
MySQL ===========================> is running
NVIDIA Display Driver Service
O2FLASH
...

Se ha completado el comando correctamente.

MySQL is using port 3306, this is output

-- 
C:\Users\amin>mysql --host=localhost --user=root --password=anaconda --port=3306 mydb
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 6
Server version: 5.1.43-community MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> status
--------------
mysql Ver 14.14 Distrib 5.1.43, for Win32 (ia32)

Connection id: 6
Current database: mydb
Current user: root@localhost
SSL: Not in use
Using delimiter: ;
Server version: 5.1.43-community MySQL Community Server (GPL)
Protocol version: 10
Connection: localhost via TCP/IP
Server characterset: latin1
Db characterset: latin1
Client characterset: latin1
Conn. characterset: latin1
TCP port: 3306
Uptime: 4 min 35 sec

Threads: 3 Questions: 40 Slow queries: 0 Opens: 66 Flush tables: 1 Open tables: 9 Queries per second avg: 0.145
--------------

mysql>
-- 

the full error message is:

-- 
[window title] "Error Starting Workbench Administrator"
Error Message: "runtimeError: Could not initialize WMI interface:
Workbench.wmiOpenSession(): Could not connect to target machine.

No se puede encontrar el módulo especificado 

How to repeat:
Open MySQL WorkBench and create a new server instance.

Suggested fix:
NA,
[18 Jul 2012 17:16] Valeriy Kravchuk
What exact version of Workbench do you use, 5.2.31 as noted in version field, or 5.2.40? Please, clarify.

wb.out is the log file you are looking for.
[18 Jul 2012 18:28] Amin Chavarria
Hi all,

I installed MySQL Workbench 5.2.16 OSS Beta and the error is not present.

I'll try with MySQL Workbench 5.2.40 CE again.

regards
[18 Jul 2012 18:32] Amin Chavarria
Hi Valeriy Kravchuk,

The version correct is Workbench 5.2.40

regadrs
[18 Jul 2012 18:40] Amin Chavarria
My results: I installed MySQL Workbench 5.2.40 again and I get  same error.
I notice that Firewall WIndows is not running, this affects?

Regards
Amin
[14 Aug 2012 12:14] C.A. Pelle
Seems I've got the same problem over here.
Just tried to update to 5.42, but problem is still there.
Is there any news for this one?

Regards,
CaP.
[15 Aug 2012 12:09] MySQL Verification Team
Please try version 5.2.42. Thanks.
[15 Aug 2012 17:18] Amin Chavarria
I installed new MySQL Workbench 5.2.42  and I get  same error.  Regards Amin

Attachment: 15-08-2012 12-17-13 p.m..png (image/png, text), 59.25 KiB.

[15 Aug 2012 17:22] Amin Chavarria
I installed new MySQL Workbench 5.2.42  and I get a new error:

"Exception: Current profile has no WMI enabled"

Regards
Amin
[15 Aug 2012 17:23] Amin Chavarria
window error : "Exception: Current profile has no WMI enabled"

Attachment: new_error.png (image/png, text), 19.53 KiB.

[30 Aug 2012 20:25] MySQL Verification Team
Looks duplicate of bug: http://bugs.mysql.com/bug.php?id=59933 (same error message).
[1 Oct 2012 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".