Bug #60379 | Cannot open SSH tunnel manager - Administration plugin is missing | ||
---|---|---|---|
Submitted: | 7 Mar 2011 23:49 | Modified: | 15 May 2011 17:42 |
Reporter: | Patrick Bertke | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.2.32 | OS: | Windows (XP Pro sp3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Admin plugin missing, ssh tunnel manager |
[7 Mar 2011 23:49]
Patrick Bertke
[7 Mar 2011 23:56]
Patrick Bertke
Screen capture of error
Attachment: error.rtf (text/richtext), 370.87 KiB.
[8 Mar 2011 2:50]
Antonio Gianni
I am having the same issue. Fresh install of mysql-workbench-gpl-5.2.32-win32, my Server version: 5.0.86-enterprise-nt MySQL Enterprise Server - Pro Edition (Commercial) I am running Windows Server 2008 R2 This Server was just staged…does not have python installed (have seen some other bugs where the path was a problem) Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\missas>echo %PATH% C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;D:\mysql\bin I am only trying to connect from the localhost as root using the connections that get preconfigured for you during the install. Also if I try to create a new connection I get the same error. Can’t use SQL Development or Server Administration I have done this same install about a dozen times on Win Server 2003 and also once with 2008 (R1) with no issues. Do I need to install python or does it come with workbench? I notice my other servers have it but this one does not have it yet. While we wait the bug reply I will install py and see if that fixes my issue.
[8 Mar 2011 3:03]
Antonio Gianni
After Installing python-2.6.5 (our corporate standard) the connection worked! I figured if the workbench needed py it would have bundled it on its own or checked like it does for .Net 4
[8 Mar 2011 3:44]
Patrick Bertke
YOU ARE A GOD SEND! Installing python-2.7.1 fixed the problem! Thank you, Thank you, Thank YOU!
[9 Mar 2011 8:39]
Hristijan Petreski
I had the same problem on win 7 (x64). After removing PYTHON variable from environment variables and re-installing WB it works!
[10 Mar 2011 0:02]
Will Warren
I am having the same problem getting SSH tunneling-related errors from MySQL Workbench 5.2.32, but Python 2.7.1 is not the issue. I have "fixed" the issue by falling back to 5.2.31 and everything works again. I am running on OS: Microsoft Windows 7 Service Pack 1 (build 7601), 32-bit against mysql Ver 14.14 Distrib 5.5.8, for Win32 (x86). I have python 2.7.1 installed already. Before trying to install the new MySQL workbench, I was running MySQL Workbench 5.2.31 with the following configuration and everything was fine. I installed 5.2.32 over top of 5.2.31 and I could not connect to my database anymore due to SSH tunneling errors. I rebooted but got the same problems. I then uninstalled 5.2.32 and reinstalled 5.2.31 and everything works fine. My workbench configuration: --------------------------- MySQL Workbench CE for Windows version 5.2.31 Configuration Directory: C:\Users\FTGUser\AppData\Roaming\MySQL\Workbench Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE Cairo Version: 1.8.8 Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering. OpenGL Driver Version: 2.1.0 - Build 8.15.10.2202 OS: Microsoft Windows 7 Service Pack 1 (build 7601), 32-bit CPU: Intel(R) Celeron(R) CPU 900 @ 2.20GHz, 2.0 GiB RAM Active video adapter: Mobile Intel(R) 4 Series Express Chipset Family Installed video RAM: 777 MB Current video mode: 1280 x 800 x 4294967296 colors Used bit depth: 32 Driver version: 8.15.10.2202 Installed display drivers: igdumdx32.dll,igd10umd32.dll Current user language: English (United States)
[10 Mar 2011 23:08]
Alfredo Kojima
Please open the View -> Output tab and copy/paste everything you see there. In addition, open a cmdline prompt window and paste the output of set (ie, the values of all environment variables). For the people who got this fixed once they installed Python, did you have an older version of Python installed before? What version?
[11 Mar 2011 0:04]
Antonio Gianni
In my scenario I had a freshy staged Server 2008 R2 and NO version of Python was installed. So it appears Python is a prereq...
[11 Mar 2011 13:20]
MySQL Verification Team
Then installing Python fixed the issue?. Thanks in advance.
[11 Mar 2011 16:35]
Antonio Gianni
Correct. I installed plain vanilla Python and it worked without doing anything else.
[14 Mar 2011 17:07]
v k
the same problem. and the issue the same too (install Python and reinstall Workbench)
[14 Mar 2011 17:11]
Antonio Gianni
I did not have to reinstall WB...just installed Python and nothing more.
[15 Mar 2011 9:34]
Valeriy Kravchuk
Antonio, What exact version of Python you had installed?
[15 Mar 2011 13:17]
Antonio Gianni
python-2.6.5 (our corporate standard) but I imagine other versions work as well. Read throught the comments as others have posted the versions that seem OK.
[15 Mar 2011 22:59]
Daniel Gollas
Hi, I had the same problem. Windows 7 64bit Python 2.6 and 2.7 installed side by side (64bit versions). Trying to work on SQL Development threw the error and Server Admin would not even start. SOLUTION: You need Python 2.6 32bit installed. It NEEDS to be the 32bit version of python. Python for AMD64 won't work. I'm not sure if you can use 2.7 32bit, but from my tests you can't. It will always try to load python libs from the 2.6 lib folder regardless of what your path environment value says. Maybe setting the PYTHONPATH would work for 2.7, but I didn't try.
[24 Mar 2011 15:56]
Alfredo Kojima
Please paste the output of running "set" from a command prompt, I need to see the values of PATH and other environment variables possibly set by Python.
[10 Apr 2011 4:09]
Chin Boon Oh
This may help. You may be having conflicts with your other Python dependent applications.
[10 Apr 2011 4:09]
Chin Boon Oh
This may help. You may be having conflicts with your other Python dependent applications. http://java.sg/mysql-workbench-cannot-connect-ssh-tunnel-manager-python-conflict/
[11 Apr 2011 8:31]
Valeriy Kravchuk
If you have Python installed you may want to check this build: ftp://ftp.mysql.com/pub/mysql/download/gui-tools/mysql-workbench-gpl-snapshot-5.2.34.7605-... It solves at least some of the bugs related to external Python installation. Please, check if it solves the problem for your.
[13 Apr 2011 9:19]
Nicholas Sherlock
I had this exact problem (Workbench picking up a random Python installation on my machine which didn't have the right libraries in it for SSH to work). The build posted above (workbench-gpl-snapshot-5.2.34.7605-win32) fixes the problem for me.
[15 May 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".