Bug #60506 | Unexpected Error when creating new Server Instance | ||
---|---|---|---|
Submitted: | 17 Mar 2011 10:25 | Modified: | 17 Mar 2011 13:18 |
Reporter: | Dick Dijk | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Administration | Severity: | S3 (Non-critical) |
Version: | 5.2.31CE rev 7115 | OS: | Windows (7) |
Assigned to: | CPU Architecture: | Any | |
Tags: | error, unexpected |
[17 Mar 2011 10:25]
Dick Dijk
[17 Mar 2011 10:40]
Valeriy Kravchuk
Please, check if the same problem happens with a newer version, 5.2.33.
[17 Mar 2011 12:35]
Peter Laursen
This problem is only one of those I reported here (with 5.2.33): http://bugs.mysql.com/bug.php?id=60451 (I used the term 'memory violation' but I think it was exactly same error message I had).
[17 Mar 2011 12:39]
Peter Laursen
And my last post set status back to 'open'. Not intentional from my side (of course as I cannot control it) and I think this is a recent change of behavior with this system. If this is deliberate in order to ensure that '3rd party comments' are considered, it is fine with me!
[17 Mar 2011 13:18]
Dick Dijk
I upgraded Workbench to 5.2.33. I now get a clearer error message: "In order to manage a MySQL server it must be installed as a service. This wizard could not find any MySQL service on the target machine, hence the server instance cannot be created". This makes sense, because my server is running in "noinstall" mode. Case closed, as far as I'm concerned. Dick