Bug #51115 Windows server will not start w/in workbenvch
Submitted: 11 Feb 2010 18:03 Modified: 12 Mar 2010 18:31
Reporter: Andy Ellixson Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.15b OS:Windows (Vista/7)
Assigned to: CPU Architecture:Any

[11 Feb 2010 18:03] Andy Ellixson
Description:
I've pre-installed MySql server to a non-standard location, I:\mysql\MySql Server5.1  Using the workbench, I attempted to configure the WB for my instance. The key="sys.config.path" always points to "%ProgramFiles%\MySQL\MySQL Server 5.1\my.ini"  WB instance configurator should allow you to browse to the my.ini location.  Assuming instance will be in "%ProgramFiles%" is not a good assumption.

To fix, locate windows profile and change %ProgramFiles% to appropriate prefix.

How to repeat:
1)Install in non-standard location.
2) Start Workbench
3) Attempt to add Instance configuration for running MySQL 5.1 server.

Suggested fix:
Browse button that will allow administrator to locate instance on file system.
[11 Feb 2010 18:15] Andy Ellixson
The title says server will not start w/in WB, but the bug is about config.  As such, the server won't start while in the WB anyway.  Even after verifying all paths and my.ini locations.  Start Server will not start the server.
[12 Feb 2010 13:01] Valeriy Kravchuk
What is the Windows service name for your MySQL server? Is it MySQL or something else, like MySQL51?
[12 Feb 2010 14:41] Andy Ellixson
I've made several attempts at this.  The service name is currently MySQLSvr51
[12 Feb 2010 18:31] Valeriy Kravchuk
Check then if the same service name is listed in the instance configuration. There is a tab where exact commands (sc ...) used to start, stop server and check its status are listed. They use MySQL as service name by default.
[13 Mar 2010 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".