Bug #74266 Unexpected exception: Cannot Acces a Disposed Object. Object Name : 'HUDForm '
Submitted: 8 Oct 2014 9:48 Modified: 8 Nov 2014 11:05
Reporter: Dilip Debsingha Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.0 OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any

[8 Oct 2014 9:48] Dilip Debsingha
Description:

Unexpected exception: Cannot Acces a Disposed
 Object. Object Name : 'HUDForm '
when trying to connect MYSQL server through VPN

How to repeat:
STR:

1. Launch MYSQL Workbench
2. Database-> Connect to Database
3. Enter Parameters for the connection
4. Click on OK

Got error popup
Cannot Acces a Disposed Object. Object Name : 'HUDForm '

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
[8 Oct 2014 9:49] Dilip Debsingha
Error screenshot

Attachment: WorkbenchUnexpectedError.PNG (image/png, text), 64.25 KiB.

[8 Oct 2014 9:49] Dilip Debsingha
Error screenshot

Attachment: WorkbenchUnexpectedError.PNG (image/png, text), 64.25 KiB.

[8 Oct 2014 11:05] MySQL Verification Team
Hello Dilip,

Thank you for the report.
I could not reproduce this issue at my end with latest WB. Could you please try latest MySQL workbench 6.2.3? You may want to download it from http://dev.mysql.com/downloads/workbench/

If you are still seeing the issue with WB 6.2.3 then pls report us back with WB log and screenshot with exact reproducible steps.

Thanks,
Umesh
[8 Oct 2014 11:06] MySQL Verification Team
Changing category to Workbench
[9 Nov 2014 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".