Bug #65980 "Query Database" generates "Connection Cancelled" message when not maximized
Submitted: 22 Jul 2012 14:03 Modified: 3 Nov 2012 13:02
Reporter: Andy McKenna Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.40 CE REV 8790 OS:Windows (Server 2003 R2 x86)
Assigned to: CPU Architecture:Any
Tags: 2003, R2, server, VMWARE, windows, x86

[22 Jul 2012 14:03] Andy McKenna
Description:
I am using VMWare v4.x Player on Windows 7 Pro x64 on a core i7 ASUS laptop with 8GB of RAM. I run various Windows guests as VMs.

I have an external LCD onto which I _usually_ extend the Windows desktop and the external monitor is set to 1440x900). I have replicated the problem under both single monitor and extended monitor configurations.

The behavior is inconsistent. Sometimes I cannot get MySQLWB to launch at all. The issue does seem to be affected by the Windows screen resolutions and Window states of the VM Guest and the MySQLWB app. 

I have tried using MySQL WB from two different Windows guest VMs, both server 2003 R2 x86 boxes.

If the VM guest is started and maximized on any either the laptop or external display, using eitehr automatic or fixed screen resolutions, and then MySQLWB is launched maximized, I can use the "Query Database" operation and get a SQL Editor window.

Launching MySQLWB from any Windows guest VM that is not maximized to the host screen size and has MySQLWB in an unmaximized state yields the "Connection Cancelled" message. No errors are visible in the wb.log file.

How to repeat:
1. Launch the Windows Server 2003 R2 guest OS
2. Restore the guest window if it is maximized
3. Login and launch MySQLWB
4. Use any method to open the SQL Query Editor (double click a connection, menu ite, or right-mouse click)

OR

1. Launch the Windows Server 2003 R2 guest OS
2. Maximize the VM Guest window if it is not maximized
3. Login and launch MySQLWB
4. Use any method to open the SQL Query Editor (double click a connection, menu ite, or right-mouse click)

Suggested fix:
Not sure - seems to have something to do with Windows display properties.
[25 Jul 2012 17:01] Valeriy Kravchuk
Please, send the output of Help > System Info menu item.
[26 Aug 2012 1:00] Bugs System
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".
[12 Sep 2012 7:51] Vittorio Zinno
Hi Andy,

I had the same problem this morning on a new installation von win 2003 srv. It's a VM for testing purpose. Installing workbench-gpl-5.2.42-win32 and then connecting brought me to the BUG "Connection Cancelled". I uninstalled that version an I tried mysql-workbench-gpl-5.2.25-win32. This version works.

Well I don't know if it's a matter of win 2003 srv. 

Best regards,

Vittorio Zinno
mailto:v.zinno@docucom.ch 
Docucom AG
Switzerland
[12 Sep 2012 14:35] Andy McKenna
System Info
MySQL Workbench CE for Windows version 5.2.40  revision 8790
Configuration Directory: C:\Documents and Settings\Administrator.HOMEBASE\Application Data\MySQL\Workbench
Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft Windows Server 2003 R2, Standard Edition Service Pack 2 (build 3790)
CPU: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 512 MiB RAM
Active video adapter (0): VMware SVGA II
Installed video RAM: 128 MB
Current video mode: 1440 x 900 x 4294967296 colors
Used bit depth: 32
Driver version: 11.08.11.0000 - build-442614
Installed display drivers: vmx_fb.dll
Current user language: English (United States)
[3 Oct 2012 13:02] Armando Lopez Valencia
Thanks for your report Andy
Can you please try with our new WB 5.2.44 and let us know if you can still see the problem?
Thanks.
[4 Nov 2012 1:00] Bugs System
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".