MySQL Bugs: #64305: Data Export: 'ascii' codec can't decode byte 0xea in position 57

Bug #64305	Data Export: 'ascii' codec can't decode byte 0xea in position 57
Submitted:	12 Feb 2012 21:59	Modified:	4 May 2012 1:11
Reporter:	Michał B.	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.37	OS:	Windows (7 SP1 32-bit)
Assigned to:		CPU Architecture:	Any
Tags:	data export ascii exception unhandled

Description:
Exception catched on MySQL Workbench 5.2.37. When I used "Server Administration" and tried to enter "Data Export" following exception was throwed:

Traceback (most recent call last):

  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_export.py", line 1486, in start

    if not self.check_mysqldump_version(True):

  File "C:\Program Files\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_export.py", line 1375, in check_mysqldump_version

    msg = "Could not parse version number from %s:\n%s"%(path, output)

UnicodeDecodeError: 'ascii' codec can't decode byte 0xea in position 57: ordinal not in range(128)

This same exception is showing every time when I click "Start Export" in "Data Export" tab.

Tested on few databases (local and remote) and exists in every possible cases. Schemas and tables don't have any specials signs except latin and _ (undermark).

How to repeat:
1. Connect to Server Administration (fe. local XAMPP server)
2. Go to "Data Export" (first exception, blank page will be loaded).
3. Click on any other tab (for example "Data Import/Restore)
4. Try to enter to "Data Export" again. This time it should load correctly.
5. Choose some schema, options and click "Start Export".
6. See "beautiful" error "Unhandled exception: 'ascii' codec can't decode byte 0xea in position 57: ordinal not in range(128)".
7. Button "Start Export" will be disabled.
8. See Output (View -> Output).

Suggested fix:
Unknown.

Please provide the output of Help->System Info. I couldn't repeat on Win7 Ultimate 64-bits.

Configuration:

MySQL Workbench CE for Windows version 5.2.37  revision 8576
Configuration Directory: C:\Users\m1chu\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering.
OS: Microsoft Windows 7  Service Pack 1 (build 7601), 32-bit
CPU: 2x Intel(R) Core(TM)2 CPU         T5500  @ 1.66GHz, 2.5 GiB RAM
Active video adapter (0): Mobile Intel(R) 945 Express Chipset Family
Installed video RAM: 0 MB
Current video mode: 1280 x 800 x 4294967296 colors
Used bit depth: 32
Driver version: 8.15.10.1930
Installed display drivers: igdumd32.dll
Current user language: Polski (Polska)

Did you change any WB settings? What does mysqldump --version report (it's in the WB install folder)?

No, i did not change anything in WB settings. And the result of mysqldump --version is: mysqldump  Ver 10.13 Distrib 5.5.16, for Win32 (x86)

Does your database schema, tables or any object names have non-ascii characters?
What about file paths?

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

Bug dissapeared with next release. Thanks.

Thanks for the report Michał, please feel free to reopen this bug in case you fund it again.