Reputation: 423
MySQL workbench was working properly till last login(yesterday). When I tried to open an existing connection(today), this error was popped up. I was trying to convert tables from MSSQL to MySQL yesterday.
Detailed error message
MySQL workbench has encountered a problem 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!
The MySQL Workbench Team
Upvotes: 3
Views: 28213
Reputation: 383
I had a similar experience with this on Windows 11. I was not able to get any database connection to work. Instead on the first attempt, there was a popup message that said:
Further attempts did nothing, unless I tried opening the connection via the drop down menu, which then resulted in the error popup.
Help > Show Log File
revealed this error stack trace
09:17:39 [INF][SQL Editor Form]: Opened connection 'My Dev Connection' to Source distribution version 8.0.32
09:17:39 [WRN][ mforms]: Resource file not found: wb-toolbar_nav-back.png
09:17:39 [WRN][ mforms]: Resource file not found: wb-toolbar_nav-forward.png
09:17:39 [WRN][ mforms]: Resource file not found: wb-toolbar_automatic-help-off.png
09:17:39 [WRN][ mforms]: Resource file not found: wb-toolbar_automatic-help-on.png
09:17:39 [WRN][ mforms]: Resource file not found: wb-toolbar_manual-help.png
09:17:39 [WRN][ mforms]: Resource file not found: snippet_use.png
09:17:39 [WRN][ mforms]: Resource file not found: snippet_insert.png
09:17:39 [WRN][ mforms]: Resource file not found: snippet_clipboard.png
09:17:39 [ERR][ Workbench]: Parameter is not valid.
Exception = System.ArgumentException
Message = Parameter is not valid.
FullText = System.ArgumentException: Parameter is not valid.
at System.Drawing.Bitmap..ctor(String filename, Boolean useIcm)
at TriangleNodeControl..ctor()
at MformsTree.AddColumn(TreeColumnType type, String name, Int32 initial_width, Boolean editable)
at mforms.MenuItem.callback(MenuItem* )
at MenuItemEventTarget.MenuItemClick(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
This post contained the above error:
https://bugs.mysql.com/bug.php?id=105392
That post itself pointed to another post:
https://bugs.mysql.com/bug.php?id=99285
Which says this: "To fix the issue, I simply used MySQL Installer to uninstall and reinstall MySQL Workbench, and it resolved the issue."
So I downloaded the latest MySQL installer from here:
https://dev.mysql.com/downloads/file/?id=525959
Finally, I located the Workbench app here:
Settings > Apps > Installed Apps
I selected "Modify", "Repair", and browsed to the installer I had already downloaded. Then I completed the wizard, and this resolve the issue.
Upvotes: 0
Reputation: 1
I faced the same issue today, what I simply did is
Upvotes: 0
Reputation: 11
Okay listen up. Go to your downloads where you had actually downloaded workbench setup right click on it, you will find an option called "Repair", click on it, follow all steps, open your workbench, open your connection now!(Mine is Windows 10)
Note : You can do it by re-installing workbench too! But Repairing the tool is more convenientPFA Image
Upvotes: 0
Reputation: 4279
For future reference, I had the same problem out of the blue with Workbench on Windows 7 so I re-ran MySQL Workbench installer, selected Repair and everything went back to normal.
I guess some update messed up the install.
Upvotes: 19
Reputation: 53317
This is not about the normal login but migration in MySQL Workbench. This part uses separate logins to source and target servers. If your connection to the MS SQL server worked yesterday and you didn't change anything in MySQL Workbench then it is very likely something with your MS SQL server happened. So, someone needs to check if that server is still running properly and can be accessed from your machine.
Upvotes: 1