Bug #80484 Cannot run anything on MySQL Workbench, keep getting parameter is not valid.
Submitted: 23 Feb 2016 19:11 Modified: 15 Apr 2016 7:44
Reporter: Weston Christensen Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.3.6 CE build 511 64-bit OS:Windows
Assigned to: CPU Architecture:Any

[23 Feb 2016 19:11] Weston Christensen
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:
I don't know?

Suggested fix:
Have no clue
[23 Feb 2016 20:16] MySQL Verification Team
Thank you for the bug report. Which version are you using 6.3.6? Otherwise please try it. Thanks.
[23 Feb 2016 23:58] Weston Christensen
This is the version that I am running. 6.3.6 CE build 511 64-bit
[3 Mar 2016 22:15] Sharon Jones
I'm having the same issue. Can't run anything after getting the same "parameter is not valid" error message.
[4 Mar 2016 5:20] Weston Christensen
Sharon, I just uninstalled the program and then reinstalled it and that seemed to help. I am not sure any other way to fix that issue so that is just what I did.
[6 Mar 2016 21:45] Sharon Jones
Thanks Weston... I went back to my previous version - build 4. That seems to be working fine for me so far :)
[8 Mar 2016 14:45] MySQL Verification Team
Then re-installing solved the issue?. Thanks.
[8 Mar 2016 21:46] Sharon Jones
Reinstalling an old version did for me thanks Miguel
[15 Apr 2016 7:44] MySQL Verification Team
Not enough information was provided for us to be able to handle this bug. I tried to trigger this issue on many boxes without any luck.

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.