MySQL Bugs: #26128: Service control not accessible when connected to localhost

Bug #26128	Service control not accessible when connected to localhost
Submitted:	6 Feb 2007 23:11	Modified:	22 Mar 2007 1:56
Reporter:	[ name withheld ]	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.2.9	OS:	Windows (win2k sp4)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When firing up MySQL Administrator, it complains it cannot find the server service and/or the configuration file and therefore the Service Control and Startup Variables will not be available. In fact, said panels are disabled with a warning notice "This section is only available when connected to localhost".

The point is, I *am* connected to localhost, as the Server Information panel duly reports.

This bug is similar to http://bugs.mysql.com/bug.php?id=12794

On this particular machine, the server (5.1.7 beta) is installed in a non standard directory (Basedir: d:\mysql5). The my.ini file however is in the standard location (c:\winnt).

MySQL Administrator 1.1.9 does not have the problem. 1.2.6 through 1.2.9 do.

The type of windows user account does not matter. 1.1.9 worked OK both when logged in as administrator or power user, the other versions have the problem in both cases.

I am not sure, but this may have something to do with non-standard install dir. Another win2k machine I know of which only has a C: drive and (probably, not sure)  both server and MySQL Administrator installed in their default locations does not have the problem.

However, changing the install dirs on my development machine is not something I would undertake lightly... Regrettably, I do not have VMWare floating around.

How to repeat:
For those willing to take the plunge: install both server and GUI tools in non standard dirs on a win2k machine and see what happens...

Thank you for the bug report. I did the installation with the installer
using the custom option and non-default path and I was unable to repeat
the behavior. Could you please describe the exactly install procedure
you used. Thanks in advance.

The original install was done with the 5.0.18 setup.exe, alongside an existing 4.1 installation which was later removed. Subsequent upgrades have been done with "noinstall" packages unzipped right into the install dir. 

I checked the windows registry and found that there was no registry entry for the server. I then created the registry entry by hand using the relevant info in the reference manual (section 2.3.3.6), but the problem persist.

Thank you for the feedback.

"Subsequent upgrades have been done
with "noinstall" packages unzipped right into the install dir."

Then you installed the service using the --install option of the
server? mysqld-nt --install --defaults-file...

Thanks in advance.

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