Bug #59836 Cannot create a new server instance in MySQL Workbench
Submitted: 31 Jan 2011 10:34 Modified: 15 Sep 2012 12:07
Reporter: Valter Silva Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S1 (Critical)
Version:5.2.31, 5.2.34, 5.2.37, 5.2.41 OS:Microsoft Windows (Windows 7 Ultimate 64 bits)
Assigned to:
Tags: Cannot create a new server instance in MySQL Workbench

[31 Jan 2011 10:34] Valter Silva
Description:
http://forums.mysql.com/read.php?152,404947,405552#msg-405552

How to repeat:
http://www.youtube.com/watch?v=rq7LeBpObJk
[1 Feb 2011 15:49] Valerii Kravchuk
Do you have a Windows service defined for MySQL server that listens to port 3306 on localhost?
[23 Feb 2011 22:34] David Aristizabal
I think I have the same issue:
Workbench 5.2.31 CE  Revision 7115
Running MySQL server on localhost as Windows service, on default port 3306.
Windows XP sp2
No problem creating a connection, and connecting to server (left side of Workbench).  But can't create a New instance for administration (right side).

Mine is in English, and this is the error I get (after waiting at the "Testing the Database Connection" screen for about a 30 seconds):

error
WMI query execution failed.
Server execution failed   
   [ OK ]
[27 Feb 2011 14:57] Valerii Kravchuk
I am still waiting for a conformation from the original bug reporter that he has Windows service defined for MySQL server. I also need to know if service name starts with "mysql" (case does not matter).
[28 Feb 2011 16:40] David Aristizabal
Hi there,

In my case, the service name is "MySQL"

The work-around I'm using is that I enabled remote root access (not an issue in my network, but probably not suitable for most users), then I created a new admin instance, this time using the hostname of my system (instead of "localhost").  In that case, the wizard asks for the "type of remote management you want to use" and I chose "Do not use remote management"

With that setup, the admin instance works, but I can't start/stop the server, or change the my.ini options.  All other features seem to work OK.

PS: I also tried the "type of remote management you want to use" as "Native Windows remote management"  In this case it prompted me for a username and password (for service: wmi@hostname).  After I enter the username and password I get:

Error
Could not connect to target machine
User credentials cannot be used for local connections
                              [ OK ]
[28 Feb 2011 18:48] David Aristizabal
Here's another piece of information:

Today I installed MySQL workbench on another system in my network (Win XP sp2).  When I try to create an admin instance to connect to the system that's running the MySQL server, I get to the point where it asks for the user and password for service: wmi@hostname

After I provide my credentials I get:

Error
Could not connect to target machine
The RPC server is unavailable
              [ OK ]

Now I'm thinking perhaps my network administrator has disabled / blocked some service that's required for wmi to work?  

I'd like to be able to create an admin instance to the localhost that works without any wmi stuff -- like it did with Worbkench 5.2.28.  Is there a way to do that that I'm not seeing?

Thanks!
David A.
[22 Mar 2011 10:13] P B-S
I have the same issue trying to manage a MySQL instance on a remote windows machine (XP Pro). It tells me that "The RPC Server is unavailable".

It would be really great if this worked :)
[9 Apr 2011 16:04] Matej Tomcik
Make sure that the Windows Management Instrumentation (WMI) service is not disabled and also you have MySQL running as a service.
[14 May 2011 8:16] Valerii Kravchuk
All reporters,

Please, make sure that the Windows Management Instrumentation (WMI) service is not disabled and you have MySQL running as a service. If this is the case, check if the problem is still repeatable with a recent version of Workbench, 5.2.33b.
[14 Jun 2011 23: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".
[15 Jun 2011 10:13] Valter Silva
i install the new version and the problem seems fix it.
thanks.
[15 Jun 2011 18:26] David Aristizabal
Hi there,

Today I installed MySql workbench 5.2.34 CE, but I still have the same issue.

Creating a new admin instance to the localhost fails with the error message:

Could not set up connection: WMI query execution failed.  Server execution failed.

I now think there is a problem with my WMI service.  In "services" it says it is running, but a while ago I had another problem with another application (unrelated to MySql) also complaining about WMI query execution.

So, is there a way to create a server admin instance to the localhost that does not use WMI?  Should I submit this as a separate bug / feature request?

Thanks!
David A.
[15 Jun 2011 19:30] Armando Lopez Valencia
Hello.
Why don't you try our Installer tool (http://dev.mysql.com/downloads/mirror.php?id=402893#mirrors).
This tool will help you to install/configure on an easy way a MySQL server, workbench and other tools.
Please give a try and let us know the output.
[15 Jul 2011 23: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".
[30 Aug 2011 11:54] pafel genov
Same issue but i don't want to connect to localhost server. I want to connect to example.com on default port 3306. Workbench connect to the server and know that remote server is windows and the version of mysql server is 5.5.13. When go to the next step i choose "Native Windows Remote management" and when go to the next step workbench ask me for username and password of my Windows Server Machine. I give him right user/pass (first time COMPUTERNAME\USERNAME, second time only USERNAME) and every time the result is - Can't connect bla bla.
[24 Sep 2011 8:31] Valerii Kravchuk
Please, check if the same problem still happens with a newer version, 5.2.35.
[24 Oct 2011 23: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".
[15 Feb 2012 7:58] Ray Montgomery
This bug is still there.  I cannot create a new server instance to localhost. The error message is:
Could not set up connection: Could not connect to target machine 

This is a brand new installation on Windows 7.  Workbench version: 5.2.37 CE, Revision 8576

MySQL was installed from:  mysql-5.5.20-win32.msi

In services MySql and WMI are both running.  I am logged on as Administrator.  Any ideas about what to do?

Thanks.
[9 Mar 2012 4:27] Alfredo Kojima
What is the full error message?
[13 Apr 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".
[13 Jul 2012 15:34] Amin Chavarria
Hi all, 
Yo tengo el mismo problema:
Windows Vista Home Premium SP2
Mysql: 5.1.43-community

Al tratar de crear una nueva Instancia, me marca el siguiente error en el apartado de "Windows Management": Could not connect to target machine

El servicio de windows "MySQL" esta corriendo, si puedo accesar a las bases de datos desde mis aplicaciones y SQL Development.

Inicia sesion en windows con el usuario administrador.

Voy a crear otros servicios con otro usuario de windows y notifico como me va.
[1 Aug 2012 14:32] Valerii Kravchuk
All reporters,

Please, check if this problem still happens with a newer version, 5.2.41.
[6 Aug 2012 17:12] Amin Chavarria
Hi Valeriy,
I installed new version 5.2.41 and the problem persists.

regadrs
amin
[15 Aug 2012 12:07] Miguel Solorzano
Please try version 5.2.42. Thanks.
[16 Sep 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".