Bug #98280 | Runtime Exception: Unable to execute command chcp | ||
---|---|---|---|
Submitted: | 18 Jan 2020 3:27 | Modified: | 8 Apr 2021 1:17 |
Reporter: | Larysa Baishenko | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench | Severity: | S7 (Test Cases) |
Version: | 8.0.19, 8.0.34 | OS: | Windows (Microsoft Windows 10 Pro) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[18 Jan 2020 3:27]
Larysa Baishenko
[15 Sep 2020 22:12]
MySQL Verification Team
Thank you for the bug report. Please upgrade to version 8.0.21.
[8 Apr 2021 1:17]
MySQL Verification Team
Hi Miguel, My environment hit this problem. wb.log is here. 10:11:59 [ERR][SQL Editor Form]: Unable to create db_mgmt_SSHConnectionRef object 10:11:59 [ERR][wb_server_management.py:local_run_cmd_windows:400]: Exception executing local command: chcp.com: 'utf-8' codec can't decode byte 0x8c in position 0: invalid start byte Traceback (most recent call last): File "C:\Program Files\MySQL\MySQL Workbench 8.0\modules\wb_server_management.py", line 397, in local_run_cmd_windows retcode = OSUtils.exec_command(command, output_handler) File "C:\Program Files\MySQL\MySQL Workbench 8.0\workbench\os_utils.py", line 353, in exec_command for line in iter(process.stdout.readline, ""): File "C:\Program Files\MySQL\MySQL Workbench 8.0\Python\Lib\codecs.py", line 322, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8c in position 0: invalid start byte After these procedure. (1) Uninstall All mysql related items. (MySQL 8.0.22) (2) Install MySQL 8.0.23 with Developer profile. If you want to need more information, please let me know.
[16 Apr 2021 8:13]
MySQL Verification Team
The root cause looks same for me. https://bugs.mysql.com/bug.php?id=102300
[18 Oct 2021 12:45]
MySQL Verification Team
Bug #105237 marked as duplicate of this one.
[18 Oct 2021 13:02]
MySQL Verification Team
Bug #105233 marked as duplicate of this one.
[4 Oct 2023 11:08]
MySQL Verification Team
Bug #112611 marked as duplicate of this one.