MySQL Bugs: #59748: Could not parse version number from C:\Program Files (x86)\MySQL\MySQL Server 5.

Bug #59748	Could not parse version number from C:\Program Files (x86)\MySQL\MySQL Server 5.
Submitted:	26 Jan 2011 16:43	Modified:	27 Aug 2012 14:58
Reporter:	Felipe Castro	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.31 CE	OS:	Windows (Windows 7)
Assigned to:		CPU Architecture:	Any
Tags:	mysqldump, Program Files, Windoes 7

Description:
Cannot export database to disk because it cannot access the mysqldump.exe program.  The use of spaces by Windows in the "Program Files (x86)" directory gives problems to WorkBench.

It probably will work if i re-install MySQl in a directory where spaces are not used in the name but it should work with the defaults.

I get this when opening the Admin screen:

WARNING

Error checking mysqldump version

Could not parse version number from C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin: 'C:\Program' is not recognized as an internal or external command, operable program or batch file.

How to repeat:
To replicate the problem:

- Install MySQL in the default location for 32 bit in Windows 7, which is "C:\Program Files (x86)\MySQL\MySQL Server 5.1".
- Start MySQL WorkBench.
- Open Server Administration for the default instance.
- Click on Data Dump section.

The Log will show the warning mentioned in the description.

Hello Felipe,

I cannot reproduce the problem on my machine. I too have both Workbench and the Server installed in the Default directories, but i don't see that problem on my machine.
What is the setting in your workbench preferences, on the Administrator-Tab in the "Path to mysqldump Tool:" Field?
Please also provide output of help->system info
thanks in advance

Some additional information.

In my WorkBench Preferences -> Administrator, I have this values:

Path to mysqldump Tool: C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin
Path to mysql Tool: C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin

From Help -> System Info:

MySQL Workbench CE for Windows version 5.2.31
Configuration Directory: C:\Users\felipe.castro\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\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: 3.1.0
OS: Microsoft Windows 7  (build 7600), 64-bit
CPU: 4x Intel(R) Xeon(R) CPU           X5482  @ 3.20GHz, 4.0 GiB RAM
Active video adapter: NVIDIA Quadro FX 1700
Installed video RAM: 512 MB
Current video mode: 1600 x 1200 x 4294967296 colors
Used bit depth: 32
Driver version: 8.15.11.9038
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Current user language: English (United States)

Thanks a lot for the help.

-Felipe

Please note that I can leave the "Path to mysqldump Tool" blank and use the bundled version of the tool and then it works fine.  For this reason I set this report as Non-critical.

However, I would expect it to work as well when the path is defined explicitly in the settings.

Thanks,
Felipe

Had you tried to quote path, like this:

"C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin"

I already tried enclosing the path inside quotes or apostrophes in the "Path to mysqldump Tool" setting but it did not work.

Are you tried to edit the path for mysqldump.exe?. Edit->Preferences->Administrator.

Please note that I already tried updating the actual path in the administrator settings as described before.

I can not repeat this on Windows XP SP3. Path to mysqldump from normal local server installation (5.1.54) is properly quoted as dump runs without any problem.

Please, check with full pathname of mysqldump in preferences, like this:

"C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin\mysqldump.exe"

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

I recently encountered this error. (Win7 64bit)
It turns out that the system's PATH variable was neither pointing to MySQL folder nor to the %system% folder. I added those to the PATH and the problem was fixed.

I'd say this was not a bug, but a misconfiguration issue at Workbench or OS level.