MySQL Bugs: #101492: unexpected exception has been raised by one of the MYSQL workbench modules.

Bug #101492	unexpected exception has been raised by one of the MYSQL workbench modules.
Submitted:	6 Nov 2020 9:22	Modified:	6 Dec 2020 13:40
Reporter:	maheen s	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0	OS:	Windows
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	mysql verification team

Description:
I was trying to open MYSQL connection ,but I couldn't open it, it is throwing an error.

I am getting getting following error message

we are sorry for 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 the [Report Bug]button below.

please make sure to include 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 close the MYSQL workbench and then restart the system, then trying to open the MYSQL workbench again.
even uninstalling many times and reinstalling and that did not fix the issues.
updating repairing also I tried nothing is working for me.

before also I reported a bug but after that also not able to connect to my data base every time bug message is coming tries all possible ways to connect but no results.

Suggested fix:
Please say some suggested fix solutions

Hello maheen,

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)? Thank you.

Regards
Ashwini Patil

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