Bug #59865 | Hang-up while configuring new server for management | ||
---|---|---|---|
Submitted: | 1 Feb 2011 8:48 | Modified: | 2 Apr 2011 16:21 |
Reporter: | Arnaud Millereux | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 5.2.31a | OS: | Windows (XP SP3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
[1 Feb 2011 8:48]
Arnaud Millereux
[1 Feb 2011 9:18]
Valeriy Kravchuk
Do you have Windows service defined for your MySQL server?
[2 Mar 2011 0: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".
[2 Mar 2011 16:21]
Valeriy Kravchuk
Then it looks like a duplicate of/related to bug #59578. Please, check. Workbench assumes your server is represented by a Windows service with a name that starts with MySQL (case-insensitive). This is needed to find out what my.ini file it uses (as it is needed for several tabs in Administration service). If service like that does not exist current version of Workbench just crashes. Fix to bug #59578 should allow it to proceed and let you enter my.ini full path manually.
[2 Apr 2011 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".