MySQL Bugs: #83492: Parameter is not valid

Bug #83492	Parameter is not valid
Submitted:	24 Oct 2016 3:25	Modified:	6 Jan 2017 1:56
Reporter:	Sally Budack	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.3.8	OS:	Windows (Win10)
Assigned to:		CPU Architecture:	Any

Description:
When opening the program, The message appears to report the bug. I used the program successfully earlier today after updating to the newest version. I closed the program, rebooted my system and the notice appeared. I created a test database with a new connection. The connection was successful.
Now, when I open the program, I get the "report a big message", and when I try to open the new database.

How to repeat:
Open the program. Open the schema sb15 

Suggested fix:
The only message is "parameter not met". Which parameter is not specified. Before I rebooted, I did not have this problem.

Are you using 6.3.8 version?.

I had just downloaded it & installed it. I have since uninstalled it and re-installed 5.2CE (version available if you only install the workbench) and the bug is not there.
I had installed 5.7 during the summer, the newest at the time. I needed to connect to a new connection. I got the message that I needed to update. The update caused the problem. I had several mySQL products installed. I removed them all and started over with just the workbench.
I am getting no bug messages. If I need more that just the workbench, I will see what happens. I wish the specific parameter that was not being met was identified in the "parameter not met" message.

Thank you for the feedback. If I understood you you aren't getting that error message currently if you will get again please describe step by step how that can be repeatable and attach a screen-shot of the error dialog using the Files tab here. Thanks in advance.

screen shot of error message

Attachment: sql message.JPG (image/jpeg, text), 35.35 KiB.

FYI: since I removed the program & reinstalled it, I am not getting the error. I am using an older version (5.2). I needed to be able to work.

Hello Sally Budack,

Thank you for your feedback.
This is most likely duplicate of Bug #83369, please see Bug #83369.

Thanks,
Chiranjeevi.

I have not gone back to the newer version. I am still using the older version and not having any issues.