Bug #120537 MySQL Workbench Database Connection Not Loading – “Parameter is not valid” Error

• Submitted: 24 May 10:19
• Modified: 24 May 10:24
• Reporter: Nayana Hegde Hegde
• Status: Won't Fix
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 8.0.46
• OS: Windows (Windows 10 64-bit)
• CPU Architecture: Other (x86_64)
• Tags: connection-error, mysql-workbench, parameter-invalid, windows10

[24 May 10:19] Nayana Hegde Hegde

Description:
Operating System: Windows 10 64-bit

MySQL Server 8.0.46 installed successfully.
MySQL Shell connection works successfully using:
\connect root@localhost

However, MySQL Workbench throws an unexpected error popup:
“Parameter is not valid”

Workbench opens, but database connection and schemas do not load properly.

Tried the following:
- Restarted MySQL service
- Ran Workbench as Administrator
- Deleted Workbench AppData cache/configuration
- Reconnected using localhost:3306

Expected Result:
Workbench should connect to the local MySQL database and load schemas normally.

Actual Result:
Workbench throws “Parameter is not valid” unexpected error popup and database UI does not load correctly.

How to repeat:
1. Install MySQL Server 8.0 and MySQL Workbench on Windows 10.
2. Open MySQL Workbench.
3. Click on “Local instance MySQL80”.
4. Workbench opens but throws an unexpected error popup.
5. Error message displayed: “Parameter is not valid”.
6. Database schemas and connection UI do not load properly.
7. Issue occurs every time Workbench is opened.

Suggested fix:
Please investigate the Workbench UI configuration or connection initialization process causing the “Parameter is not valid” exception.

Possible fixes:
- Improve validation handling for corrupted configuration/cache files
- Automatically reset invalid Workbench UI settings
- Prevent unexpected popup during connection loading
- Provide detailed stack trace or error logging for debugging

[24 May 10:24] Nayana Hegde Hegde

Nothing is working in the workbench

[14 Sep 18:07] Omer Barnir

Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.