Bug #116436 MySQL has Encountered a problem
Submitted: 21 Oct 2024 14:38 Modified: 21 Nov 2024 15:14
Reporter: Meghana G Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0 OS:Windows (11)
Assigned to: CPU Architecture:Any

[21 Oct 2024 14:38] Meghana G 
Description:
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!

Above pasted message pop up while trying to open the mysql connections

How to repeat:
Parameter is not valid.
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!

Above pasted message pop up while trying to open the mysql connections
[21 Oct 2024 15:14] MySQL Verification Team 
Hi Mr. G,

Thank you very much for your bug report.

However, let us inform you that this is a forum for the reports with fully repeatable test cases. Each of these test cases should consist of detailed description of anything that you tried to do, point by point. If any of the schemas, tables, stored routines etc ... have been used when MySQL encountered a problem, you should send those too.

We shall wait until you provide us with a full test case, as described above.
[22 Nov 2024 1:00] Bugs System 
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".