MySQL Bugs: #55725: Cannot connect to server instance via server administration

Bug #55725	Cannot connect to server instance via server administration
Submitted:	3 Aug 2010 22:50	Modified:	13 Jun 2011 15:58
Reporter:	eric kinskofer	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.33b, 5.2.25 CE rev 6303	OS:	Windows (windows 7, XP SP3 32-bit)
Assigned to:		CPU Architecture:	Any
Tags:	Connection, Failure, python, ssh

Description:
When opening MySql workbench 5.2.25 on windows 7 get the following error:

"Cannot Start SSH Tunnel Manager"

I can open SQL Editor to perform query's, however, for the server administration I cannot open the server instance, manage import/export, or manage security.

When I click on the log entry, I get:

Traceback (most recent call last):

  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE/sshtunnel.py", line 6, in <module>

    import socket

  File "C:\Program Files\python27\LIB\socket.py", line 47, in <module>

    import _socket

ImportError: Module use of python27.dll conflicts with this version of Python.

How to repeat:
open mysql workbench.

Thank you for the bug report. http://bugs.mysql.com/bug.php?id=55674 related?

related in symptoms, however, I am not running two instances of mysql. I am running 5.1.49 community. I tried uninstalling and re-installing the workbench, however, this has not resolved. I get the same errors in the logs. thanks.

Based on this error message:

ImportError: Module use of python27.dll conflicts with this version of Python.

and your private comment, I think this has something to do with PATH environment variable setting. Please, send the results of:

echo %PATH%

from cmd.exe command line window.

C:\Users\ekinskof>echo %PATH%

C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\Wind
owsPowerShell\v1.0\;C:\Program Files\Vim\vim72;C:\Program Files\Microsoft SQL Se
rver\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Prog
ram Files\Microsoft Visual Studio 10.0\VC;C:\Program Files\python27;C:\Program F
iles\python27\Lib\site-packages\django\bin\;C:\Program Files\MySQL\MySQL Server
5.1\bin;C:\Program Files\python27\Scripts

Can you ssh to your server machine by using e.g. putty?

This is a development database and is installed locally. I can ssh using putty out to other machines.

I see this in the PATH:

C:\Program Files\python27

Can you, please, try to remove all references to python27 from PATH and check if this will solve the problem?

I had almost exactly the same problem.  Taking Python27 out of the PATH "solved" it...though now I can't have python in my path.

Does this error still happen with WB 5.2.27?

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".

Happens for me on Win7. Got the python in the path... is there any workaround? I want to have python in the path...

Setting environment variable PYTHONHOME to WB’s python directory solved the problem for me. Eventhough  I am not familiar with python it seems to me that default python installation lacks some sort of modules required by WB and thus fails. Guess if these modules were in default python install directory than may be it would work.

I had verified that after setting PYTHONHOME environment variable to c:\Python27 (where 2.7.1 is installed) on 32-bit XP, administration part of Workbench does not work. Setting this variable to python subdirectory of Workbench installation makes it work OK again. So, we definitely have a problem here to solve. Workbench should NOT depend on environment settings like this (and presence of any other Python versions besides the "included" one).

FYI

I'm running Workbench 5.2.33 on Windows 7 64-bit.

I did not have python in my path or a PYTHONHOME environment variable, but I had to add PYTHONHOME to my environment variables and point it at the workbench python folder to get this error message to go away.

Can you please try with next release of WB? The related issue have been addressed, so this one can be resolved as well.

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".