MySQL Bugs: #55674: PYTHONPATH from other Python installations interferes with workbench

Bug #55674	PYTHONPATH from other Python installations interferes with workbench
Submitted:	2 Aug 2010 5:30	Modified:	24 Nov 2010 16:10
Reporter:	Murray Thompson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S1 (Critical)
Version:	5.2.25 CE rev6303, 5.2.26	OS:	Windows (Vista 64 Ultimate)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	server administration, workbench

Description:
I am using Vista64 Ultimate and still having a problem with opening Server Administration tools.

New Server Instance and Manage Server Instances work OK. 

Manage Import/Export and Manage Security tools do not.

I am trying to manage local instances, and connecting to them via TCP/IP. The SQL Development and Data Modeling  features work fine. (A "cannot open SSH Tunnel Manager" error appears when opening Workbench, but I'm not using an SSH configuration.)

Double-clicking on a server instance opens a very briefly shown "Please stand by..." dialogue box, but nothing happens afterwords. Clicking on the non-working tools below does nothing at all.

How to repeat:
Have existing local MySQL instance, connecting via Standard TCP/IP.
Try to use Manage Import/Export or Manage Security tools- try do not open.

What exact version of MySQL server, x.y.z, are you working with?

I have two local instances running:
5.1.3
5.5.3

But neither of them can be managed with the Import/Export or Security features in Workbench. 

(FYI, I marked it as an S1 severity in that I can't replace my use of MySQL Administrator with using Workbench until those features do work.. and if others are running into the same thing, they likely can't either.)

Sorry. The versions I currently have are:
5.1.30
5.5.3

I will install 5.1.49 and see if there is still a problem, too.

I upgraded my community server version to 5.1.49.  The same issues still occur.

I couldn't repeat on Vista 64-bit.

In checking further, installing Workbench 5.2.25 on Win XP Pro SP3 and on OSX 10.6 running pre-existing instance of MySQL 5.1.30 has no problems for me. All tools work OK.

The problems persist in Vista-64 Ultimate, and I guess the New Server Instance tool doesn't work either: it opens, but doesn't do the whole job. 

Some details of using the New Server Instance tool in case it helps pinpoint what's going on: 
Things go OK up to the 'Testing Host Machine Settings' step, but at that step, the Message Log says "Operation failed:" with no further explanation. In the 'Information About MySQL Configuration' step, even though I located the "Path to Configuration File" directly (and it's in the default directory anyway), the tool still indicates that "The config file could not be found."

The ssh warning should not occur.

How did you create the instance?

When you create a new instance then the first question you get is the question if local or remote ... did you click remote here by accident?

When using the New Server Instance tool, I did choose the 'local' option and ran into the problems I described.

However, I created the instances I do have with the Manage Server Instances tool. Connections test OK, and the proper version is found when performing a "connect and check" operation. Instances *appear* to be good to go, but they—or the tools related to them—just aren't working.

To clarify, the "Cannot start SSH Tunnel Manager" warning appears when opening Workbench, not when trying to open or work with an instance. If if I clear my instances under Server Administration, the warning still appears.

Please, send the results of:

echo %PATH%

from cmd.exe command line window.

Here you go, Valeriy:

C:\WebDev\ruby\bin;
C:\Program Files (x86)\CollabNet Subversion Server;
C:\WebDev\Perl\bin;
C:\Windows\system32;
C:\Windows;
C:\Windows\System32\Wbem;
C:\Program Files\TortoiseSVN\bin;
C:\Program Files\MySQL\MySQL Server 5.1\bin;
c:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;
c:\WebDev\PHP5;
C:\Program Files (x86)\QuickTime\QTSystem\;
C:\Program Files\MySQL\MySQL Server 5.5\bin

..maybe it's the two installations that are causing the problem?

After setting an environment variable named PYTHONPATH, I had the same error message (it referred to Python 2.6). Remove the variable and all is well. Same error may be caused by python 2.x in the path proper.

Thank you for the feedback.

Please try current version 5.2.26 and if problem still exists send us all settings you have for problem instance.

Updated to 5.2.26.. same problem still occurring for me in Vista 64 Ultimate. 

With no one able to corroborate (including myself on other OS's), I'm not sure if it is just a single system issue or what.

Please, check if this still happens with a newer version, 5.2.28.

I am experiencing the exact same issues here:
- "cannot open SSH Tunnel Manager" error when starting Workbench
- Double-clicking on server instance opens "Please stand by...", but nothing happens 

The SQL development part is working. I am using Workbench 5.2.28 CE Revision 6722. 

If a create a new localhost instance, first everything works fine:

> Connecting to MySQL server localhost...
> Connected.
> MySQL server version is 5.1.40-community
> MySQL server architecture is ia32
> MySQL server OS is Win32

But in the next step, the check of the configuration file fails:
> Check MySQL configuration file:
> Operation failed: 

The instance is running and it is located at C:\Program Files\MySQL\MySQL Server 5.1. The my.ini is located there.

I have also started the Workbench as Administrator, but the error still persists.

Forgot to mention the OS: I am using Windows Home Premium 32 Bit SP 2 here.

Sorry, me again :-) Just checked that the same workaround is possible here: an environment variable PYTHONPATH was set. If I remove the variable, everything works fine and the "ssh tunnel" error disappears.

We still need to know if this can NOT be fixed with removing Python 2.6 from the path in 5.2.28.

This can be fixed with removing the environment variable PYTHONPATH from the path in 5.2.28.

The problem also disappears for me when removing the PYTHONPATH system environment variable.

Not sure if should be closed or not. (We know what's causing it.. but why?)

I'll leave that up to others to decide.

Setting to Verified and changing synopsys from "Server Administration tool not working in Workbench for Standard Connections "

Fixed in repository.

I had the same issue on a Windows Server 2008 R2 X64 system. Fixed it by installing Visual Studio 2008 Redistributable and the ... SP1 Redistributable.

fix confirmed in repository

An entry has been added to the 5.2.31 changelog:

The environment variable PYTHONPATH from other Python installations interfered with MySQL Workbench. When starting MySQL Workbench the error “cannot open SSH Tunnel Manager” appeared. Further, it was not possible to use the administrative functions of MySQL Workbench.

I tried adding environment variable PYTHONHOME=path to the Workbench python folder, that didn't work.

When I looked into the Event Viewer I was seeing an error message indicating that Dependent Assembly Microsoft.VC90.CRT could not be found. After doing some more researching, I saw that I did not have the Microsoft C++ 2008 Runtime libraries installed on my server. Once I installed the "Microsoft Visual C++ 2008 Redistributable - x86" I was able to connect successfully with MySQL Workbench. 

Note, even though I'm running a 64bit OS, and 64bit MySQL Server instance, I can only find a 32bit version of the Workbench, so I had to install the 32bit (x86) version of the Microsoft Visual C++ 2008 Redistributable. I still had the error when I only installed the 64bit of the Microsoft Visual C++ 2008 Redistributable.

Long story short, try installing the x86 version of the Microsoft Visual C++ 2008 Redistributable. I used the latest service SP1 version, 9.0.30729

For Windows Server 64 bit 2008 installing the 
Microsoft Visual C++ 2008 Redistributable Package (x86)

did the trick for me as well. Thanks.