MySQL Bugs: #98886: parameter is not valid: MySQL Workbench Unexpected Error

Bug #98886	parameter is not valid: MySQL Workbench Unexpected Error
Submitted:	10 Mar 2020 2:45	Modified:	10 Apr 2020 6:22
Reporter:	Destiny Clarke	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	8.0.19	OS:	Windows (Microsoft Windows 10 Home)
Assigned to:		CPU Architecture:	Any
Tags:	is, model, not, Parameter, vaild, workbench

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!
The MySQL Workbench Team

How to repeat:
Open workbench
open models
Got the error

Hello Destiny Clarke,

Thank you for the report and feedback.
I'm not seeing any issues while opening the dummy/sakila model on Win10 with WB 8.0.19. Could you please attach the model file(.mwb) to this bug report which manifest this problem to reproduce at our end? Thank you.

regards,
Umesh

I am getting the exact same error "Parameter is not valid" starting today when trying to open a connection to a database. Yesterday I ran the MySql Installer and it updated MySQL Workbench to the latest version.

I initially get "AN error occurred while loading image search_sidebar.png" when starting workbench community edition.  Sometimes with an all gray screen and sometimes workbench will load.  But then when I select my connection (to a localhost) I receive the same error.  This had worked a few weeks back without issues.

Have the exact same bug with the same reproduction methods as Tara Welch. Please advise.

Initial search image error

Attachment: mysql-bug-20200403-01.png (image/png, text), 83.69 KiB.

Selecting DB parameter bug

Attachment: mysql-bug-20200403-02.png (image/png, text), 162.12 KiB.

uninstalling the workbench and reinstalling seems to fix it

additional note: Original installation to 8.0.19 was an upgrade from an older version (I think 8.0.18 but it could have been 16 or 17), perhaps it was an artifact left in the old version that the upgrade installation does not remove?

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