MySQL Bugs: #13330: Administrator looks in the wrong location for my.ini file

Bug #13330	Administrator looks in the wrong location for my.ini file
Submitted:	19 Sep 2005 22:18	Modified:	12 Dec 2006 12:29
Reporter:	Gerardo Narvaja	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.4rc	OS:	Windows (Windows)
Assigned to:	Vladimir Kolesnikov	CPU Architecture:	Any

Description:
When installing 5.0 with the Windows installer, he my.ini file is located in the base installatioin directory by default. MySQL Administrator, when trying to read the Startup Variables crashes with an "Access violation" message. Clicking OK in the error message shows the variables screen empty, at the bottom it says "Option File: C:\WINDOWS\my.ini" (wrong location, see above).

How to repeat:
1. Do a clean MySQL 5.0 installation (no my.ini from previous installations) using the regular installer and all default options
2. Start the server
3. Run MySQL Administrator
4. Click on Startup Variables on the left hand side panel

Hi, Gerardo

Do you run MySQL Server as a Windows service (It should be so if you accept installation defaults) ? If so, can you please send the command line for the service being run. To do this please open control panel -> administration -> services. and select the mysql service from the list. right-click on it and copy the command line.

It for example could look like "C:\Program Files\MySQL\MySQL Server 5.0.13rc\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0.13rc\my.ini" MySQL

If you have multiple mysql service entries (with different names) please send them all and point which one MySQL Administrator was connected to. Also please include the version of MySQL Administrator you're using.

Thanks

I too have noticed that MySql Administrator looks in the wrong place for the MySql.ini file.

DETAILS:
- Windows 2003 (SP1)
- MySql 4.1.x: not running on 3306
- MySql 5.0.10: running on 3310

STEPS TO REPRODUCE:
1) Start MySql Administrator 1.1.3

2) Connect to 5.0.10 (3310) instance

3) Server information displays the correct information. All icons on the left hand side are enabled.

4) Clicking the "Service Control" icon results in the app thinking it's connected to MySql 4.1.x. Now only the "Service Control", "Startup Variables" and "Server Logs" icons are enabled.

I'm experiencing the same thing. The first time I click on Startup Variables
I'm running the uniform server http://www.uniformserver.com/
which starts mysql as: start \usr\local\mysql\bin\mysqld-opt.exe --defaults-file=/usr/local/mysql/bin/my-small.cnf

I'm a little new to mysql: Is mysqlAdministrator supposed to pick up the startup variables from my-small.cnf ???

Do I need a c:\windows\my.ini ???

I think the version of mysql bundled with uniform server is 4.1.14a
My MySqlAdministrator is version 1.1.3
and i'm running windows 2003

I'm experiencing the same problem with 1.1.4

I have two server instances running as services:
4.0.18 and 5.0.15 on Win XP SP2 512M RAM
4.0.18 service entry:
    \mysqld-max-nt --defaults-file="C:\WINDOWS\my.ini" "MySql"
5.0.15 service entry:
    C:\db\mysql5\bin\mysqld-max-nt --defaults-file="C:\db\mysql5\my.ini" "MySQL5"

If I have "Service Control" selected and look at the "Configure Service" tab for each server, the config file is correct.
If I swtich to "Startup Variables" the "option file" at the bottom of the screen always stays "C:\WINDOWS\my.ini" regardless of which instance I select.

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".

Thank you for the report.

Verified as described in comments: more than one server, but MySQL Administrator looks only in C:\Windows\my.ini.

I made mistake in previous comment.

MySQL Administrator takes configuration file of first server if sort them in alphabetical order. Not always from C:\Windows

I was unable to repeat this issue with 1.2.7.