Bug #87785 Workbench unable to get mysqldump version
Submitted: 17 Sep 2017 8:40 Modified: 19 Sep 2017 13:37
Reporter: Ganapati hegde Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.9 OS:Windows (Microsoft Windows 8.1 Pro)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[17 Sep 2017 8:40] Ganapati hegde
Description:
When i try to export the data workbench is throwing me an error saying that "Workbench unable to get mysqldump version.Please verify the log file for more information". I did reinstallation and also i have changed the "Path to mysqldump Tool" to C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe. Even after that i am getting the same error.

How to repeat:
When i try to export the data workbench is throwing me an error saying that "Workbench unable to get mysqldump version.Please verify the log file for more information". I did reinstallation and also i have changed the "Path to mysqldump Tool" to C:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe. Even after that i am getting the same error.
[18 Sep 2017 6:51] Chiranjeevi Battula
Hello Ganapati,

Thank you for the bug report.
I could not repeat the issue at our end using with MySQL workbench 6.3.9 versions to get mysqldump.
Could you please provide repeatable test case (exact steps, screenshot etc. - please make it as private if you prefer) to confirm this issue at our end?
Please check File->Edit->Preferences, Administrator tab. You need to provide correct path to mysqldump there.

Thanks,
Chiranjeevi.
[18 Sep 2017 6:52] Chiranjeevi Battula
Screenshot

Attachment: 87785.JPG (image/jpeg, text), 135.93 KiB.

[19 Sep 2017 11:55] Ganapati hegde
This the screenshot which shows the error

Attachment: mysqldumpnotfound.png (image/png, text), 75.22 KiB.

[19 Sep 2017 11:58] Ganapati hegde
The dump tool path i have changed to same path which i got in the reply. But even after doing that i am getting the same error.

Attachment: mysqldump.png (image/png, text), 58.80 KiB.

[19 Sep 2017 13:37] Chiranjeevi Battula
Hello Ganapati,

Thank you for the feedback.
I could not repeat the issue at our end using with MySQL workbench 6.3.9 version.
If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Thanks,
Chiranjeevi.
[22 Dec 2017 8:35] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88993 marked as duplicate of this one.
[22 Dec 2017 13:32] Kyler Moore
Hello, the problem is with version 6.3.10. Thank you.
[22 Dec 2017 13:43] Kyler Moore
This is in my log after trying to export.

08:37:53 [ERR][wb_admin_export.py:get_mysqldump_version:117]: Could not parse version number from mysqldump.exe:
C:\Program Files\MySQL\MySQL Workbench 6.3 CE>cd /d C:\Users\KMoore 
mysqldump  Ver 10.13 Distrib 5.7.17, for Win64 (x86_64)

Hope this helps, thanks.
[1 Mar 2018 17:31] Henry Kafeman
This is happening in v6.3.9 and v6.3.10 for me with v8.0.1 MySQL!

If I set the "path to mysqldump tool" OR copy the v8.0.1 mysqldump.exe to the "C:\Program Files\MySQL\MySQL Workbench 6.3 CE" folder I just get the "Colud not get mysqldump version" dialogue.

Please fix this bug.

Thanks
Henry
[1 May 2018 10:33] David Garratt
Error message

Attachment: 2018-05-01_11-28-20.jpg (image/jpeg, text), 32.42 KiB.

[1 May 2018 10:33] David Garratt
Error message

Attachment: 2018-05-01_11-29-00.jpg (image/jpeg, text), 20.08 KiB.

[1 May 2018 10:35] David Garratt
Exact same problem backing up mysql server 8.0.11 which is running on MacOS. Tried mysqlworkbench running under MacOS and also windows versions. Screen dumps uploaded.
[18 May 2018 7:26] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=90924 marked as duplicate of this one.
[18 May 2018 16:14] Henry Kafeman
When will this be fixed.
Surely it is Important to be able to Export Databases for Backup, etc.
I cannot believe this has not been fixed given that it was reported by myself and other long before...
Setting the Administration Paths as per Bug #90924,does NOT fix the problem.

Thanks
[1 Jun 2018 5:48] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=91079 marked as duplicate of this one.