MySQL Bugs: #112821: Can not access database through workbench after laptop clone

Bug #112821	Can not access database through workbench after laptop clone
Submitted:	24 Oct 2023 23:31	Modified:	26 Oct 2023 13:19
Reporter:	J. Glasgow	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	8.0.34	OS:	Windows (11)
Assigned to:		CPU Architecture:	Any

Description:
I had my laptop cloned. Everything works fine otherwise. I run MySQL Workbench and all the data for my connections look correct. But when I click on any of them, I get this error message:

MySQL Workbench has encountered a problem External Component has thrown an exception We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below.  Please make sure to include a detailed description of your actions that lead to this problem. Thanks a lot for taking the time to help us improve MySQL Workbench! The MySQL Workbench Team

How to repeat:
I have attempted to re-install Workbench, and I have reinstalled Visual C++ and .net framework. I have also repaired all of those things. I thought the issue might be server-side security, so I verified that and when I came back to the laptop, after a couple of attempts, surprisingly I got through one time. Then I worked on the database, and later I came back to Workbench and can't get in again. So there is some fluke accident that let me get past this error once. Any suggestions on how to fix this?

Hello!

Thank you for the bug report.
To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (--log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html)?

Regards,
Ashwini Patil

Hello!

Thank you for the details.
Imho this is duplicate of Bug #110786, please see Bug #110786.

Regards,
Ashwini Patil

So... i checked out 110786, and it's still open and has been open for a long time. By saying my issue is the same, does that mean you stop working on it as well? I can tell you that there are a number of issues with my workbench and I feel they all have a common source -- you guys have an issue with pathing, or framework defaults (like VC++, .net framework, or python), and you need a repair tool that can automate library checks, env settings that your product is currently using, and other settings like other mature products, and that will tell the users the steps to take to fix their problems. I have installed dbForge and it works like a champ (it's not my laptop or environment)! So, I am switching over to dbForge after using workbench for years. When you have a solution to this problem, I hope you will update my bug/notify me, and not just 110786. If you are waiting on me to check every day on the status of 110786, I wouldn't hold my breath. I'm not being mean, I am just telling you the point of view of your declining user numbers.