MySQL Bugs: #51950: No connection to MySQL server: Cannot open selected view (dbquery)

Bug #51950	No connection to MySQL server: Cannot open selected view (dbquery)
Submitted:	11 Mar 2010 12:49	Modified:	23 Jul 2010 11:53
Reporter:	Hermann Boeken	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.16, 5.2.21, 5.2.22	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
A connection to a MySQL server with the workbench doesn't work. It gives the following error message:
MySQL Workbench Error:
  Cannot open selected view (dbquery)
  Input string was not in a correct format.

A connection to the same MySQL server with the same connection setting works without any problems in the "old" MySQL Administrator tool.
I uninstalled all MySQL tools and the workbench, rebooted, reinstalled the workbench, but still the same problem. 

How to repeat:
1. I installed MySQL Workbench 5.2.16 OSS Beta Revision 5249.
2. I created a new connection for a remote MySQL 5.2 server running on a Solaris 10 server (standard IP:3306 connection method).
3. Testing the connection gives the result "Connection parameters are correct".
Double-clicking the connection gives the MySQL Workbench Error:
  Cannot open selected view (dbquery)
  Input string was not in a correct format.

When selecting the same server connection in the "Server Administration" section the following bug info is available :

Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException: External component has thrown an exception.
   at MySQL.Forms.DrawBoxImpl.drawbox_mouse_click(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseClick(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Correction: the mysql server I'm connecting to is version 5.0.90

MySQL server 5.0 is very old and unsupported.

For more informations about that read:

http://www.mysql.com/about/legal/lifecycle/

Please try actual server here. MySQL 5.1.45.

Even if MySQL server 5.0 is unsupported, I expect the Workbench to behave more robust, e.g. by giving an appropriate error message "MySQL server version (5.0) not supported".

I'll upgrade to a more recent server version though and try again.
Thanks for your support.

Please try Workbench version 5.2.17. Thanks in advance.

Miguel, I don't understand, what you want me to test:

Workbench 5.2.17 with MySQL Server 5.0 to verify my original request?
Or Workbench 5.2.17 with MySQL Server 5.1?

Please, check latest Workbench version, 5.2.18 today, with both 5.1.x and 5.0.x server versions, whatever they are, and inform about the results.

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

I tested to connect to MySQL Server 5.0.90 with WB 5.2.21rc:
This opens a Bug Report window with the text:
MySQL Workbench has encountered a problem
Nullable object must have a value
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.

There's still no indication that the reason for this exception might be an old MySQL server version.

I don't have a MySQL server 5.1 available for testing (yet).

Thank you for the feedback.

I can not repeat described behavior. Please provide screenshots with connection settings in WB and output of SHOW GRANTS for user you are trying to connect as in Solaris. Please try latest version of WB 5.2.22 to see if this problem occasionally fixed.

Output of SHOW GRANTS (modified actual user/password/host/schema):

mysql> show grants for user@dbhost;
+-------------------------------------------------------------------------------------------------------------+
| Grants for user@dbhost                                                                                      |
+-------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'user'@'dbhost' IDENTIFIED BY PASSWORD '907DFF608883BA5A81F9B471499C37C7FDE7BFDB5'    |
| GRANT SELECT, EXECUTE ON `SCHEMA`.* TO 'user'@'dbhost'                                                      |
+-------------------------------------------------------------------------------------------------------------+

Thank you for the feedback.

I still can not repeat described behavior. Does schema you are connect to exist? Please also add option log-warnings=2 into MySQL server configuration file, restart it, then try to connect using WB again and send us content of MySQL server error log.

I did add the option log-warnings=2, restarted the server, tried to reconnect with WB, got the same WB error again, but the server error log stays empty.

Additional hints:

1. Yes, the schema does exist.

2. The error occurs when trying to connect via the 'SQL Development' column of WB. When I connect via the 'Server Administration' column of WB there's no problem.

I need to know the last commands Workbench is sending to the server.

Please enable general log and let us know what are the last commands from Workbench.

Also I need to know if you are using a special sql-mode.

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