Bug #52547 | "Unexpected Error" when connecting to server instance | ||
---|---|---|---|
Submitted: | 2 Apr 2010 9:14 | Modified: | 26 May 2010 17:09 |
Reporter: | Norbert Ziegler | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.16 | OS: | Windows (XP SP3) |
Assigned to: | CPU Architecture: | Any |
[2 Apr 2010 9:14]
Norbert Ziegler
[8 Apr 2010 16:24]
Johannes Taxacher
Hi Norbert, can you repeat the problem and give us instructions on how to do so too? Please also try latest release (5.2.17) thanks in advance
[12 Apr 2010 7:38]
Norbert Ziegler
Hi, 1. "give us instructions on how to do so too?" Read the section in "how to repeat", I already filed text in this section, anything unclear? 2. Can not reproduce it today, seems that computers need vacations, too. 3. Try it on your own if you can reproduce it. If not: close and forget. Regards, Norbert
[26 Apr 2010 8:14]
Sveta Smirnova
Thank you for the feedback. I don't understand what "Enter new (first) Server Instance (did not fill out 2nd tab)" means. Please explain. Please also try with current version 5.2.19.
[26 Apr 2010 15:20]
Norbert Ziegler
Replying to "I don't understand what "Enter new (first) Server Instance (did not fill out 2nd tab)" means. Please explain." Simple: when you open "MySQL Workbench", on the right side you have "Server Admin" and below a link to add a "New Server Instance". The error occured when I added the first, new server-instance. When adding it, in the second step a dialog with a tabbed-pane pops up, I only filled out "Parameters" but not "Advanced".
[26 Apr 2010 17:09]
Sveta Smirnova
Thank you for the feedback. I tried same in my environment and can not repeat crash with version 5.2.19. Please try with version 5.2.19 in yours when you have time, so we can be sure bug is not repeatable anymore.
[26 May 2010 23: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".